Make it clear that provider hooks can be properties or methods.

Signed-off-by: Justin Abrahms <[email protected]>

specification.json

@@ -266,7 +266,7 @@
         {
             "id": "Requirement 2.10",
             "machine_id": "requirement_2_10",
-            "content": "The provider interface MAY define a `provider hook` method or function, which can be optionally implemented in order to add `hook` instances to the client.",
+            "content": "The provider interface MAY define a `provider hook` mechanism which can be optionally implemented in order to add `hook` instances to the client.",
             "RFC 2119 keyword": "MAY",
             "children": []
         },

specification/sections/02-providers.md

@@ -117,13 +117,16 @@ Feature flag management systems often need to transform the context structures t
 
 ##### Requirement 2.10
 
-> The provider interface **MAY** define a `provider hook` method or function, which can be optionally implemented in order to add `hook` instances to the client.
+> The provider interface **MAY** define a `provider hook` mechanism which can be optionally implemented in order to add `hook` instances to the client.
 
-```typescript
+```
 class MyProvider implements Provider {
   //...
 
-  List<Hook> providerHooks() {
+  private readonly hooks: Hook[] = [new MyProviderHook()];
+
+  // ..or alternatively..
+  getProviderHooks(): Hook[]  {
     return [new MyProviderHook()];
   }