Fix typos

Docker-DCO-1.1-Signed-off-by: Bryan Bess <squarejaw@bsbess.com> (github: squarejaw)

docs/man/Dockerfile.5.md

@@ -96,7 +96,7 @@ or
   If you use the shell form of the CMD, the <command> executes in /bin/sh -c:
   **FROM ubuntu**
   **CMD echo "This is a test." | wc -**
-  If you run <command> wihtout a shell, then you must express the command as a
+  If you run <command> without a shell, then you must express the command as a
   JSON arry and give the full path to the executable. This array form is the
   preferred form of CMD. All additional parameters must be individually expressed
   as strings in the array:

docs/man/docker-run.1.md

@@ -338,7 +338,7 @@ fedora-data image:
 
 Multiple --volumes-from parameters will bring together multiple data volumes from
 multiple containers. And it's possible to mount the volumes that came from the
-DATA container in yet another container via the fedora-container1 intermidiery
+DATA container in yet another container via the fedora-container1 intermediary
 container, allowing to abstract the actual data source from users of that data:
 
     # docker run --volumes-from=fedora-container1 --name=fedora-container2 -i -t fedora bash

docs/man/docker-tag.1.md

@@ -29,7 +29,7 @@ separated by a ':'
 
 **TAG**
    The tag you are assigning to the image.  Though this is arbitrary it is
-recommended to be used for a version to disinguish images with the same name.
+recommended to be used for a version to distinguish images with the same name.
 Note that here TAG is a part of the overall name or "tag".
 
 # OPTIONS

docs/sources/articles/runmetrics.md

@@ -365,7 +365,7 @@ container, we need to:
 Please review [*Enumerating Cgroups*](#enumerating-cgroups) to learn how to find
 the cgroup of a pprocess running in the container of which you want to
 measure network usage. From there, you can examine the pseudo-file named
-`tasks`, which containes the PIDs that are in the
+`tasks`, which contains the PIDs that are in the
 control group (i.e. in the container). Pick any one of them.
 
 Putting everything together, if the "short ID" of a container is held in

docs/sources/reference/api/docker_remote_api.md

@@ -100,7 +100,7 @@ after timestamp.
 
 `GET /containers/(id)/logs`
 
-This url is prefered method for getting container logs now.
+This url is preferred method for getting container logs now.
 
 ## v1.10
 
@@ -284,7 +284,7 @@ output is now generated in the client, using the
 
 **New!**
 You can now split stderr from stdout. This is done by
-prefixing a header to each transmition. See
+prefixing a header to each transmission. See
 [`POST /containers/(id)/attach`](
 /reference/api/docker_remote_api_v1.9/#post--containers-(id)-attach "POST /containers/(id)/attach").
 The WebSocket attach is unchanged. Note that attach calls on the

docs/sources/reference/run.md

@@ -385,7 +385,7 @@ container running Redis:
     $ docker port 4241164edf6f 6379
     2014/01/25 00:55:38 Error: No public port '6379' published for 4241164edf6f
 
-Yet we can get information about the Redis container'sexposed ports
+Yet we can get information about the Redis container's exposed ports
 with `--link`. Choose an alias that will form a
 valid environment variable!