Skip to content

Commit a2971fb

Browse files
committed
Fix doc typos
1 parent d9bb171 commit a2971fb

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/admin/networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ applies IP addresses at the `Pod` scope - containers within a `Pod` share their
125125
network namespaces - including their IP address. This means that containers
126126
within a `Pod` can all reach each other’s ports on `localhost`. This does imply
127127
that containers within a `Pod` must coordinate port usage, but this is no
128-
different that processes in a VM. We call this the "IP-per-pod" model. This
128+
different than processes in a VM. We call this the "IP-per-pod" model. This
129129
is implemented in Docker as a "pod container" which holds the network namespace
130130
open while "app containers" (the things the user specified) join that namespace
131131
with Docker's `--net=container:<id>` function.

docs/design/networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ whereas, in general, they don't control what pods land together on a host.
8787
## Pod to pod
8888

8989
Because every pod gets a "real" (not machine-private) IP address, pods can
90-
communicate without proxies or translations. The can use well-known port
90+
communicate without proxies or translations. The pod can use well-known port
9191
numbers and can avoid the use of higher-level service discovery systems like
9292
DNS-SD, Consul, or Etcd.
9393

0 commit comments

Comments
 (0)