Merge pull request #54384 from gwynnemonahan/sidecar_proxies_typo

OSSMDOC-738 Fixed noun/verb agreement.

Author: bburt-rh

modules/ossm-architecture.adoc

@@ -16,7 +16,7 @@ The data plane is implemented in such a way that it intercepts all inbound (ingr
 
 * *Envoy proxies* are the only Istio components that interact with data plane traffic. All incoming (ingress) and outgoing (egress) network traffic between services flows through the proxies. The Envoy proxy also collects all metrics related to services traffic within the mesh. Envoy proxies are deployed as sidecars, running in the same pod as services. Envoy proxies are also used to implement mesh gateways.
 
-** *Sidecar proxies* manage inbound and outbound communication to the workload instance it is attached to.
+** *Sidecar proxies* manage inbound and outbound communication for their workload instance.
 
 ** *Gateways* are proxies operating as load balancers receiving incoming or outgoing HTTP/TCP connections. Gateway configurations are applied to standalone Envoy proxies that are running at the edge of the mesh, rather than sidecar Envoy proxies running alongside your service workloads. You use a Gateway to manage inbound and outbound traffic for your mesh, letting you specify which traffic you want to enter or leave the mesh.