From a2971fb2ab30d2e4400946e2413bcc3ded74a814 Mon Sep 17 00:00:00 2001 From: Janet Kuo Date: Wed, 22 Jul 2015 17:16:28 -0700 Subject: [PATCH] Fix doc typos --- docs/admin/networking.md | 2 +- docs/design/networking.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/networking.md b/docs/admin/networking.md index d9de18bfbdf..7213434120c 100644 --- a/docs/admin/networking.md +++ b/docs/admin/networking.md @@ -125,7 +125,7 @@ applies IP addresses 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 does imply that containers within a `Pod` must coordinate port usage, but this is no -different that processes in a VM. We call this the "IP-per-pod" model. This +different than processes in a VM. We call this the "IP-per-pod" model. This is implemented in Docker as a "pod container" which holds the network namespace open while "app containers" (the things the user specified) join that namespace with Docker's `--net=container:` function. diff --git a/docs/design/networking.md b/docs/design/networking.md index b1d5a460101..dfe0f93e299 100644 --- a/docs/design/networking.md +++ b/docs/design/networking.md @@ -87,7 +87,7 @@ whereas, in general, they don't control what pods land together on a host. ## Pod to pod Because every pod gets a "real" (not machine-private) IP address, pods can -communicate without proxies or translations. The can use well-known port +communicate without proxies or translations. The pod can use well-known port numbers and can avoid the use of higher-level service discovery systems like DNS-SD, Consul, or Etcd.