mark review

Signed-off-by: Hannah Hunter <[email protected]>
dapr · Jul 31, 2023 · 16beee2 · 16beee2
1 parent f19dfc9
commit 16beee2
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 8 deletions.
diff --git a/...ontent/en/developing-applications/building-blocks/bindings/bindings-overview.md b/...ontent/en/developing-applications/building-blocks/bindings/bindings-overview.md
@@ -59,14 +59,14 @@ Read the [Use output bindings to interface with external resources guide]({{< re
 
 ## Binding directions (optional)
 
-You can provide information via the `direction` metadata field to indicate the direction supported by the binding component. With one of the following metadata values, the Dapr sidecar avoids the `"wait for the app to become ready"` state:
+You can provide the `direction` metadata field to indicate the direction(s) supported by the binding component. In doing so, the Dapr sidecar avoids the `"wait for the app to become ready"` state reducing the lifecycle dependency between the Dapr sidecar and the application:
 
 - `"input"`
 - `"output"`
 - `"input, output"`
 
 {{% alert title="Note" color="primary" %}}
-All bindings should include the `direction` property.
+It is highly recommended that all bindings should include the `direction` property.
 {{% /alert %}}
 
 [See a full example of the bindings `direction` metadata.]({{< ref "bindings_api.md#binding-direction-optional" >}})

diff --git a/...s/content/en/developing-applications/building-blocks/bindings/howto-bindings.md b/...s/content/en/developing-applications/building-blocks/bindings/howto-bindings.md
@@ -61,7 +61,7 @@ spec:
   - name: publishTopic
     value: sample
   - name: authRequired
-    value: "false"
+    value: false
   - name: direction
     value: output
 ```
@@ -93,7 +93,7 @@ spec:
   - name: publishTopic
     value: sample
   - name: authRequired
-    value: "false"
+    value: false
   - name: direction
     value: output
 ```

diff --git a/...s/content/en/developing-applications/building-blocks/bindings/howto-triggers.md b/...s/content/en/developing-applications/building-blocks/bindings/howto-triggers.md
@@ -66,7 +66,7 @@ spec:
   - name: publishTopic
     value: sample
   - name: authRequired
-    value: "false"
+    value: false
   - name: direction
     value: input
 ```
@@ -98,7 +98,7 @@ spec:
   - name: publishTopic
     value: sample
   - name: authRequired
-    value: "false"
+    value: false
   - name: direction
     value: input
 ```

diff --git a/daprdocs/content/en/reference/api/bindings_api.md b/daprdocs/content/en/reference/api/bindings_api.md
@@ -41,15 +41,15 @@ If running on kubernetes apply the component to your cluster.
 
 In some scenarios, it would be useful to provide additional information to Dapr to indicate the direction supported by the binding component. 
 
-Providing the supported binding direction helps the Dapr sidecar avoid the `"wait for the app to become ready"` state, where it waits indefinitely for the application to become available.
+Providing the binding `direction` helps the Dapr sidecar avoid the `"wait for the app to become ready"` state, where it waits indefinitely for the application to become available. This decouples the lifecycle dependency between the Dapr sidecar and the application.
 
 You can specify the `direction` field as part of the component's metadata. The valid values for this field are: 
 - `"input"`
 - `"output"`
 - `"input, output"`
 
 {{% alert title="Note" color="primary" %}}
-All bindings should include the `direction` property.
+It is highly recommended that all bindings should include the `direction` property.
 {{% /alert %}}
 
 Here a few scenarios when the `"direction"` metadata field could help: