Skip to content

Commit ab666c2

Browse files
authored
Merge pull request #52519 from DhritiShikhar/fix-cluster-networking-typo
[en] Fixes typo in documentation
2 parents 754974f + be90770 commit ab666c2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/en/docs/concepts/cluster-administration/networking.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,9 @@ Kubernetes clusters, attending to the IP families configured, can be categorized
5656
- All components must agree on the configured primary IP family.
5757

5858
Kubernetes clusters only consider the IP families present on the Pods, Services and Nodes objects,
59-
independently of the existing IPs of the represented objects. Per example, a server or a pod can have multiple
60-
IP addresses on its interfaces, but only the IP addresses in `node.status.addresses` or `pod.status.ips` are
61-
considered for implementing the Kubernetes network model and defining the type of the cluster.
59+
independently of the existing IPs of the represented objects. For example, a server or a pod can have multiple
60+
IP addresses assigned to its interfaces, but only the IP addresses in `node.status.addresses` or `pod.status.ips` are
61+
considered when implementing the Kubernetes network model and defining the cluster type.
6262

6363
## How to implement the Kubernetes network model
6464

0 commit comments

Comments
 (0)