From 52281512ac314ba22f6ccfc717e0e40a9dd786ef Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Wed, 9 Mar 2022 10:56:48 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Fredrik Strand Oseberg --- website/docs/advanced/strategy-constraints.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/advanced/strategy-constraints.md b/website/docs/advanced/strategy-constraints.md index 500780a3399..fd07a14a625 100644 --- a/website/docs/advanced/strategy-constraints.md +++ b/website/docs/advanced/strategy-constraints.md @@ -33,7 +33,7 @@ To be able to constrain on a field, it must be listed under the Context Field me Unleash only provides a limited set of context fields by default, and they may not fulfill all your needs. By using [custom context fields](../user_guide/unleash_context#custom-context-fields), you can tailor strategy constraints to your specific use case, such as: -- based on tenant IDs,release a feature to only specific tenants in a multi-tenant setup +- based on tenant IDs, release a feature to only specific tenants in a multi-tenant setup - release a feature to users in a specific region - release a feature only to beta testers