Skip to content

Commit c0bb986

Browse files
rikatzTim Bannister
andauthored
Add review suggestions
Co-authored-by: Tim Bannister <[email protected]>
1 parent a799505 commit c0bb986

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content/en/docs/concepts/services-networking/network-policies.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@ You must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin tha
225225

226226
{{< feature-state for_k8s_version="v1.21" state="alpha" >}}
227227

228-
When writing a Network Policy, you can target a range of Ports instead of a single port.
228+
When writing a NetworkPolicy, you can target a range of ports instead of a single port.
229229

230230
This is achiveable with the usage of the `endPort` field, as the following example:
231231

@@ -260,7 +260,8 @@ The following restrictions apply when using this field:
260260
* When using `endPort` field, the `port` field must be numeric.
261261

262262
{{< note >}}
263-
You must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin that supports endPort field in NetworkPolicies ports specification.
263+
Your cluster must be using a {{< glossary_tooltip text="CNI" term_id="cni" >}} plugin that
264+
supports the `endPort` field in NetworkPolicy specifications.
264265
{{< /note >}}
265266

266267
## What you can't do with network policies (at least, not yet)

0 commit comments

Comments
 (0)