Merge branch 'v0.11' into patch-1

daprdocs/content/en/developing-applications/building-blocks/bindings/howto-bindings.md

@@ -57,7 +57,7 @@ As seen above, you invoked the `/binding` endpoint with the name of the binding
 The payload goes inside the mandatory `data` field, and can be any JSON serializable value.
 
 You'll also notice that there's an `operation` field that tells the binding what you need it to do.
-You can check [here]({{< ref bindings >}}) which operations are supported for every output binding.
+You can check [here]({{< ref supported-bindings >}}) which operations are supported for every output binding.
 
 
 ## References

daprdocs/content/en/operations/components/setup-bindings/supported-bindings/kubernetes-binding.md

@@ -63,7 +63,7 @@ Three different event types are available:
 - Delete : Only the `oldVal` field is populated, `newVal` field is an empty `v1.Event`, `event` is `delete`
 - Update : Both the `oldVal` and `newVal` fields are populated,  `event` is `update`
 
-## Required permisiions
+## Required permissions
 
 For consuming `events` from Kubernetes, permissions need to be assigned to a User/Group/ServiceAccount using [RBAC Auth] mechanism of Kubernetes.
 
@@ -105,4 +105,4 @@ roleRef:
 - [Bindings building block]({{< ref bindings >}})
 - [How-To: Trigger application with input binding]({{< ref howto-triggers.md >}})
 - [How-To: Use bindings to interface with external resources]({{< ref howto-bindings.md >}})
-- [Bindings API reference]({{< ref bindings_api.md >}})
+- [Bindings API reference]({{< ref bindings_api.md >}})