Apply suggestions from code review

Co-authored-by: Todd Baert <[email protected]> Signed-off-by: Michael Beemer <[email protected]>
open-feature · Jan 19, 2024 · 37feff9 · 37feff9
1 parent 69918f5
commit 37feff9
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/specification/sections/01-flag-evaluation.md b/specification/sections/01-flag-evaluation.md
@@ -107,7 +107,7 @@ See [hooks](./04-hooks.md) for details.
 OpenFeature.getProviderMetadata();
 ```
 
-It must be possible to access provider metadata using a `domain`.
+It's possible to access provider metadata using a `domain`.
 If a provider has not be registered under the requested domain, the default provider metadata is returned.
 
 ```typescript
@@ -130,7 +130,7 @@ See [provider](./02-providers.md), [domain](../glossary.md#domain) for details.
 OpenFeature.getClient();
 ```
 
-It must be possible to create a client that is associated with a `domain`.
+It's possible to create a client that is associated with a `domain`.
 The client will use a provider in the same `domain` if one exists, otherwise, the default provide is used.
 
 ```java

diff --git a/specification/sections/03-evaluation-context.md b/specification/sections/03-evaluation-context.md
@@ -90,7 +90,7 @@ See [setting a provider](./01-flag-evaluation.md#setting-a-provider), [domain](.
 
 > The API **MUST** have a mechanism to manage `evaluation context` for an associated `domain`.
 
-In the static-context paradigm, it must be possible to create and remove provider-specific context.
+In the static-context paradigm, it's possible to create and remove provider-specific context.
 See [setting a provider](./01-flag-evaluation.md#setting-a-provider), [domain](../glossary.md#domain) for details.
 
 #### Requirement 3.2.3