Minor documentation edits for grammar and clarity

These are things I noticed as I read through the documentation.
There are a couple of minor substantive corrections as well.

website/source/docs/drivers/docker.html.md

@@ -102,7 +102,7 @@ The `docker` driver supports the following configuration in the job spec:
 * `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
   is `none` for a private IPC namespace. Other values are `host` for sharing
   the host IPC namespace or the name or id of an existing container. Note that
-  it is not possible to refer to Nomad started Docker containers since their
+  it is not possible to refer to Docker containers started by Nomad since their
   names are not known in advance. Note that setting this option also requires the
   Nomad agent to be configured to allow privileged containers.
 
@@ -339,11 +339,11 @@ The `docker` driver has the following [client configuration
 options](/docs/agent/config.html#options):
 
 * `docker.endpoint` - Defaults to `unix:///var/run/docker.sock`. You will need
-  to customize this if you use a non-standard socket (http or another
+  to customize this if you use a non-standard socket (HTTP or another
   location).
 
-* `docker.auth.config` - Allows an operator to specify a json file which is in
-  the dockercfg format containing authentication information for private registry.
+* `docker.auth.config` - Allows an operator to specify a JSON file which is in
+  the dockercfg format containing authentication information for a private registry.
 
 * `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
   this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
@@ -439,6 +439,7 @@ container does not exceed the amount of memory allocated to it, or it will be
 terminated or crash when it tries to malloc. A process can inspect its memory
 limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
 usage. Memory limit is expressed in megabytes so 1024 = 1Gb.
+HIO!!!
 
 ### IO
 

website/source/docs/drivers/exec.html.md

@@ -36,7 +36,7 @@ The `exec` driver supports the following configuration in the job spec:
   is downloaded from an [`artifact`](/docs/jobspec/index.html#artifact_doc), the
   path can be relative from the allocations's root directory.
 
-* `args` - (Optional) A list of arguments to the optional `command`. References
+* `args` - (Optional) A list of arguments to the `command`. References
   to environment variables or any [interpretable Nomad
   variables](/docs/jobspec/interpreted.html) will be interpreted before
   launching the task.

website/source/docs/drivers/java.html.md

@@ -34,7 +34,7 @@ The `java` driver supports the following configuration in the job spec:
   contains the Jar in a subfolder, the path will need to be the relative path
   (`subdir/from_archive/my.jar`).
 
-* `args` - (Optional) A list of arguments to the optional `command`. References
+* `args` - (Optional) A list of arguments to the Jar's main method. References
   to environment variables or any [interpretable Nomad
   variables](/docs/jobspec/interpreted.html) will be interpreted before
   launching the task.

website/source/docs/drivers/raw_exec.html.md

@@ -34,10 +34,10 @@ The `raw_exec` driver supports the following configuration in the job spec:
   is downloaded from an [`artifact`](/docs/jobspec/index.html#artifact_doc), the
   path can be relative from the allocations's root directory.
 
-* `args` - (Optional) A list of arguments to the optional `command`. References
+* `args` - (Optional) A list of arguments to the `command`. References
   to environment variables or any [interpretable Nomad
   variables](/docs/jobspec/interpreted.html) will be interpreted before
-  launching the task. For example:
+  launching the task.
 
 ## Examples