blindly make all uses of e\.?g\.? into e.g.,

Docker-DCO-1.1-Signed-off-by: SvenDowideit <SvenDowideit@home.org.au> (github: SvenDowideit)

docs/README.md

@@ -70,7 +70,7 @@ in their shell:
 
 ### Images
 
-When you need to add images, try to make them as small as possible (e.g. as
+When you need to add images, try to make them as small as possible (e.g., as
 gifs). Usually images should go in the same directory as the `.md` file which
 references them, or in a subdirectory if one already exists.
 

docs/man/docker-commit.1.md

@@ -14,7 +14,7 @@ Using an existing container's name or ID you can create a new image.
 
 # OPTIONS
 **-a, --author**=""
-   Author name. (e.g. "John Hannibal Smith <hannibal@a-team.com>"
+   Author name. (e.g., "John Hannibal Smith <hannibal@a-team.com>"
 
 **-m, --message**=""
    Commit message

docs/man/docker-images.1.md

@@ -17,7 +17,7 @@ docker-images - List the images in the local repository
 This command lists the images stored in the local Docker repository.
 
 By default, intermediate images, used during builds, are not listed. Some of the
-output, e.g. image ID, is truncated, for space reasons. However the truncated
+output, e.g., image ID, is truncated, for space reasons. However the truncated
 image ID, and often the first few characters, are enough to be used in other
 Docker commands that use the image ID. The output includes repository, tag, image
 ID, date created and the virtual size.

docs/man/docker-inspect.1.md

@@ -142,7 +142,7 @@ output:
 
 ## Getting information on an image
 
-Use an image's ID or name (e.g. repository/name[:tag]) to get information
+Use an image's ID or name (e.g., repository/name[:tag]) to get information
  on it.
 
     # docker inspect 58394af37342

docs/man/docker-pull.1.md

@@ -10,7 +10,7 @@ docker-pull - Pull an image or a repository from the registry
 # DESCRIPTION
 
 This command pulls down an image or a repository from the registry. If
-there is more than one image for a repository (e.g. fedora) then all
+there is more than one image for a repository (e.g., fedora) then all
 images for that repository name are pulled down including any tags.
 It is also possible to specify a non-default registry to pull from.
 

docs/man/docker-run.1.md

@@ -71,7 +71,7 @@ stopping the process by pressing the keys CTRL-P CTRL-Q.
 **--dns**=*IP-address*
    Set custom DNS servers. This option can be used to override the DNS
 configuration passed to the container. Typically this is necessary when the
-host DNS configuration is invalid for the container (e.g. 127.0.0.1). When this
+host DNS configuration is invalid for the container (e.g., 127.0.0.1). When this
 is the case the **-dns** flags is necessary for every run.
 
 

docs/man/docker-tag.1.md

@@ -35,7 +35,7 @@ Note that here TAG is a part of the overall name or "tag".
 
 ## Giving an image a new alias
 
-Here is an example of aliasing an image (e.g. 0e5574283393) as "httpd" and 
+Here is an example of aliasing an image (e.g., 0e5574283393) as "httpd" and 
 tagging it into the "fedora" repository with "version1.0":
 
     docker tag 0e5574283393 fedora/httpd:version1.0

docs/sources/articles/cfengine_process_management.md

@@ -87,7 +87,7 @@ The first two steps can be done as part of a Dockerfile, as follows.
     ENTRYPOINT ["/var/cfengine/bin/docker_processes_run.sh"]
 
 By saving this file as Dockerfile to a working directory, you can then build
-your image with the docker build command, e.g.
+your image with the docker build command, e.g.,
 `docker build -t managed_image`.
 
 ### Testing the container

docs/sources/articles/https.md

@@ -29,7 +29,7 @@ keys:
     $ openssl req -new -x509 -days 365 -key ca-key.pem -out ca.pem
 
 Now that we have a CA, you can create a server key and certificate
-signing request. Make sure that "Common Name (e.g. server FQDN or YOUR
+signing request. Make sure that "Common Name (e.g., server FQDN or YOUR
 name)" matches the hostname you will use to connect to Docker or just
 use `\*` for a certificate valid for any hostname:
 

docs/sources/articles/runmetrics.md

@@ -35,7 +35,7 @@ known to the system, the hierarchy they belong to, and how many groups they cont
 
 You can also look at `/proc/<pid>/cgroup` to see which control groups a process
 belongs to. The control group will be shown as a path relative to the root of
-the hierarchy mountpoint; e.g. `/` means “this process has not been assigned into
+the hierarchy mountpoint; e.g., `/` means “this process has not been assigned into
 a particular group”, while `/lxc/pumpkin` means that the process is likely to be
 a member of a container named `pumpkin`.
 
@@ -106,9 +106,9 @@ to the processes within the cgroup, excluding sub-cgroups. The second half
 (with the `total_` prefix) includes sub-cgroups as well.
 
 Some metrics are "gauges", i.e. values that can increase or decrease
-(e.g. swap, the amount of swap space used by the members of the cgroup).
+(e.g., swap, the amount of swap space used by the members of the cgroup).
 Some others are "counters", i.e. values that can only go up, because
-they represent occurrences of a specific event (e.g. pgfault, which
+they represent occurrences of a specific event (e.g., pgfault, which
 indicates the number of page faults which happened since the creation of
 the cgroup; this number can never decrease).
 
@@ -410,7 +410,7 @@ used.
 
 Docker makes this difficult because it relies on `lxc-start`, which
 carefully cleans up after itself, but it is still possible. It is
-usually easier to collect metrics at regular intervals (e.g. every
+usually easier to collect metrics at regular intervals (e.g., every
 minute, with the collectd LXC plugin) and rely on that instead.
 
 But, if you'd still like to gather the stats when a container stops,

docs/sources/articles/security.md

@@ -91,8 +91,8 @@ without any restriction. This sounds crazy? Well, you have to know that
 same way**. Nothing prevents you from sharing your root filesystem (or
 even your root block device) with a virtual machine.
 
-This has a strong security implication: if you instrument Docker from
-e.g. a web server to provision containers through an API, you should be
+This has a strong security implication: for example, if you instrument Docker
+from a web server to provision containers through an API, you should be
 even more careful than usual with parameter checking, to make sure that
 a malicious user cannot pass crafted parameters causing Docker to create
 arbitrary containers.
@@ -108,7 +108,7 @@ socket.
 You can also expose the REST API over HTTP if you explicitly decide so.
 However, if you do that, being aware of the above mentioned security
 implication, you should ensure that it will be reachable only from a
-trusted network or VPN; or protected with e.g. `stunnel` and client SSL
+trusted network or VPN; or protected with e.g., `stunnel` and client SSL
 certificates. You can also secure them with [HTTPS and
 certificates](/articles/https/).
 
@@ -136,7 +136,7 @@ Finally, if you run Docker on a server, it is recommended to run
 exclusively Docker in the server, and move all other services within
 containers controlled by Docker. Of course, it is fine to keep your
 favorite admin tools (probably at least an SSH server), as well as
-existing monitoring/supervision processes (e.g. NRPE, collectd, etc).
+existing monitoring/supervision processes (e.g., NRPE, collectd, etc).
 
 ## Linux Kernel Capabilities
 
@@ -154,8 +154,8 @@ This means a lot for container security; let's see why!
 
 Your average server (bare metal or virtual machine) needs to run a bunch
 of processes as root. Those typically include SSH, cron, syslogd;
-hardware management tools (to e.g. load modules), network configuration
-tools (to handle e.g. DHCP, WPA, or VPNs), and much more. A container is
+hardware management tools (e.g., load modules), network configuration
+tools (e.g., to handle DHCP, WPA, or VPNs), and much more. A container is
 very different, because almost all of those tasks are handled by the
 infrastructure around the container:
 
@@ -232,7 +232,7 @@ harden a Docker host. Here are a few examples.
    mechanism.
 
 Just like there are many third-party tools to augment Docker containers
-with e.g. special network topologies or shared filesystems, you can
+with e.g., special network topologies or shared filesystems, you can
 expect to see tools to harden existing Docker containers without
 affecting Docker's core.
 

docs/sources/contributing/devenvironment.md

@@ -113,7 +113,7 @@ something like this
     ok      github.com/dotcloud/docker/utils        0.017s
 
 If $TESTFLAGS is set in the environment, it is passed as extra arguments
-to `go test`. You can use this to select certain tests to run, e.g.
+to `go test`. You can use this to select certain tests to run, e.g.,
 
     $ TESTFLAGS=`-run \^TestBuild\$` make test
 

docs/sources/installation/rackspace.md

@@ -15,7 +15,7 @@ will need to install it. And this is a little more difficult on
 Rackspace.
 
 Rackspace boots their servers using grub's `menu.lst`
-and does not like non `virtual` packages (e.g. Xen compatible)
+and does not like non `virtual` packages (e.g., Xen compatible)
 kernels there, although they do work. This results in
 `update-grub` not having the expected result, and
 you will need to set the kernel manually.

docs/sources/reference/api/docker_remote_api.md

@@ -373,7 +373,7 @@ List containers (/containers/json):
 
 Start containers (/containers/<id>/start):
 
- - You can now pass host-specific configuration (e.g. bind mounts) in
+ - You can now pass host-specific configuration (e.g., bind mounts) in
    the POST body for start calls
 
 ## v1.2

docs/sources/reference/api/docker_remote_api_v1.0.md

@@ -935,7 +935,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.1.md

@@ -946,7 +946,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.10.md

@@ -286,7 +286,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps\_args** – ps arguments to use (e.g. aux)
+    -   **ps\_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1181,7 +1181,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.11.md

@@ -290,7 +290,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1223,7 +1223,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.12.md

@@ -290,7 +290,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1301,7 +1301,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.13.md

@@ -290,7 +290,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1304,7 +1304,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.2.md

@@ -959,7 +959,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.3.md

@@ -1009,7 +1009,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.4.md

@@ -264,7 +264,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1055,7 +1055,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.5.md

@@ -261,7 +261,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1067,7 +1067,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.6.md

@@ -311,7 +311,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1163,7 +1163,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/docker_remote_api_v1.7.md

@@ -267,7 +267,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1112,7 +1112,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
     -   **run** – config automatically applied when the image is run.
         (ex: {"Cmd": ["cat", "/world"], "PortSpecs":["22"]})

docs/sources/reference/api/docker_remote_api_v1.8.md

@@ -303,7 +303,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1157,7 +1157,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
     -   **run** – config automatically applied when the image is run.
         (ex: {"Cmd": ["cat", "/world"], "PortSpecs":["22"]})

docs/sources/reference/api/docker_remote_api_v1.9.md

@@ -303,7 +303,7 @@ List processes running inside the container `id`
 
      
 
-    -   **ps_args** – ps arguments to use (e.g. aux)
+    -   **ps_args** – ps arguments to use (e.g., aux)
 
     Status Codes:
 
@@ -1194,7 +1194,7 @@ Create a new image from a container's changes
     -   **repo** – repository
     -   **tag** – tag
     -   **m** – commit message
-    -   **author** – author (e.g. "John Hannibal Smith
+    -   **author** – author (e.g., "John Hannibal Smith
         <[hannibal@a-team.com](mailto:hannibal%40a-team.com)>")
 
     Status Codes:

docs/sources/reference/api/hub_registry_spec.md

@@ -77,11 +77,11 @@ grasp the context, here are some examples of registries:
 > - local mount point;
 > - remote docker addressed through SSH.
 
-The latter would only require two new commands in docker, e.g.
+The latter would only require two new commands in docker, e.g.,
 `registryget` and `registryput`,
 wrapping access to the local filesystem (and optionally doing
 consistency checks). Authentication and authorization are then delegated
-to SSH (e.g. with public keys).
+to SSH (e.g., with public keys).
 
 ### Docker
 

docs/sources/reference/api/registry_api.md

@@ -62,10 +62,10 @@ grasp the context, here are some examples of registries:
 >  - local mount point;
 >  - remote docker addressed through SSH.
 
-The latter would only require two new commands in docker, e.g.
+The latter would only require two new commands in docker, e.g.,
 `registryget` and `registryput`, wrapping access to the local filesystem
 (and optionally doing consistency checks). Authentication and authorization
-are then delegated to SSH (e.g. with public keys).
+are then delegated to SSH (e.g., with public keys).
 
 # Endpoints
 

docs/sources/reference/commandline/cli.md

@@ -335,7 +335,7 @@ schema.
 
     Create a new image from a container's changes
 
-      -a, --author=""     Author (eg. "John Hannibal Smith <hannibal@a-team.com>")
+      -a, --author=""     Author (e.g., "John Hannibal Smith <hannibal@a-team.com>")
       -m, --message=""    Commit message
 
 It can be useful to commit a container's file changes or settings into a
@@ -518,7 +518,7 @@ by default.
 ### Filtering
 
 The filtering flag (`-f` or `--filter`) format is of "key=value". If there are more
-than one filter, then pass multiple flags (e.g. `--filter "foo=bar" --filter "bif=baz"`)
+than one filter, then pass multiple flags (e.g., `--filter "foo=bar" --filter "bif=baz"`)
 
 Current filters:
  * dangling (boolean - true or false)
@@ -929,7 +929,7 @@ removed before the image is removed.
       --sig-proxy=true           Proxify received signals to the process (even in non-tty mode). SIGCHLD is not proxied.
       -t, --tty=false            Allocate a pseudo-tty
       -u, --user=""              Username or UID
-      -v, --volume=[]            Bind mount a volume (e.g. from the host: -v /host:/container, from docker: -v /container)
+      -v, --volume=[]            Bind mount a volume (e.g., from the host: -v /host:/container, from docker: -v /container)
       --volumes-from=[]          Mount volumes from the specified container(s)
       -w, --workdir=""           Working directory inside the container
 

docs/sources/terms/repository.md

@@ -13,10 +13,10 @@ server.
 Images can be associated with a repository (or multiple) by giving them
 an image name using one of three different commands:
 
-1. At build time (e.g. `sudo docker build -t IMAGENAME`),
-2. When committing a container (e.g.
+1. At build time (e.g., `sudo docker build -t IMAGENAME`),
+2. When committing a container (e.g.,
    `sudo docker commit CONTAINERID IMAGENAME`) or
-3. When tagging an image id with an image name (e.g.
+3. When tagging an image id with an image name (e.g.,
    `sudo docker tag IMAGEID IMAGENAME`).
 
 A Fully Qualified Image Name (FQIN) can be made up of 3 parts: