From 490c20c433cde0e04ac098a2a1f1899d6ab70be7 Mon Sep 17 00:00:00 2001 From: Melinda Fekete Date: Fri, 11 Jul 2025 13:13:51 +0200 Subject: [PATCH] Update website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md Co-authored-by: Simon Hornby --- .../docs/feature-flag-tutorials/use-cases/gradual-rollout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md b/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md index d98bbd909d..da000000a0 100644 --- a/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md +++ b/website/docs/feature-flag-tutorials/use-cases/gradual-rollout.md @@ -95,7 +95,7 @@ Within a gradual rollout activation strategy, you can use strategy constraints t Add [constraints](/reference/activation-strategies#constraints) to refine the rollout based on user attributes, segments, or conditions. -### Define custom context Fields for strategy constraints +### Define custom context fields for strategy constraints If you want to create new types of constraints that are not built into Unleash, you can create [custom context fields](/reference/unleash-context#custom-context-fields) to use in your gradual rollout for more advanced use cases.