Merge branch 'v0.11' into amolenk/actorkeyseparator

daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md

@@ -53,7 +53,7 @@ Dapr allows two methods by which you can subscribe to topics: **declarative**, w
 
 ### Message Delivery
 
-In principle, Dapr considers message successfully delivered when the subscriber responds with a non-error response after processing the message. For more granular control, Dapr's publish/subscribe API also provides explicit statuses, defined in the response payload, which the subscriber can use to indicate the specific handling instructions to Dapr (e.g. `RETRY` or `DROP`). For more information message routing see [Dapr publish/subscribe API documentation] ({{< ref "pubsub_api.md#provide-routes-for-dapr-to-deliver-topic-events" >}})
+In principle, Dapr considers message successfully delivered when the subscriber responds with a non-error response after processing the message. For more granular control, Dapr's publish/subscribe API also provides explicit statuses, defined in the response payload, which the subscriber can use to indicate the specific handling instructions to Dapr (e.g. `RETRY` or `DROP`). For more information message routing see [Dapr publish/subscribe API documentation]({{< ref "pubsub_api.md#provide-routes-for-dapr-to-deliver-topic-events" >}})
 
 ### At-Least-Once guarantee
 

daprdocs/static/docs/open-telemetry-collector/open-telemetry-collector.yaml

@@ -10,9 +10,6 @@ data:
     receivers:
       zipkin:
         endpoint: 0.0.0.0:9411
-    processors:
-      queued_retry:
-      batch:
     extensions:
       health_check:
       pprof:
@@ -37,7 +34,6 @@ data:
         traces:
           receivers: [zipkin]
           exporters: [azuremonitor,logging]
-          processors: [batch, queued_retry]
 ---
 apiVersion: v1
 kind: Service