Spelling revision

README.md

@@ -307,7 +307,7 @@ In order to keep the Git repository light, _please_ compress the images
 (losslessly).  On Mac you may use (ImageOptim)[https://imageoptim.com] for
 instance.  Be sure to compress the images *before* adding them to the
 repository, doing it afterwards actually worsens the impact on the Git repo (but
-still optimizes the bandwith during browsing).
+still optimizes the bandwidth during browsing).
 
 ## Building archives and the live published docs
 

apidocs/cloud-api-source/source/includes/container.md

@@ -303,7 +303,7 @@ memory | The memory limit of the container in MB (see [Runtime Constraints on CP
 memory_swap | Total memory limit (memory + swap) of the container in MB
 autorestart | Whether to restart the container automatically if it stops (see [Crash recovery](/docker-cloud/apps/autorestart/) for more information)
 autodestroy | Whether to terminate the container automatically if it stops (see [Autodestroy](/docker-cloud/apps/auto-destroy/) for more information)
-roles | List of Docker Cloud roles asigned to this container (see [API roles](/docker-cloud/apps/api-roles/) for more information))
+roles | List of Docker Cloud roles assigned to this container (see [API roles](/docker-cloud/apps/api-roles/) for more information))
 linked_to_container | List of IP addresses of the linked containers (see table `Container Link attributes` below and [Service links](/docker-cloud/apps/service-links/) for more information)
 link_variables | List of environment variables that would be exposed in any container that is linked to this one
 privileged | Whether the container has Docker's `privileged` flag set or not (see [Runtime privilege](/engine/reference/run/#runtime-privilege-linux-capabilities-and-lxc-configuration) for more information)

apidocs/cloud-api-source/source/javascripts/lib/_jquery.highlight.js

@@ -11,7 +11,7 @@
  *  - highlight element tag and class names can be specified in options
  *
  * Usage:
- *   // wrap every occurrance of text 'lorem' in content
+ *   // wrap every occurrence of text 'lorem' in content
  *   // with <span class='highlight'> (default options)
  *   $('#content').highlight('lorem');
  *
@@ -26,7 +26,7 @@
  *   // don't ignore case during search of term 'lorem'
  *   $('#content').highlight('lorem', { caseSensitive: true });
  *
- *   // wrap every occurrance of term 'ipsum' in content
+ *   // wrap every occurrence of term 'ipsum' in content
  *   // with <em class='important'>
  *   $('#content').highlight('ipsum', { element: 'em', className: 'important' });
  *

apidocs/cloud-api-source/source/javascripts/lib/_jquery.tocify.js

@@ -858,7 +858,7 @@
 
             }
 
-            // Maintains chainablity
+            // Maintains chainability
             return self;
 
         },
@@ -911,7 +911,7 @@
 
             }
 
-            // Maintains chainablity
+            // Maintains chainability
             return self;
         },
 

apidocs/cloud-api-source/source/javascripts/lib/_lunr.js

@@ -1667,7 +1667,7 @@
 
   /**
    * lunr.trimmer is a pipeline function for trimming non word
-   * characters from the begining and end of tokens before they
+   * characters from the beginning and end of tokens before they
    * enter the index.
    *
    * This implementation may not work correctly for non latin
@@ -1891,7 +1891,7 @@
     } else if (typeof exports === 'object') {
       /**
        * Node. Does not work with strict CommonJS, but
-       * only CommonJS-like enviroments that support module.exports,
+       * only CommonJS-like environments that support module.exports,
        * like Node.
        */
       module.exports = factory()

apidocs/docker-cloud/includes/action.html

@@ -62,7 +62,7 @@ <h2 id="action">Action</h2>
 
 <p>An action represents an API call by a user. Details of the API call such as timestamp, origin IP address, and user agent are logged in the action object.</p>
 
-<p>Simple API calls that do not require asynchronous execution will return immediately with the appropiate HTTP error code and an action object will be created either in <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> states. API calls that do require asynchronous execution will return HTTP code <code class="prettyprint">202 Accepted</code> immediately and create an action object in <code class="prettyprint">In progress</code> state, which will change to <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> state depending on the outcome of the operation being performed. In both cases the response will include a <code class="prettyprint">X-DockerCloud-Action-URI</code> header with the resource URI of the created action.</p>
+<p>Simple API calls that do not require asynchronous execution will return immediately with the appropriate HTTP error code and an action object will be created either in <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> states. API calls that do require asynchronous execution will return HTTP code <code class="prettyprint">202 Accepted</code> immediately and create an action object in <code class="prettyprint">In progress</code> state, which will change to <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> state depending on the outcome of the operation being performed. In both cases the response will include a <code class="prettyprint">X-DockerCloud-Action-URI</code> header with the resource URI of the created action.</p>
 
 <h3 id="attributes">Attributes</h3>
 

