Browse code

Fix some doc typos and spacings

Signed-off-by: Kevin Jing Qiu <kevin@idempotent.ca>
(cherry picked from commit 3b2ee9a704f1e3974dbb9ce857886d5e377580ab)

Kevin Jing Qiu authored on 2016/06/21 15:54:36
Showing 3 changed files
... ...
@@ -55,7 +55,7 @@ Docker Engine is a client-server application with these major components:
55 55
 
56 56
 ![Docker Engine Components Flow](article-img/engine-components-flow.png)
57 57
 
58
-The CLI imakes use of the Docker REST API to control or interact with the Docker daemon through scripting or direct CLI commands. Many other Docker applications make use of the underlying API and CLI.
58
+The CLI makes use of the Docker REST API to control or interact with the Docker daemon through scripting or direct CLI commands. Many other Docker applications make use of the underlying API and CLI.
59 59
 
60 60
 The daemon creates and manages Docker objects.  Docker objects include images, containers, networks, data volumes, and so forth.
61 61
 
... ...
@@ -252,7 +252,7 @@ isolated workspace we call the *container*.  When you run a container, Docker
252 252
 creates a set of *namespaces* for that container.
253 253
 
254 254
 This provides a layer of isolation: each aspect of a container runs in its own
255
-namespace and does not have access outside it.
255
+namespace and does not have access outside of it.
256 256
 
257 257
 Some of the namespaces that Docker Engine uses on Linux are:
258 258
 
... ...
@@ -44,7 +44,7 @@ Many using Docker will want `ip_forward` to be on, to at least make
44 44
 communication _possible_ between containers and the wider world. May also be
45 45
 needed for inter-container communication if you are in a multiple bridge setup.
46 46
 
47
-Docker will   never make changes to your system `iptables` rules if you set
47
+Docker will never make changes to your system `iptables` rules if you set
48 48
 `--iptables=false` when the daemon starts.  Otherwise the Docker server will
49 49
 append forwarding rules to the `DOCKER` filter chain.
50 50
 
... ...
@@ -35,7 +35,7 @@ NETWORK ID          NAME                DRIVER
35 35
 cf03ee007fb4        host                host
36 36
 ```
37 37
 
38
-Historically, these three networks are  part of Docker's implementation. When
38
+Historically, these three networks are part of Docker's implementation. When
39 39
 you run a container you can use the `--net` flag to specify which network you
40 40
 want to run a container on. These three networks are still available to you.
41 41