From 7b90ef4bdcf39c61a7ea3c81a9cff158484f3355 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Tue, 21 Mar 2017 11:49:07 -0700 Subject: [PATCH] Fix spelling errors (#2409) --- datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache.md | 2 +- datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md | 2 +- datacenter/dtr/2.2/guides/release-notes/index.md | 2 +- datacenter/ucp/1.1/installation/install-production.md | 2 +- .../ucp/2.0/guides/content-trust/continuous-integration.md | 2 +- .../guides/high-availability/backups-and-disaster-recovery.md | 2 +- .../ucp/2.1/guides/admin/backups-and-disaster-recovery.md | 2 +- .../guides/admin/configure/restrict-services-to-worker-nodes.md | 2 +- .../ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md | 2 +- datacenter/ucp/2.1/guides/release-notes/index.md | 2 +- docker-cloud/cloud-swarm/register-swarms.md | 2 +- docker-for-azure/faqs.md | 2 +- docker-for-windows/index.md | 2 +- engine/swarm/services.md | 2 +- engine/swarm/swarm-mode.md | 2 +- engine/userguide/storagedriver/imagesandcontainers.md | 2 +- kitematic/known-issues.md | 2 +- kitematic/userguide.md | 2 +- opensource/project/set-up-dev-env.md | 2 +- registry/recipes/apache.md | 2 +- 20 files changed, 20 insertions(+), 20 deletions(-) diff --git a/datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache.md b/datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache.md index 5267e1b186..75d56f7232 100644 --- a/datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache.md +++ b/datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache.md @@ -96,7 +96,7 @@ docker run --detach --restart always \ docker/dtr-content-cache: /config.yml ``` -You can also run the command in interactive mode instead of detatched by +You can also run the command in interactive mode instead of detached by replacing `--detached` with `--interactive`. This allows you to see the logs generated by the container and troubleshoot misconfigurations. diff --git a/datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md b/datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md index 7d903fe279..0b85fd4517 100644 --- a/datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md +++ b/datacenter/dtr/2.2/guides/admin/configure/garbage-collection.md @@ -21,7 +21,7 @@ UTC time (unless the system time is mounted), therefore remember that the cron schedule will run based off of 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 behaviour and data loss, therefore +image while GC runs may lead to undefined behavior and data loss, therefore this is disabled for safety. For this reason it's generally best practice to ensure GC runs in the early morning on a Saturday or Sunday night. diff --git a/datacenter/dtr/2.2/guides/release-notes/index.md b/datacenter/dtr/2.2/guides/release-notes/index.md index 9c71a928cf..3788f91328 100644 --- a/datacenter/dtr/2.2/guides/release-notes/index.md +++ b/datacenter/dtr/2.2/guides/release-notes/index.md @@ -24,7 +24,7 @@ to upgrade your installation to the latest release. * Several improvements to the installer to make it more resilient * Improved the installer to better detect port conflicts when installing or joining DTR replicas -* Security scans can now be cancelled +* Security scans can now be canceled * DTR job logs are now stored in the DTR datastore but also sent to Docker Engine **Bugs fixed** diff --git a/datacenter/ucp/1.1/installation/install-production.md b/datacenter/ucp/1.1/installation/install-production.md index 6b6ed01d6f..ab1703c379 100644 --- a/datacenter/ucp/1.1/installation/install-production.md +++ b/datacenter/ucp/1.1/installation/install-production.md @@ -57,7 +57,7 @@ browsers and client tools already trust. If you want to use your own certificates: -1. Log into the host where you intend to instal UCP. +1. Log into the host where you intend to install UCP. 2. Create a volume with the name `ucp-controller-server-certs`. diff --git a/datacenter/ucp/2.0/guides/content-trust/continuous-integration.md b/datacenter/ucp/2.0/guides/content-trust/continuous-integration.md index 6ef5e0160a..cdf4f4d816 100644 --- a/datacenter/ucp/2.0/guides/content-trust/continuous-integration.md +++ b/datacenter/ucp/2.0/guides/content-trust/continuous-integration.md @@ -35,7 +35,7 @@ In this case, the only member is the "jenkins" user. The signing policy implementation uses the certificates issued in user client bundles to connect a signature to a user. Using an incognito browser window (or otherwise), log in to the "jenkins" user account you created earlier. Download a client bundle for -this user. It is also recommeneded to change the description associated with the public +this user. It is also recommended to change the description associated with the public key stored in UCP such that you can identify in the future which key is being used for signing. diff --git a/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md b/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md index 926bfad466..5b8ab96d23 100644 --- a/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md +++ b/datacenter/ucp/2.0/guides/high-availability/backups-and-disaster-recovery.md @@ -90,7 +90,7 @@ You should now have your UCP cluster up and running. Additionally, in the event where half or more controller nodes are lost and cannot be recovered to a healthy state, the system can only be restored through the following disaster recovery procedure. It is important to note that this -proceedure is not guaranteed to succeed with no loss of either swarm services or +procedure is not guaranteed to succeed with no loss of either swarm services or UCP configuration data: 1. On one of the remaining manager nodes, perform `docker swarm init diff --git a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md index 00d75ff1f7..422717eee3 100644 --- a/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md +++ b/datacenter/ucp/2.1/guides/admin/backups-and-disaster-recovery.md @@ -130,7 +130,7 @@ In the event where half or more manager nodes are lost and cannot be recovered to a healthy state, the system is considered to have lost quorum and can only be restored through the following disaster recovery procedure. -It is important to note that this proceedure is not guaranteed to succeed with +It is important to note that this procedure is not guaranteed to succeed with no loss of running services or configuration data. To properly protect against manager failures, the system should be configured for [high availability](configure/set-up-high-availability.md). diff --git a/datacenter/ucp/2.1/guides/admin/configure/restrict-services-to-worker-nodes.md b/datacenter/ucp/2.1/guides/admin/configure/restrict-services-to-worker-nodes.md index 3e3320aba4..23ba274234 100644 --- a/datacenter/ucp/2.1/guides/admin/configure/restrict-services-to-worker-nodes.md +++ b/datacenter/ucp/2.1/guides/admin/configure/restrict-services-to-worker-nodes.md @@ -12,7 +12,7 @@ If a user deploys a malicious service that can affect the node where it is running, they won't be able to affect other nodes in the cluster, or any cluster management functionality. -To restrict users from deploying to manager nodes, log in with adminstrator +To restrict users from deploying to manager nodes, log in with administrator credentials to the **UCP web UI**, navigate to the **Admin Settings** page, and choose **Scheduler**. diff --git a/datacenter/ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md b/datacenter/ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md index 6ef5e0160a..cdf4f4d816 100644 --- a/datacenter/ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md +++ b/datacenter/ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md @@ -35,7 +35,7 @@ In this case, the only member is the "jenkins" user. The signing policy implementation uses the certificates issued in user client bundles to connect a signature to a user. Using an incognito browser window (or otherwise), log in to the "jenkins" user account you created earlier. Download a client bundle for -this user. It is also recommeneded to change the description associated with the public +this user. It is also recommended to change the description associated with the public key stored in UCP such that you can identify in the future which key is being used for signing. diff --git a/datacenter/ucp/2.1/guides/release-notes/index.md b/datacenter/ucp/2.1/guides/release-notes/index.md index d260d63fcd..e8807489f8 100644 --- a/datacenter/ucp/2.1/guides/release-notes/index.md +++ b/datacenter/ucp/2.1/guides/release-notes/index.md @@ -28,7 +28,7 @@ You can either wait for UCP 2.1.2 to be released so that the problem is automatically fixed, or upgrade to 2.1.1, and use the following steps to fix the problem. -Star by getting the current configuration for user sessions by running: +Start by getting the current configuration for user sessions by running: ```bash curl -u admin "https://$UCP_HOST/enzi/v0/config/sessions" diff --git a/docker-cloud/cloud-swarm/register-swarms.md b/docker-cloud/cloud-swarm/register-swarms.md index 101101624d..619984fb53 100644 --- a/docker-cloud/cloud-swarm/register-swarms.md +++ b/docker-cloud/cloud-swarm/register-swarms.md @@ -78,7 +78,7 @@ Swarms that are registered in Docker Cloud appear in the Swarms list. Each line - **DEPLOYED**: the swarm is sending heartbeat pings to Docker Cloud, and Cloud can contact it to run a health check. -- **UNREACHABLE**: the swarm is sending heartbeart pings, but Docker Cloud cannot contact the swarm. +- **UNREACHABLE**: the swarm is sending heartbeat pings, but Docker Cloud cannot contact the swarm. - **UNAVAILABLE**: Docker Cloud is not receiving any heartbeats from the swarm. - **REMOVED**: the swarm has been unregistered from Docker Cloud and will be removed from the list soon. diff --git a/docker-for-azure/faqs.md b/docker-for-azure/faqs.md index 666d613d9b..a92d9a7a03 100644 --- a/docker-for-azure/faqs.md +++ b/docker-for-azure/faqs.md @@ -74,7 +74,7 @@ $ sudo ping 10.0.0.4 ## What are the different Azure Regions? All regions can be found here: [Microsoft Azure Regions](https://azure.microsoft.com/en-us/regions/) -An exerpt of the above regions to use when you create your service principal are: +An excerpt of the above regions to use when you create your service principal are: ```none australiaeast diff --git a/docker-for-windows/index.md b/docker-for-windows/index.md index e7430742c5..a40e4f9c54 100644 --- a/docker-for-windows/index.md +++ b/docker-for-windows/index.md @@ -466,7 +466,7 @@ in the [Docker Experimental Features README](https://github.com/docker/docker/bl Experimental features are not appropriate for production environments or workloads. They are meant to be sandbox experiments for new ideas. Some experimental features may become incorporated into upcoming stable releases, but -others may be modified or pulled from subsquent Betas, and never released +others may be modified or pulled from subsequent Betas, and never released on Stable. On both Beta and Stable releases, you can toggle **experimental mode** on and diff --git a/engine/swarm/services.md b/engine/swarm/services.md index fc8b98fe32..a7a90fc98a 100644 --- a/engine/swarm/services.md +++ b/engine/swarm/services.md @@ -560,7 +560,7 @@ $ docker service create \ > with single quotes (`'`). > > For example, the `local` driver accepts mount options as a comma-separated -> list in the `o` parameter. This example shows the correcty to escape the list. +> list in the `o` parameter. This example shows the correctly to escape the list. > > $ docker service create \ > --mount 'type=volume,src=,dst=,volume-driver=local,volume-opt=type=nfs,volume-opt=device=:,"volume-opt=o=addr=,vers=4,soft,timeo=180,bg,tcp,rw"' diff --git a/engine/swarm/swarm-mode.md b/engine/swarm/swarm-mode.md index 695a5b72dc..491647b277 100644 --- a/engine/swarm/swarm-mode.md +++ b/engine/swarm/swarm-mode.md @@ -84,7 +84,7 @@ reach the first manager node is not the same address the manager sees as its own. For instance, in a cloud setup that spans different regions, hosts have both internal addresses for access within the region and external addresses that you use for access from outside that region. In this case, specify the external -address with `--advertise-addr` so that the node can propogate that information +address with `--advertise-addr` so that the node can propagate that information to other nodes that subsequently connect to it. Refer to the `docker swarm init` [CLI reference](../reference/commandline/swarm_init.md) diff --git a/engine/userguide/storagedriver/imagesandcontainers.md b/engine/userguide/storagedriver/imagesandcontainers.md index a370bb58eb..c90dbf068f 100644 --- a/engine/userguide/storagedriver/imagesandcontainers.md +++ b/engine/userguide/storagedriver/imagesandcontainers.md @@ -340,7 +340,7 @@ command. > layer. It is now stored as a string of text in a single config file that > relates to the overall image. This can result in some image layers showing as > "missing" in the output of the `docker history` command. This is normal -> behaviour and can be ignored. +> behavior and can be ignored. > > You may hear images like these referred to as *flat images*. diff --git a/kitematic/known-issues.md b/kitematic/known-issues.md index a9f8f22697..8e79d918c7 100644 --- a/kitematic/known-issues.md +++ b/kitematic/known-issues.md @@ -38,4 +38,4 @@ if you're looking to help fix specific issues around VM provisioning. ## View All Issues For a full list of Kitematic bugs or issues see our existing GitHub -issues labelled as `bug`. +issues labeled as `bug`. diff --git a/kitematic/userguide.md b/kitematic/userguide.md index dfc7ec7e8a..8ced328a51 100644 --- a/kitematic/userguide.md +++ b/kitematic/userguide.md @@ -133,7 +133,7 @@ want to rename it. ### Adding Environment variables -Many images use environment variables to let you customise them. The "General" +Many images use environment variables to let you customize them. The "General" "Settings" tab allows you to add and modify the environment variables used to start a container. diff --git a/opensource/project/set-up-dev-env.md b/opensource/project/set-up-dev-env.md index 5b67a9acc3..625f6b286e 100644 --- a/opensource/project/set-up-dev-env.md +++ b/opensource/project/set-up-dev-env.md @@ -309,7 +309,7 @@ change, you might repeat or iterate through this flow several times. ## Where to go next Congratulations, you have successfully achieved Docker inception. You've had a -small experience of the develpment process. You've set up your development +small experience of the development process. You've set up your development environment and verified almost all the essential processes you need to contribute. Of course, before you start contributing, [you'll need to learn one more piece of the development process, the test framework](test-and-docs.md). diff --git a/registry/recipes/apache.md b/registry/recipes/apache.md index c60c64f96a..7febe0bc2e 100644 --- a/registry/recipes/apache.md +++ b/registry/recipes/apache.md @@ -105,7 +105,7 @@ Listen 5043 SSLCertificateFile /usr/local/apache2/conf/domain.crt SSLCertificateKeyFile /usr/local/apache2/conf/domain.key - ## SSL settings recommandation from: https://raymii.org/s/tutorials/Strong_SSL_Security_On_Apache2.html + ## SSL settings recommendation from: https://raymii.org/s/tutorials/Strong_SSL_Security_On_Apache2.html # Anti CRIME SSLCompression off