From 1b5d57ea6463a4b89d500e115316dfbe2aae3d7b Mon Sep 17 00:00:00 2001 From: Amulya Varote Date: Mon, 6 Dec 2021 22:20:23 -0800 Subject: [PATCH] Modified based on the review comments - 2 Signed-off-by: Amulya Varote --- .../building-blocks/bindings/howto-triggers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md b/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md index c6616a783..26ec1176c 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md +++ b/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md @@ -104,7 +104,7 @@ spec: Now configure your application to receive incoming events. If using HTTP, you need to listen on a `POST` endpoint with the name of the binding as specified in `metadata.name` in the file. -Below are code examples that leverage Dapr SDKs for output binding. +Below are code examples that leverage Dapr SDKs to demonstrate an output binding. {{< tabs Dotnet Java Python Go Javascript>}} @@ -281,7 +281,7 @@ In order to tell Dapr that you successfully processed an event in your applicati ### Rejecting an event -In order to tell Dapr that the event was not processed correctly in your application and schedule it for redelivery, return any response other than `200 OK`. For example, a `500 Error`. +In order to tell Dapr that the event was not processed correctly in your application and schedule it for redelivery and handle it gracefully using logs or exceptions. ### Specifying a custom route