apidocs/docker-cloud/includes/container.html

@@ -470,7 +470,7 @@ <h3 id="attributes">Attributes</h3>
 </tr>
 <tr>
 <td>roles</td>
-<td>List of Docker Cloud roles asigned to this container (see <a href="/docker-cloud/apps/api-roles/">API roles</a> for more information))</td>
+<td>List of Docker Cloud roles assigned to this container (see <a href="/docker-cloud/apps/api-roles/">API roles</a> for more information))</td>
 </tr>
 <tr>
 <td>linked_to_container</td>

apidocs/docker-cloud/includes/dockercloud-events.html

@@ -81,7 +81,7 @@ <h3 id="attributes">Attributes</h3>
 </tr>
 <tr>
 <td style="text-align: left">action</td>
-<td style="text-align: left">Type of action that was executed on the object. Posible values: <code class="prettyprint">create</code>, <code class="prettyprint">update</code> or <code class="prettyprint">delete</code></td>
+<td style="text-align: left">Type of action that was executed on the object. Possible values: <code class="prettyprint">create</code>, <code class="prettyprint">update</code> or <code class="prettyprint">delete</code></td>
 </tr>
 <tr>
 <td style="text-align: left">parents</td>

apidocs/docker-cloud/includes/nodecluster.html

@@ -200,7 +200,7 @@ <h3 id="provider-options">Provider options</h3>
 
 <ul>
 <li><code class="prettyprint">id</code>: AWS VPC identifier of the target VPC where the nodes of the cluster will be deployed (required)</li>
-<li><code class="prettyprint">subnets</code>: a list of target subnet indentifiers inside selected VPC. If you specify more than one subnet, Docker Cloud will balance among all of them following a high-availability schema (optional)</li>
+<li><code class="prettyprint">subnets</code>: a list of target subnet identifiers inside selected VPC. If you specify more than one subnet, Docker Cloud will balance among all of them following a high-availability schema (optional)</li>
 <li><code class="prettyprint">security_groups</code>: the security group that will be applied to every node of the cluster (optional)</li>
 </ul></li>
 <li><code class="prettyprint">iam</code>: IAM-related options (optional)

apidocs/layouts/single.html

@@ -208,7 +208,7 @@ <h2 id="action">Action</h2>
 
 <p>An action represents an API call by a user. Details of the API call such as timestamp, origin IP address, and user agent are logged in the action object.</p>
 
-<p>Simple API calls that do not require asynchronous execution will return immediately with the appropiate HTTP error code and an action object will be created either in <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> states. API calls that do require asynchronous execution will return HTTP code <code class="prettyprint">202 Accepted</code> immediately and create an action object in <code class="prettyprint">In progress</code> state, which will change to <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> state depending on the outcome of the operation being performed. In both cases the response will include a <code class="prettyprint">X-DockerCloud-Action-URI</code> header with the resource URI of the created action.</p>
+<p>Simple API calls that do not require asynchronous execution will return immediately with the appropriate HTTP error code and an action object will be created either in <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> states. API calls that do require asynchronous execution will return HTTP code <code class="prettyprint">202 Accepted</code> immediately and create an action object in <code class="prettyprint">In progress</code> state, which will change to <code class="prettyprint">Success</code> or <code class="prettyprint">Failed</code> state depending on the outcome of the operation being performed. In both cases the response will include a <code class="prettyprint">X-DockerCloud-Action-URI</code> header with the resource URI of the created action.</p>
 
 <h3 id="attributes">Attributes</h3>
 
@@ -1450,7 +1450,7 @@ <h3 id="provider-options">Provider options</h3>
 
 <ul>
 <li><code class="prettyprint">id</code>: AWS VPC identifier of the target VPC where the nodes of the cluster will be deployed (required)</li>
-<li><code class="prettyprint">subnets</code>: a list of target subnet indentifiers inside selected VPC. If you specify more than one subnet, Docker Cloud will balance among all of them following a high-availability schema (optional)</li>
+<li><code class="prettyprint">subnets</code>: a list of target subnet identifiers inside selected VPC. If you specify more than one subnet, Docker Cloud will balance among all of them following a high-availability schema (optional)</li>
 <li><code class="prettyprint">security_groups</code>: the security group that will be applied to every node of the cluster (optional)</li>
 </ul></li>
 <li><code class="prettyprint">iam</code>: IAM-related options (optional)
