From e8e61870c91748308a3b77bd5d5a4b5638424147 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Tue, 23 Oct 2018 07:34:32 -0700 Subject: [PATCH] content/en/docs/setup/multiple-zones: Fix "pods in some pods" typo (#10664) The previous version is from cbbf1fa6 (Multizone: docs, 2016-03-16, #140). --- content/en/docs/setup/multiple-zones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/setup/multiple-zones.md b/content/en/docs/setup/multiple-zones.md index e050489730..5256d703b0 100644 --- a/content/en/docs/setup/multiple-zones.md +++ b/content/en/docs/setup/multiple-zones.md @@ -58,7 +58,7 @@ There are some important limitations of the multizone support: * We assume that the different zones are located close to each other in the network, so we don't perform any zone-aware routing. In particular, traffic -that goes via services might cross zones (even if pods in some pods backing that service +that goes via services might cross zones (even if some pods backing that service exist in the same zone as the client), and this may incur additional latency and cost. * Volume zone-affinity will only work with a `PersistentVolume`, and will not