From 46987cf0e9aadc563b9843ae30d3e4d1459ef7d1 Mon Sep 17 00:00:00 2001 From: chirangaalwis Date: Sat, 17 Jul 2021 13:42:22 +0530 Subject: [PATCH] [NetworkPolicy][EndPort] Fix incorrect grammar Fix incorrect grammar of the valid range of `endPort` property --- .../en/docs/concepts/services-networking/network-policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/network-policies.md b/content/en/docs/concepts/services-networking/network-policies.md index 2c9ed4a90e..ec29f1d813 100644 --- a/content/en/docs/concepts/services-networking/network-policies.md +++ b/content/en/docs/concepts/services-networking/network-policies.md @@ -255,7 +255,7 @@ The above rule allows any Pod with label `db` on the namespace `default` to comm The following restrictions apply when using this field: * As an alpha feature, this is disabled by default. To enable the `endPort` field at a cluster level, you (or your cluster administrator) need to enable the `NetworkPolicyEndPort` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the API server with `--feature-gates=NetworkPolicyEndPort=true,…`. -* The `endPort` field must be equal than or greater to the `port` field. +* The `endPort` field must be equal to or greater than the `port` field. * `endPort` can only be defined if `port` is also defined. * Both ports must be numeric.