@@ -5263,7 +5263,7 @@ <h3 id="attributes">Attributes</h3>
 </tr>
 <tr>
 <td>roles</td>
-<td>List of Docker Cloud roles asigned to this container (see <a href="/docker-cloud/apps/api-roles/">API roles</a> for more information))</td>
+<td>List of Docker Cloud roles assigned to this container (see <a href="/docker-cloud/apps/api-roles/">API roles</a> for more information))</td>
 </tr>
 <tr>
 <td>linked_to_container</td>
@@ -6326,7 +6326,7 @@ <h3 id="attributes">Attributes</h3>
 </tr>
 <tr>
 <td style="text-align: left">action</td>
-<td style="text-align: left">Type of action that was executed on the object. Posible values: <code class="prettyprint">create</code>, <code class="prettyprint">update</code> or <code class="prettyprint">delete</code></td>
+<td style="text-align: left">Type of action that was executed on the object. Possible values: <code class="prettyprint">create</code>, <code class="prettyprint">update</code> or <code class="prettyprint">delete</code></td>
 </tr>
 <tr>
 <td style="text-align: left">parents</td>

compose/aspnet-mssql-compose.md

@@ -186,7 +186,7 @@ configure this app to use our SQL Server database, and then create a
     Go ahead and try out the website! This sample uses the SQL Server
     database image in the back-end for authentication.
 
