From 9ba441b9cf63dbca4b394dc95571eade623c0564 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivar=20Conradi=20=C3=98sthus?= Date: Thu, 29 Sep 2022 19:26:14 +0200 Subject: [PATCH] fix: typo in strategy-constraints.md (#2115) --- 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 5981570f16..a67cec58db 100644 --- a/website/docs/advanced/strategy-constraints.md +++ b/website/docs/advanced/strategy-constraints.md @@ -13,7 +13,7 @@ Unleash 4.9 introduced a more comprehensive set of constraint operators. These r When using _advanced strategy constraints_ (any operator that isn't `IN` or `NOT_IN`), *make sure your client SDK is up to date* and supports this feature. For older versions of the client SDKs we **cannot guarantee** any specific behavior. Please see the [incompatibilities section](#incompatibilities) for more information. ::: -**Strategy constraints** are conditions that must be satisifed for an [activation strategy](../user_guide/activation_strategy) to be evaluated for a feature toggle. +**Strategy constraints** are conditions that must be satisfied for an [activation strategy](../user_guide/activation_strategy) to be evaluated for a feature toggle. With strategy constraints, you can: - roll out a feature **only to users in a specific region** - schedule a feature to be **released at a specific time**