Minor fixes to multicluster blog (kubernetes#1159)

This commit updates "cluster" to "cross-cluster" in the service mirroring section. Fixes kubernetes#1157 Signed-off-by: Ujjwal Goyal <[email protected]>
mikutas · Aug 17, 2021 · e3c149a · e3c149a
1 parent ec733ac
commit e3c149a
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/linkerd.io/content/blog/multicluster-kubernetes-with-service-mirroring.md b/linkerd.io/content/blog/multicluster-kubernetes-with-service-mirroring.md
@@ -68,9 +68,9 @@ Enter service mirroring.
 The goal of the service mirroring is to allow the same guarantees that a service
 mesh like Linkerd provides for in-cluster calls—identity, traffic shifting,
 etc—to also be applied to cross-cluster calls. Service mirroring works, as the
-name suggests, by "mirroring" service information between clusters, With service
+name suggests, by "mirroring" service information between clusters. With service
 mirroring in place, the full observability, security, and routing features of
-Linkerd apply uniformly to both in-cluster and cluster-calls, and the
+Linkerd apply uniformly to both in-cluster and cross-cluster calls, and the
 application does not need to distinguish between those situations.
 
 The service mirror is a Kubernetes Operator. Once installed, it mirrors a remote