-Ready! You now have a ASP.NET Core application running against SQL Server in
+Ready! You now have an ASP.NET Core application running against SQL Server in
 Docker Compose! This sample made use of some of the most popular Microsoft
 products for Linux. To learn more about Windows Containers, check out
 [Docker Labs for Windows Containers](https://github.com/docker/labs/tree/master/windows)

compose/compose-file/compose-file-v1.md

@@ -415,7 +415,7 @@ id.
 Sets the PID mode to the host PID mode. This turns on sharing between
 container and the host operating system the PID address space. Containers
 launched with this flag can access and manipulate other
-containers in the bare-metal machine's namespace and vise-versa.
+containers in the bare-metal machine's namespace and vice versa.
 
 ### ports
 

compose/compose-file/compose-file-v2.md

@@ -1006,7 +1006,7 @@ designated container or service.
 If set to "host", the service's PID mode is the host PID mode.  This turns
 on sharing between container and the host operating system the PID address
 space. Containers launched with this flag can access and manipulate
-other containers in the bare-metal machine's namespace and vise-versa.
+other containers in the bare-metal machine's namespace and vice versa.
 
 > **Note**: the `service:` and `container:` forms require
 > [version 2.1](compose-versioning.md#version-21) or above
@@ -1483,7 +1483,7 @@ Set a custom name for this volume.
       data:
         name: my-app-data
 
-It can also be used in conjuction with the `external` property:
+It can also be used in conjunction with the `external` property:
 
     version: '2.1'
     volumes:
@@ -1641,7 +1641,7 @@ Set a custom name for this network.
       network1:
         name: my-app-net
 
-It can also be used in conjuction with the `external` property:
+It can also be used in conjunction with the `external` property:
 
     version: '2.1'
     networks:

compose/compose-file/index.md

@@ -1409,7 +1409,7 @@ networks:
 Sets the PID mode to the host PID mode.  This turns on sharing between
 container and the host operating system the PID address space.  Containers
 launched with this flag can access and manipulate other
-containers in the bare-metal machine's namespace and vise-versa.
+containers in the bare-metal machine's namespace and vice versa.
 
 ### ports
 
@@ -2029,7 +2029,7 @@ and will **not** be scoped with the stack name.
       data:
         name: my-app-data
 
-It can also be used in conjuction with the `external` property:
+It can also be used in conjunction with the `external` property:
 
     version: '3.4'
     volumes:
@@ -2257,7 +2257,7 @@ and will **not** be scoped with the stack name.
       network1:
         name: my-app-net
 
-It can also be used in conjuction with the `external` property:
+It can also be used in conjunction with the `external` property:
 
     version: '3.5'
     networks:

compose/rails.md

@@ -230,7 +230,7 @@ web_1 | A server is already
 running. Check /myapp/tmp/pids/server.pid.
 ```
 
-To resolve this, delete the file `tmp/pids/server.pid`, and then re-start the
+To resolve this, delete the file `tmp/pids/server.pid`, and then restart the
 application with `docker-compose up`.
 
 ### Restart the application

config/containers/logging/splunk.md

@@ -49,7 +49,7 @@ The following properties let you configure the splunk logging driver.
 
 - To configure the `splunk` driver across the Docker environment, edit
   `daemon.json` with the key, `"log-opts": {"NAME": "VALUE", ...}`.
-- To configure the `splunk` driver for an indiviual container, use `docker run`
+- To configure the `splunk` driver for an individual container, use `docker run`
   with the flag, `--log-opt NAME=VALUE ...`.
 
 | Option                      | Required | Description                                                                                                                                                                                                                                                                                                                                 |

datacenter/dtr/2.0/install/upgrade/index.md

@@ -11,7 +11,7 @@ is ensuring you're running DTR 2.0. If that's not the case, start by upgrading
 your installation to version 2.0.0, and then upgrade to the latest version
 available.
 
-There is no downtime when upgrading an highly-available DTR cluster. If your
+There is no downtime when upgrading a highly-available DTR cluster. If your
 DTR deployment has a single replica, schedule the upgrade to take place outside
 business peak hours to ensure the impact on your business is close to none.
 

datacenter/dtr/2.1/guides/install/upgrade.md

@@ -9,7 +9,7 @@ is ensuring you're running DTR 2.0. If that's not the case, start by upgrading
 your installation to version 2.0.0, and then upgrade to the latest version
 available.
 
-There is no downtime when upgrading an highly-available DTR cluster. If your
+There is no downtime when upgrading a highly-available DTR cluster. If your
 DTR deployment has a single replica, schedule the upgrade to take place outside
 business peak hours to ensure the impact on your business is close to none.
 

datacenter/dtr/2.1/reference/api/swagger-ui.js

@@ -2121,7 +2121,7 @@ SuperagentHttpClient.prototype.execute = function (obj) {
     } else if (res && obj.on && obj.on.response) {
       var possibleObj;
 
-      // Already parsed by by superagent?
+      // Already parsed by superagent?
       if(res.body && Object.keys(res.body).length > 0) {
         possibleObj = res.body;
       } else {
@@ -12442,7 +12442,7 @@ var iframe,
 	elemdisplay = {};
 
 /**
- * Retrieve the actual display of a element
+ * Retrieve the actual display of an element
  * @param {String} name nodeName of the element
  * @param {Object} doc Document object
  */
@@ -13862,7 +13862,7 @@ jQuery.fx.speeds = {
 };
 
 
-// Based off of the plugin by Clint Helfers, with permission.
+// Based on the plugin by Clint Helfers, with permission.
 // http://blindsignals.com/index.php/2009/07/jquery-delay/
 jQuery.fn.delay = function( time, type ) {
 	time = jQuery.fx ? jQuery.fx.speeds[ time ] || time : time;
@@ -26068,7 +26068,7 @@ var baseCreate = require('./baseCreate'),
  * @private
  * @param {*} value The value to wrap.
  * @param {boolean} [chainAll] Enable chaining for all wrapper methods.
- * @param {Array} [actions=[]] Actions to peform to resolve the unwrapped value.
+ * @param {Array} [actions=[]] Actions to perform to resolve the unwrapped value.
  */
 function LodashWrapper(value, chainAll, actions) {
   this.__wrapped__ = value;

datacenter/dtr/2.2/guides/admin/configure/external-storage/s3.md

@@ -24,7 +24,7 @@ Start by
 Then, as a best practice you should
 [create a new IAM user](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html)
 just for the DTR
-integration and apply a IAM policy that ensures the user has limited permissions.
+integration and apply an IAM policy that ensures the user has limited permissions.
 
 This user only needs permissions to access the bucket that you use to store
 images, and to read, write, and delete files.

datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md

@@ -18,7 +18,7 @@ pushes will fail
 
 The GC cron schedule is set to run in **UTC time**. Containers typically run in
 UTC time (unless the system time is mounted), therefore remember that the cron
-schedule will run based off of UTC time when configuring.
+schedule will run based on UTC time when configuring.
 
 GC puts DTR into read-only mode; pulls succeed while pushes fail. Pushing an
 image while GC runs may lead to undefined behavior and data loss, therefore

datacenter/dtr/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-batch-jobs.md

@@ -68,7 +68,7 @@ Jobs can be in one of the following status:
 
 ## Job capacity
 
-Each job runner has a limited capacity and doesn't claim jobs that require an
+Each job runner has a limited capacity and doesn't claim jobs that require a
 higher capacity. You can see the capacity of a job runner using the
 `GET /api/v0/workers` endpoint: