Merge branch 'issue_3626' of https://github.com/hhunter-ms/docs into issue_3626

daprdocs/content/en/concepts/building-blocks-concept.md

@@ -6,7 +6,7 @@ weight: 200
 description: "Modular best practices accessible over standard HTTP or gRPC APIs"
 ---
 
-A [building block]({{< ref building-blocks >}}) is an HTTP or gRPC API that can be called from your code and uses one or more Dapr components. Dapr consists of a set of building blocks, with extensibility to add new building blocks. Dapr's building blocks:
+A [building block]({{< ref building-blocks >}}) is an HTTP or gRPC API that can be called from your code and uses one or more Dapr components. Dapr consists of a set of API building blocks, with extensibility to add new building blocks. Dapr's building blocks:
 - Address common challenges in building resilient, microservices applications 
 - Codify best practices and patterns
 

daprdocs/content/en/concepts/observability-concept.md

@@ -27,7 +27,7 @@ Maintaining this instrumentation code, which is not part of the core logic of th
 
 ## Observability for your application with Dapr
 
-When you leverage Dapr API building blocks to perform service-to-service calls and pub/sub messaging, Dapr offers an advantage with respect to [distributed tracing]({{< ref tracing >}}). Since this inter-service communication flows through the Dapr runtime (or "sidecar"), Dapr is in a unique position to offload the burden of application-level instrumentation.
+When you leverage Dapr API building blocks to perform service-to-service calls, pub/sub messaging, and other APIs, Dapr offers an advantage with respect to [distributed tracing]({{< ref tracing >}}). Since this inter-service communication flows through the Dapr runtime (or "sidecar"), Dapr is in a unique position to offload the burden of application-level instrumentation.
 
 ### Distributed tracing
 
@@ -37,7 +37,7 @@ Dapr can be [configured to emit tracing data]({{< ref setup-tracing.md >}}) usin
 
 ### Automatic tracing context generation
 
-Dapr uses [W3C tracing]({{< ref tracing >}}) specification for tracing context, included as part Open Telemetry (OTEL), to generate and propagate the context header for the application or propagate user-provided context headers. This means that you get tracing by default with Dapr.
+Dapr uses the [W3C tracing]({{< ref tracing >}}) specification for tracing context, included as part Open Telemetry (OTEL), to generate and propagate the context header for the application or propagate user-provided context headers. This means that you get tracing by default with Dapr.
 
 ## Observability for the Dapr sidecar and control plane
 

daprdocs/content/en/concepts/overview.md

@@ -107,7 +107,7 @@ Deploying and running a Dapr-enabled application into your Kubernetes cluster is
 
 ### Clusters of physical or virtual machines
 
-The Dapr control plane services can be deployed in High Availability (HA) mode to clusters of physical or virtual machines in production. In the diagram below, the Actor `Placement` and `Sentry` services are started on three different VMs to provide HA control plane. In order to provide name resolution using DNS for the applications running in the cluster, Dapr uses [Hashicorp Consul service]({{< ref setup-nr-consul >}}), also running in HA mode.  
+The Dapr control plane services can be deployed in high availability (HA) mode to clusters of physical or virtual machines in production. In the diagram below, the Actor `Placement` and security `Sentry` services are started on three different VMs to provide HA control plane. In order to provide name resolution using DNS for the applications running in the cluster, Dapr uses [Hashicorp Consul service]({{< ref setup-nr-consul >}}), also running in HA mode.  
 
 <img src="/images/overview-vms-hosting.png" width=1200 alt="Architecture diagram of Dapr control plane and Consul deployed to VMs in high availability mode">
 

daprdocs/content/en/operations/resiliency/targets.md

@@ -3,7 +3,7 @@ type: docs
 title: "Targets"
 linkTitle: "Targets"
 weight: 300
-description: "Apply resiliency policies to apps, components and actors"
+description: "Apply resiliency policies to targets including apps, components and actors"
 ---
 
 ### Targets

sdkdocs/go

@@ -1 +1 @@
-Subproject commit effc2f0d3c92ad76e11958e427c8d3b0900e1932
+Subproject commit ad25580bcfb638d56237faec0543565b4d0e134f

sdkdocs/java

@@ -1 +1 @@
-Subproject commit d1c61cae40e7c5d933d92705198506d947960aaa
+Subproject commit 9dc842faba3486e518babc29f7fbbca79248bfab