From 28567cf8375ac1277ac7979263aea4165a5dca27 Mon Sep 17 00:00:00 2001 From: Zijun Wang Date: Wed, 22 Nov 2023 15:11:42 -0800 Subject: [PATCH] Address PR comments --- docs/guides/multi-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/multi-cluster.md b/docs/guides/multi-cluster.md index 6a44445e..15d1d6b6 100644 --- a/docs/guides/multi-cluster.md +++ b/docs/guides/multi-cluster.md @@ -45,4 +45,4 @@ Following steps show you how to set up this recommended multi-cluster architectu kubectl apply -f examples/service-2-import.yaml ``` 1. At this point, the connectivity setup finished, pods in workload cluster1 are able to communicate with `service-2` in workload cluster2 (and vice versa) via the `my-httproute` DNS name. -1. Furthermore, you could have more workloads clusters to join the `my-gateway` service network by creating the `ServiceNewtorkAssociation(s)`, they will all be able to communicate with `service-1` and `service-2` via the `my-httproute` DNS name and path matching. +1. Furthermore, you could have more workload clusters to join the `my-gateway` service network by creating the `ServiceNewtorkAssociation(s)`, workloads there all be able to communicate with `service-1` and `service-2` via the `my-httproute` DNS name and path matching.