From 4e0c0aa3685bd439de548c798f17394abcd4987b Mon Sep 17 00:00:00 2001 From: Rob Levin Date: Tue, 12 Oct 2021 13:09:14 -0700 Subject: [PATCH] docs: typo fix (#1021) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit definitely not compromised and google search says to prefer composed of Co-authored-by: Ivar Conradi Østhus --- websitev2/docs/user_guide/unleash-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/websitev2/docs/user_guide/unleash-context.md b/websitev2/docs/user_guide/unleash-context.md index d341e5d4da..6b43007159 100644 --- a/websitev2/docs/user_guide/unleash-context.md +++ b/websitev2/docs/user_guide/unleash-context.md @@ -5,7 +5,7 @@ title: Unleash Context To standardize a few activation strategies, we also needed to standardize the Unleash context, which contains fields that vary per request, required to implement the activation strategies. -The Unleash context is compromised by a set of predefined fields. The static fields do not change in the life-time of your application, while dynamic fields can change per feature toggle evaluation. +The Unleash context is composed of a set of predefined fields. The static fields do not change in the life-time of your application, while dynamic fields can change per feature toggle evaluation. **Static context fields**