fixup: spelling, minor non-normative clarifications

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
open-feature · May 8, 2023 · db43992 · db43992
1 parent b3e0c8c
commit db43992
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
@@ -45,7 +45,7 @@ See [provider initialization](./02-providers.md#24-initialization).
 
 >  The `provider mutator` function **MUST** invoke the `shutdown` function on the previously registered provider once it's no longer being used to resolve flag values.
 
-Setting a new provider means the previous provider is no longer in use, and should therefor be disposed of using it's `shutdown` function.
+Setting a new provider means the previous provider is no longer in use, and should therefore be disposed of using it's `shutdown` function.
 
 see: [shutdown](./02-providers.md#26-shutdown), [setting a provider](#setting-a-provider)
 
@@ -266,7 +266,7 @@ See [hooks](./04-hooks.md) for details.
 
 > The API **MUST** define a `shutdown` function, which, when called, must call the respective `shutdown` function on the active provider.
 
-The precise name of this function is not prescribed by this specification.
+The precise name of this function is not prescribed by this specification, but should be defined be the SDK.
 Relevant language idioms should be considered when choosing the name for this function, in accordance with the resource-disposal semantics of the language in question.
 
 see: [`shutdown`](./02-providers.md#25-shutdown)
diff --git a/specification/sections/02-providers.md b/specification/sections/02-providers.md
@@ -250,5 +250,5 @@ class MyProvider implements Provider, AutoDisposable {
 
 Providers may maintain remote connections, timers, threads or other constructs that need to be appropriately disposed of.
 Provider authors may implement the `shutdown` function to perform relevant clean-up actions.
-The precise name of this function is not prescribed by this specification.
+The precise name of this function is not prescribed by this specification, but should be defined be the SDK.
 Relevant language idioms should be considered when choosing the name for this function, in accordance with the resource-disposal semantics of the language in question.