From cbffc023e91d9024656f19ff700c436bdc7448b8 Mon Sep 17 00:00:00 2001
From: Saintmalik <msalawu5@gmail.com>
Date: Fri, 27 Nov 2020 04:27:04 +0000
Subject: [PATCH] Fix broken url in docs

---
 content/en/docs/setup/best-practices/multiple-zones.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/setup/best-practices/multiple-zones.md b/content/en/docs/setup/best-practices/multiple-zones.md
index 501e954642..f24c3bdcca 100644
--- a/content/en/docs/setup/best-practices/multiple-zones.md
+++ b/content/en/docs/setup/best-practices/multiple-zones.md
@@ -111,7 +111,7 @@ see [Allowed topologies](/docs/concepts/storage/storage-classes/#allowed-topolog
 ## Networking
 
 By itself, Kubernetes does not include zone-aware networking. You can use a
-[network plugin](docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)
+[network plugin](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)
 to configure cluster networking, and that network solution might have zone-specific
 elements. For example, if your cloud provider supports Services with
 `type=LoadBalancer`, the load balancer might only send traffic to Pods running in the