diff --git a/howto/send-events-with-output-bindings/README.md b/howto/send-events-with-output-bindings/README.md
index a311cb328..ea06ee07c 100644
--- a/howto/send-events-with-output-bindings/README.md
+++ b/howto/send-events-with-output-bindings/README.md
@@ -42,5 +42,11 @@ curl -X POST -H  http://localhost:3500/v1.0/bindings/myEvent -d '{ "data": { "me
 ```
 
 As seen above, we invoked the `/binding` endpoint with the name of the binding to invoke, in our case its `myEvent`.
+The payload goes inside the mandatory `data` field, and can be any JSON serializable value.
 
-The payload goes inside the `data` field.
\ No newline at end of file
+
+## References
+
+* Binding [API](https://github.com/dapr/docs/blob/master/reference/api/bindings_api.md)
+* Binding [Components](https://github.com/dapr/docs/tree/master/concepts/bindings)
+* Binding [Detailed specifications](https://github.com/dapr/docs/tree/master/reference/specs/bindings) 
diff --git a/howto/trigger-app-with-input-binding/README.md b/howto/trigger-app-with-input-binding/README.md
index 397f921ce..e39f0f9dc 100644
--- a/howto/trigger-app-with-input-binding/README.md
+++ b/howto/trigger-app-with-input-binding/README.md
@@ -84,3 +84,10 @@ res.status(500).send()
 
 ### Event delivery Guarantees
 Event delivery guarantees are controlled by the binding implementation. Depending on the binding implementation, the event delivery can be exactly once or at least once.
+
+
+## References
+
+* Binding [API](https://github.com/dapr/docs/blob/master/reference/api/bindings_api.md)
+* Binding [Components](https://github.com/dapr/docs/tree/master/concepts/bindings)
+* Binding [Detailed specifications](https://github.com/dapr/docs/tree/master/reference/specs/bindings)