Merge pull request #2046 from allencloud/fix-typos-in-docs

fix typos in docs

docs/plan-for-production.md

@@ -60,16 +60,16 @@ the different components of a Swam cluster listen on. You should use these to
 configure your firewalls and other network access control lists.
 
 - **Swarm manager.**
-    - **Inbound 80/tcp (HTTP)**. This is allows `docker pull` commands to work. If you will be pulling from Docker Hub you will need to allow connections on port 80 from the internet.
+    - **Inbound 80/tcp (HTTP)**. This allows `docker pull` commands to work. If you plan to pull images from Docker Hub, you must allow Internet connections through port 80.
     - **Inbound 2375/tcp**. This allows Docker Engine CLI commands direct to the Engine daemon.
     - **Inbound 3375/tcp**. This allows Engine CLI commands to the Swarm manager.
     - **Inbound 22/tcp**. This allows remote management via SSH
 - **Service Discovery**:
-    - **Inbound 80/tcp (HTTP)**. This is allows `docker pull` commands to work. If you will be pulling from Docker Hub you will need to allow connections on port 80 from the internet.
+    - **Inbound 80/tcp (HTTP)**. This allows `docker pull` commands to work. If you plan to pull images from Docker Hub, you must allow Internet connections through port 80.
     - **Inbound *Discovery service port***. This needs setting to the port that the backend discovery service listens on (consul, etcd, or zookeeper).
     - **Inbound 22/tcp**. This allows remote management via SSH
 - **Swarm nodes**:
-    - **Inbound 80/tcp (HTTP)**. This is allows `docker pull` commands to work. If you will be pulling from Docker Hub you will need to allow connections on port 80 from the internet.
+    - **Inbound 80/tcp (HTTP)**. This allows `docker pull` commands to work. If you plan to pull images from Docker Hub, you must allow Internet connections through port 80.
     - **Inbound 2375/tcp**. This allows Engine CLI commands direct to the Docker daemon.
     - **Inbound 22/tcp**. This allows remote management via SSH.
 - **Custom, cross-host container networks**:
@@ -329,7 +329,7 @@ The question of ownership is vital in production environments. It is therefore
 vital that you consider and agree on all of the following when planning,
 documenting, and deploying your production Swarm clusters.
 
-- Who's budget does the production Swarm infrastructure come out of?
+- Whose budget does the production Swarm infrastructure come out of?
 - Who owns the accounts that can administer and manage the production Swarm
 cluster?
 - Who is responsible for monitoring the production Swarm infrastructure?

docs/swarm_at_scale/01-about.md

@@ -17,7 +17,7 @@ required first.
 
 ## Learn the example back story
 
-Your company is a pet food company that has bought an commercial during the
+Your company is a pet food company that has bought a commercial during the
 Superbowl. The commercial drives viewers to a web survey that asks users to vote
 – cats or dogs. You are developing the web survey.
 

docs/swarm_at_scale/04-deploy-app.md

@@ -194,7 +194,7 @@ In the following steps, your launch several containers to the voting application
         $ docker run --restart=unless-stopped --env="constraint:node==frontend02" -p 6379:6379 --name redis02 --net mynet -d redis
         $ docker -H tcp://192.168.33.21:2375 ps
 
-    These two commands are issued against the Swarm cluster. The commands specify *node constraints*, forcing Swarm to start the contaienrs on `frontend01` and `frontend02`. Port 6379 on each instance is mapped to port 6379 inside of each container for debugging purposes. The command also applies the `--restart=unless-stopped` policy to the containers and attaches them to the `mynet` overlay network.
+    These two commands are issued against the Swarm cluster. The commands specify *node constraints*, forcing Swarm to start the containers on `frontend01` and `frontend02`. Port 6379 on each instance is mapped to port 6379 inside of each container for debugging purposes. The command also applies the `--restart=unless-stopped` policy to the containers and attaches them to the `mynet` overlay network.
 
 5. Start a `web-vote-app` container the frontend nodes.
 
@@ -207,7 +207,7 @@ In the following steps, your launch several containers to the voting application
         $ docker run --restart=unless-stopped --env="constraint:node==frontend02" -d -p 5000:80 -e WEB_VOTE_NUMBER='02' --name frontend02 --net mynet --hostname votingapp.local web-vote-app
 
     These two commands are issued against the Swarm cluster. The commands
-    specify *node constraints*, forcing Swarm to start the contaienrs on
+    specify *node constraints*, forcing Swarm to start the containers on
     `frontend01` and `frontend02`. Port `5000` on each node is mapped to port
     `80` inside of each container. This allows connections to come in to each
     node on port `5000` and be forwarded to port `80` inside of each container.