From 025ce4194526151656b1a70fbeab4bbbe903868b Mon Sep 17 00:00:00 2001 From: Anthony Date: Fri, 18 Aug 2017 05:03:49 +0800 Subject: [PATCH] Update securing-a-cluster.md (#4975) modify "their namespace" to "their namespaces" --- docs/tasks/administer-cluster/securing-a-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index 43a1308d26..a0f84ad4d3 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -107,7 +107,7 @@ policy. The [network policies](/docs/tasks/administer-cluster/declare-network-policy/) for a namespace allows application authors to restrict which pods in other namespaces may access pods and ports -within their namespace. Many of the supported [Kubernetes networking providers](/docs/concepts/cluster-administration/networking/) +within their namespaces. Many of the supported [Kubernetes networking providers](/docs/concepts/cluster-administration/networking/) now respect network policy. Quota and limit ranges can also be used to control whether users may request node ports or