fix workflow hints

SPEC.md

@@ -5827,7 +5827,7 @@ If the `output {...}` section is omitted from a workflow that is called as a sub
 
 ### Workflow Hints
 
-The `hints` section is optional and may contain any number of attributes (key/value pairs) that provide hints to the execution engine. Some workflow hint keys are reserved and have well-defined values. The value of a `hint` must be a [meta value](#meta-values).
+The `hints` section is optional and may contain any number of attributes (key/value pairs) that provide hints to the execution engine. Some workflow hint keys are reserved and have well-defined values.
 
 The runtime implementation may ignore any unsupported hint. A workflow execution never fails due to the inability of the execution engine to recognize or satisfy a hint.
 
@@ -5874,8 +5874,7 @@ workflow test_allow_nested_inputs {
   }
 
   hints {
-    allow_nested_inputs: true,
-    test_config: "optional:hints:allow_nested_inputs"
+    allow_nested_inputs: true
   }
 }
 ```
@@ -5895,6 +5894,15 @@ Example output:
 {
   "test_allow_nested_inputs.greeting": "Hello John"
 }
+
+```
+
+Test config:
+
+```json
+{
+  "dependencies": "allow_nested_inputs"
+}
 ```
 </p>
 </details>