From db79ec0605e66fc441b63453bbd034cd70bcfa73 Mon Sep 17 00:00:00 2001 From: yanghaichao12 Date: Mon, 15 Apr 2019 13:02:00 +0800 Subject: [PATCH] Fix typos (#13754) --- content/en/docs/concepts/cluster-administration/networking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/cluster-administration/networking.md b/content/en/docs/concepts/cluster-administration/networking.md index e10256ca83..9610cf5035 100644 --- a/content/en/docs/concepts/cluster-administration/networking.md +++ b/content/en/docs/concepts/cluster-administration/networking.md @@ -64,7 +64,7 @@ Kubernetes IP addresses exist at the `Pod` scope - containers within a `Pod` share their network namespaces - including their IP address. This means that containers within a `Pod` can all reach each other's ports on `localhost`. This also means that containers within a `Pod` must coordinate port usage, but this -is no different than processes in a VM. This is called the "IP-per-pod" model. +is no different from processes in a VM. This is called the "IP-per-pod" model. How this is implemented is a detail of the particular container runtime in use.