docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Spelling mistakes (#2970) 

* Spelling mistakes

* Delete last_page.md
This commit is contained in:
Steven Hanna 2017-04-20 18:26:18 -04:00 committed by John Mulhausen
parent a3a7ae1e0b
commit b43c302c46
39 changed files with 50 additions and 51 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_includes/why_d4a.md
View File

@ -80,7 +80,7 @@ reduced.
Centralized logging is a critical component of many modern infrastructure
stacks. To have these logs indexed and searchable proves invaluable for
debugging appliation and system issues as they come up. Out of the box, Docker
debugging application and system issues as they come up. Out of the box, Docker
for {{cloudprovider}} forwards logs from containers to a native cloud provider
abstraction ({{cloudprovider_log_dest}}).

2
apidocs/cloud-api-source/source/includes/action.md
View File

@ -26,7 +26,7 @@
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.
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 `Success` or `Failed` states. API calls that do require asynchronous execution will return HTTP code `202 Accepted` immediately and create an action object in `In progress` state, which will change to `Success` or `Failed` state depending on the outcome of the operation being performed. In both cases the response will include a `X-DockerCloud-Action-URI` header with the resource URI of the created action.
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 `Success` or `Failed` states. API calls that do require asynchronous execution will return HTTP code `202 Accepted` immediately and create an action object in `In progress` state, which will change to `Success` or `Failed` state depending on the outcome of the operation being performed. In both cases the response will include a `X-DockerCloud-Action-URI` header with the resource URI of the created action.
### Attributes

2
apidocs/cloud-api-source/source/includes/container.md
View File

@ -709,7 +709,7 @@ uuid | The UUID of the container to redeploy
Parameter | Description
--------- | -----------
reuse_volumes | Wheather to reuse container volumes for this redeploy operation or not (default: `true`).
reuse_volumes | Whether to reuse container volumes for this redeploy operation or not (default: `true`).
## Terminate a container

2
apidocs/cloud-api-source/source/includes/dockercloud-events.md
View File

@ -34,7 +34,7 @@ This is a [namespaced endpoint](#namespaced-endpoints).
| Attribute | Description |
|:-------------|:---------------------------------------------------------------------------------------------------------------------------------|
| type | Type of object that was created or updated. For possible values, check the [events types](#event-types) table below. |
| action | Type of action that was executed on the object. Posible values: `create`, `update` or `delete` |
| action | Type of action that was executed on the object. Possible values: `create`, `update` or `delete` |
| parents | List of resource URIs (REST API) of the parents of the object, according to the "Parent-child hierarchy" table below |
| resource_uri | Resource URI (REST API) of the object that was created or updated. You can do a `GET` operation on this URL to fetch its details |
| state | The current state of the object |

2
apidocs/cloud-api-source/source/includes/nodecluster.md
View File

@ -85,7 +85,7 @@ You can specify the following options when using the Amazon Web Services provide
* `vpc`: VPC-related options (optional)
* `id`: AWS VPC identifier of the target VPC where the nodes of the cluster will be deployed (required)
* `subnets`: 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)
* `subnets`: 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)
* `security_groups`: the security group that will be applied to every node of the cluster (optional)
* `iam`: IAM-related options (optional)
* `instance_profile_name`: name of the instance profile (container for instance an IAM role) to attach to every node of the cluster (required)

2
apidocs/cloud-api-source/source/includes/service.md
View File

@ -881,7 +881,7 @@ uuid | The UUID of the service to redeploy
Parameter | Description
--------- | -----------
reuse_volumes | Wheather to reuse container volumes for this redeploy operation or not (default: `true`).
reuse_volumes | Whether to reuse container volumes for this redeploy operation or not (default: `true`).
## Terminate a service

2
apidocs/cloud-api-source/source/includes/stack.md
View File

@ -516,7 +516,7 @@ uuid | The UUID of the stack to redeploy
Parameter | Description
--------- | -----------
reuse_volumes | Wheather to reuse container volumes for this redeploy operation or not (default: `true`).
reuse_volumes | Whether to reuse container volumes for this redeploy operation or not (default: `true`).
## Terminate a stack

2
components.md
View File

@ -1,5 +1,5 @@
---
description: Componenets page
description: Components page
title: Components
hide_from_sitemap: true
---

2
datacenter/dtr/2.0/monitor-troubleshoot/troubleshoot.md
View File

@ -19,7 +19,7 @@ docker run -it --rm --net dtr-ol --name overlay-test2 --entrypoint ping docker/d
```
You can create new overlay network for this test with `docker network create
-d overaly network-name`. You can also use any images that contain `sh` and
-d overlay network-name`. You can also use any images that contain `sh` and
`ping` for this test.
If the second command succeeds, overlay networking is working.

2
datacenter/dtr/2.1/guides/monitor-troubleshoot/troubleshoot.md
View File

@ -13,7 +13,7 @@ docker run -it --rm --net dtr-ol --name overlay-test1 --entrypoint sh docker/dtr
docker run -it --rm --net dtr-ol --name overlay-test2 --entrypoint ping docker/dtr -c 3 overlay-test1
```
You can create new overlay network for this test with `docker network create -d overaly network-name`.
You can create new overlay network for this test with `docker network create -d overlay network-name`.
You can also use any images that contain `sh` and `ping` for this test.
If the second command succeeds, overlay networking is working.

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

@ -75,7 +75,7 @@ metadata
- The "manifest", which is pulled first and lists all layers and the config file
for the image.
All of these files are stored in a content-addressible manner. We take the
All of these files are stored in a content-addressable manner. We take the
sha256 hash of the file's content and use the hash as the filename. This means
that if tag `example.com/user/blog:1.11.0` and `example.com/user/blog:latest`
use the same layers we only store them once.

2
datacenter/dtr/2.2/guides/index.md
View File

@ -38,7 +38,7 @@ DTR has the ability to [clean up unreferenced manifests and layers](https://docs
## Built-in access control
DTR uses the same authentication mechanism as Docker Universal Control Plane.
Users can be managed manually or syched from LDAP or Active Directory. DTR
Users can be managed manually or synched from LDAP or Active Directory. DTR
uses [Role Based Access Control](admin/manage-users/index.md) (RBAC) to allow you to implement fine-grained
access control policies for who has access to your Docker images.

4
datacenter/dtr/2.2/guides/release-notes/index.md
View File

@ -126,7 +126,7 @@ events like image push, repository creation, and others
* The install command was improved to avoid deploying DTR to a node where it
cannot run due to port collisions
* The `docker/dtr install --ucp-node` flag is now mandatory
* The install command no longer allows deploying replicas with duplica ids
* The install command no longer allows deploying replicas with duplicate ids
* The upgrade command now validates if all tags were migrated to the latest
version before trying to migrate blob links
@ -141,7 +141,7 @@ letters
created
* The copy to clipboard button on the repository page now works on Firefox
* The repository page now renders properly the repository permissions
* You can now delete a users's full name from the UI
* You can now delete a users full name from the UI
* Organization administrators can now see the repositories owned by the organization
* The garbage collection settings now show the correct cron values
* You can now specify DTR to use port 443 when installing DTR

2
datacenter/dtr/2.2/guides/user/create-and-manage-webhooks.md
View File

@ -308,6 +308,6 @@ To delete a webhook subscription send a `DELETE` request to
which you would like to delete.
Note that in order to delete a subscription you must be either a system
administrator or an admistrator for the resource which the payload subscribes
administrator or an administrator for the resource which the payload subscribes
to. For example, as a normal user you can only delete subscriptions for
repositories which you are an admin of.

2
datacenter/dtr/2.2/guides/user/manage-images/sign-images/manage-trusted-repositories.md
View File

@ -61,7 +61,7 @@ $ notary status <dtr_url>/<account>/<repository> --unstage 0
$ notary status <dtr_url>/<account>/<repository> --reset
```
When you're ready to publish your chages to the Notary server, run:
When you're ready to publish your changes to the Notary server, run:
```bash
$ notary publish <dtr_url>/<account>/<repository>

2
datacenter/ucp/1.1/configuration/use-externally-signed-certs.md
View File

@ -1,7 +1,7 @@
---
description: Learn how to configure Docker Universal Control Plane to use your own
certificates.
keywords: Universal Control Plane, UCP, certificate, authentiation, tls
keywords: Universal Control Plane, UCP, certificate, authentication, tls
redirect_from:
- /ucp/configuration/use-externally-signed-certs/
title: Use externally-signed certificates

2
datacenter/ucp/2.0/guides/configuration/index.md
View File

@ -1,7 +1,7 @@
---
description: Learn how to configure Docker Universal Control Plane to use your own
certificates.
keywords: Universal Control Plane, UCP, certificate, authentiation, tls
keywords: Universal Control Plane, UCP, certificate, authentication, tls
title: Use externally-signed certificates
---

2
datacenter/ucp/2.0/guides/content-trust/continuous-integration.md
View File

@ -106,7 +106,7 @@ will still need to provide them for the commands to work correctly.
Now that the repository is initialized, we need to create the delegations for Jenkins. Docker
Content Trust treats a delegation role called `targets/releases` specially. It considers this
delegation to contain the canonical list of published images for the repository. It is therefore
generally desiable to add all users to this delegation with the following command:
generally desirable to add all users to this delegation with the following command:
```
notary delegation add my_repository targets/releases --all-paths /path/to/cert.pem

2
datacenter/ucp/2.0/guides/content-trust/manage-trusted-repositories.md
View File

@ -33,7 +33,7 @@ $ notary status <dtr_url>/<account>/<repository> --unstage 0
$ notary status <dtr_url>/<account>/<repository> --reset
```
When you're ready to publish your chages to the Notary server, run:
When you're ready to publish your changes to the Notary server, run:
```bash
$ notary publish <dtr_url>/<account>/<repository>

2
datacenter/ucp/2.0/guides/monitor/index.md
View File

@ -31,7 +31,7 @@ are deployed on a node, depend on whether the node is a manager or worker.
[Learn more about the UCP architecture](../architecture.md)
To check the state and logs of other UCP internal components, go to the
**Containers** page, and appply the **System containers** filter.
**Containers** page, and apply the **System containers** filter.
This can help validate that all UCP internal components are up and running.
![](../images/monitor-ucp-3.png){: .with-border}

2
datacenter/ucp/2.1/guides/admin/configure/use-trusted-images-for-ci.md
View File

@ -106,7 +106,7 @@ will still need to provide them for the commands to work correctly.
Now that the repository is initialized, we need to create the delegations for Jenkins. Docker
Content Trust treats a delegation role called `targets/releases` specially. It considers this
delegation to contain the canonical list of published images for the repository. It is therefore
generally desiable to add all users to this delegation with the following command:
generally desirable to add all users to this delegation with the following command:
```
notary delegation add my_repository targets/releases --all-paths /path/to/cert.pem

2
datacenter/ucp/2.1/guides/admin/configure/use-your-own-tls-certificates.md
View File

@ -1,7 +1,7 @@
---
description: Learn how to configure Docker Universal Control Plane to use your own
certificates.
keywords: Universal Control Plane, UCP, certificate, authentiation, tls
keywords: Universal Control Plane, UCP, certificate, authentication, tls
title: Use your own TLS certificates
---

2
docker-cloud/cloud-swarm/create-cloud-swarm.md
View File

@ -50,7 +50,7 @@ Learn how to [connect to a swarm through Docker Cloud](connect-to-swarm.md).
Learn how to [register existing swarms](register-swarms.md).
You can get an overivew of topics on [swarms in Docker Cloud](index.md).
You can get an overview of topics on [swarms in Docker Cloud](index.md).
To find out more about Docker swarm in general, see the Docker engine
[Swarm Mode overview](/engine/swarm/).

4
docker-cloud/cloud-swarm/link-aws-swarm.md
View File

@ -65,7 +65,7 @@ If you already have your AWS account connected to Docker Cloud and used the lega
7. In the **Policy Document** section, copy and paste the policy document found in the [Docker for AWS page](/docker-for-aws/iam-permissions/).
8. Click **Create Policy**.
9. Select and copy the **Role ARN** on the role screen.
It should't have changed, but you'll use it to re-link your account.
It shouldn't have changed, but you'll use it to re-link your account.
Because you edited the role's permissions, you need to re-link to your account.
Back in Docker Cloud, click the account menu and select **Cloud Settings**, and
@ -91,7 +91,7 @@ You're now ready to deploy a swarm!
For next steps, see [create a new swarm in Docker Cloud](create-cloud-swarm.md).
You can get an overivew of topics on [swarms in Docker Cloud](index.md).
You can get an overview of topics on [swarms in Docker Cloud](index.md).
<!-- TODO: Commenting out until this replaces the existing ../infrastructure/link-aws file.

2
docker-for-aws/upgrade.md
View File

@ -23,7 +23,7 @@ To initiate an update, use either the AWS Console or the AWS cli to initiate a s
![Upgrade in AWS console](img/cloudformation_update.png)
Note that single containers started (for example) with `docker run -d` are **not** preserved during an upgrade. This is because the're not Docker Swarm objects, but are known only to the individual Docker engines.
Note that single containers started (for example) with `docker run -d` are **not** preserved during an upgrade. This is because they're not Docker Swarm objects, but are known only to the individual Docker engines.
## Changing instance sizes and other template parameters

2
docker-for-mac/index.md
View File

@ -209,7 +209,7 @@ interactive settings, or switch to **Advanced** to edit the JSON directly.
The settings offered on **Basic** dialog can be
configured directly in the JSON as well. This version just surfaces
some of the commmon settings to make it easier to configure them.
some of the common settings to make it easier to configure them.
* [Experimental mode](#experimental-mode)
* [Custom registries](#custom-registries)

4
docker-for-mac/release-notes.md
View File

@ -620,7 +620,7 @@ events or unexpected unmounts.
- Memory can be allocated with 256 MiB steps
- The storage location of the Linux volume can now be moved
- More explicit proxy settings
- Proxy can now be completly disabled
- Proxy can now be completely disabled
- You can switch daemon tabs without losing your settings
- You can't edit settings while docker is restarting
@ -1225,7 +1225,7 @@ The `osxfs` file system now persists ownership changes in an extended attribute.
**New**
* Token validation is now done over an actual SSL tunnel (HTTPS). (This should fix issues with antivirus applictions.)
* Token validation is now done over an actual SSL tunnel (HTTPS). (This should fix issues with antivirus applications.)
**Upgrades**

9
docker-for-windows/index.md
View File

@ -237,11 +237,10 @@ PowerShell Module as follows.
1. Start an "elevated" PowerShell (i.e., run it as administrator).
To do this, search for PowerShell, right-click, and choose
**Run as administrator**.<br>
To do this, search for PowerShell, right-click, and choose **Run as administrator**.
![Run PowerShell as administrator](/docker-for-windows/images/PowerShell-as-admin.png)
<br><br>
When asked if you want to allow this app to make changes to your device,
click **Yes**.
@ -306,7 +305,7 @@ arrow on the taskbar to show it.
>**Tip**: You can pin the whale outside of the notification box so that it is
always visible on the taskbar. To do this, drag-and-drop the whale icon. Or,
right-click an empty porition of the taskbar, select Settings, and choose
right-click an empty portion of the taskbar, select Settings, and choose
display options through taskbar settings for notifications.
>
![whale pinned to taskbar](/docker-for-windows/images/whale-taskbar.png)
@ -457,7 +456,7 @@ containers will run. You can configure some **Basic** options on the daemon with
The settings offered on **Basic** dialog can be
configured directly in the JSON as well. This version just surfaces
some of the commmon settings to make it easier to configure them.
some of the common settings to make it easier to configure them.
* [Experimental mode](#experimental-mode)
* [Custom registries](#custom-registries)

4
docker-for-windows/release-notes.md
View File

@ -574,7 +574,7 @@ We did not distribute a 1.12.4 stable release
**Bug fixes and minor changes**
- Time drifts between Windows and Linux containers should disapear
- Time drifts between Windows and Linux containers should disappear
- VPNKit: Improved diagnostics
- Improvements in drive sharing code
- Removed the legacy "Disable oplocks" trick for enabling Windows Containers on older insider previews
@ -605,7 +605,7 @@ dialogs](index.md#about-the-docker-windows-containers-specific-dialogs).)
**Bug fixes and minor changes**
- Time drifts between Windows and Linux containers should disapear
- Time drifts between Windows and Linux containers should disappear
- VPNKit: Improved diagnostics
- Improvements in drive sharing code
- Removed the legacy "Disable oplocks" trick for enabling Windows Containers on older insider previews

2
docker-for-windows/troubleshoot.md
View File

@ -509,7 +509,7 @@ docker app.
### Docker fails to start when firewall or anti-virus software is installed
**Some firewalls and anti-virus software might be incompatible with Microsoft Windows 10 buids** (e.g., Windows 10 Anniversary Update). The conflict typically occurs after a Windows update or new install of the firewall, and manifests as an error response from the Docker daemon and a **Docker for Windows start failure**. The Comodo Firewall was one example of this problem, but users report that software has since been updated to work with these Windows 10 builds.
**Some firewalls and anti-virus software might be incompatible with Microsoft Windows 10 builds** (e.g., Windows 10 Anniversary Update). The conflict typically occurs after a Windows update or new install of the firewall, and manifests as an error response from the Docker daemon and a **Docker for Windows start failure**. The Comodo Firewall was one example of this problem, but users report that software has since been updated to work with these Windows 10 builds.
See the Comodo forums topics [Comodo Firewall conflict with
Hyper-V](https://forums.comodo.com/bug-reports-cis/comodo-firewall-began-conflict-with-hyperv-t116351.0.html)

2
engine/admin/logging/overview.md
View File

@ -310,7 +310,7 @@ The `awslogs` supports the following options:
### Examples
This exampe sends the logs to region `us-east-1` and uses the log group
This example sends the logs to region `us-east-1` and uses the log group
`myLogGroup`.
```bash

8
engine/swarm/join-nodes.md
View File

@ -5,13 +5,13 @@ title: Join nodes to a swarm
---
When you first create a swarm, you place a single Docker Engine (Engine) into
swarm mode. To take full advantage of swarm mode, you can:
swarm mode. To take full advantage of swarm mode you can add nodes to the swarm:
* Add worker nodes to the swarm to increase capacity. When you deploy a service to a swarm,
* Adding worker nodes increases capacity. When you deploy a service to a swarm,
the Engine schedules tasks on available nodes whether they are worker nodes or
manager nodes. When you add workers to your swarm, you increase the scale of
the swarm to handle tasks without affecting the manager raft consenus.
* Add Manager nodes to the swarm to increase fault-tolerance. Manager nodes perform the
the swarm to handle tasks without affecting the manager raft consensus.
* Manager nodes increase fault-tolerance. Manager nodes perform the
orchestration and cluster management functions for the swarm. Among manager
nodes, a single leader node conducts orchestration tasks. If a leader node
goes down, the remaining manager nodes elect a new leader and resume

2
engine/swarm/networking.md
View File

@ -289,7 +289,7 @@ Address 3: 10.0.9.9 my-dnsrr-service.2.am6fx47p3bropyy2dy4f8hofb.my-network
## Confirm VIP connectivity
In genaral we recommend you use `dig`, `nslookup`, or another DNS query tool to
In general we recommend you use `dig`, `nslookup`, or another DNS query tool to
test access to the service name via DNS. Because a VIP is a logical IP, `ping`
is not the right tool to confirm VIP connectivity.

2
engine/swarm/swarm-mode.md
View File

@ -37,7 +37,7 @@ as follows:
* designates the current node as a leader manager node for the swarm.
* names the node with the machine hostname.
* configures the manager to listen on an active network interface on port 2377.
* sets the current node to `Active` availability, meanining it can receive tasks
* sets the current node to `Active` availability, meaning it can receive tasks
from the scheduler.
* starts an internal distributed data store for Engines participating in the
swarm to maintain a consistent view of the swarm and all services running on it.

2
engine/userguide/storagedriver/overlayfs-driver.md
View File

@ -194,7 +194,7 @@ mount arguments.
lrwxrwxrwx 1 root root 72 Jun 20 07:36 NFYKDW6APBCCUCTOUSYDH4DXAT -> ../223c2864175491657d238e2664251df13b63adb8d050924fd1bfcdb278b866f7/diff
lrwxrwxrwx 1 root root 72 Jun 20 07:36 UL2MW33MSE3Q5VYIKBRN4ZAGQP -> ../e8876a226237217ec61c4baf238a32992291d059fdac95ed6303bdff3f59cff5/diff
The lowerest layer contains the "link" file which contains the name of the shortened
The lowest layer contains the "link" file which contains the name of the shortened
identifier, and the "diff" directory which contains the contents.
$ ls /var/lib/docker/overlay2/3a36935c9df35472229c57f4a27105a136f5e4dbef0f87905b2e506e494e348b/

2
machine/reference/create.md
View File

@ -25,7 +25,7 @@ To see how to connect Docker to this machine, run: docker-machine env dev
## Accessing driver-specific flags in the help text
The `docker-machine create` command has some flags which are applicable to all
drivers. These largely control aspects of Machine's provisoning process
drivers. These largely control aspects of Machine's provisioning process
(including the creation of Docker Swarm containers) that the user may wish to
customize.

2
registry/deploying.md
View File

@ -220,7 +220,7 @@ You can then start your registry with a simple
## Next
You will find more specific and advanced informations in the following sections:
You will find more specific and advanced information in the following sections:
- [Configuration reference](configuration.md)
- [Working with notifications](notifications.md)

2
test.md
View File

@ -69,7 +69,7 @@ culpa qui officia deserunt mollit anim id est laborum.
- [a markdown link](https://docker.com/)
- [a markdown link that opens in a new window](https://docker.com/){: target="_blank" class="_" }
(the `class="_"` trick prevents Atom from italicizing the whole rest of the file until it encouters another underscore.)
(the `class="_"` trick prevents Atom from italicizing the whole rest of the file until it encounters another underscore.)
- <a href="https://docker.com/">an HTML link</a>