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

Fixed more typos in the docs 

Signed-off-by: Ken Cochrane <KenCochrane@gmail.com>
This commit is contained in:
Ken Cochrane 2016-04-13 09:44:32 -04:00
parent 2bbea5d1a4
commit ce1dffa58a
No known key found for this signature in database
GPG Key ID: E74D22C603E63701
4 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/configure-tls.md
View File

@ -72,14 +72,13 @@ LTS.
In this step, you configure a Linux server as a CA. You use this CA to create In this step, you configure a Linux server as a CA. You use this CA to create
and sign keys. This step included so that readers without access to an existing and sign keys. This step included so that readers without access to an existing
CA (external or corpoate) and certificates can follow along and complete the CA (external or corporate) and certificates can follow along and complete the
later steps that require installing and using certificates. It is `not` later steps that require installing and using certificates. It is `not`
intended as a model for how to deploy production-worthy CA. intended as a model for how to deploy production-worthy CA.
1. Logon to the terminal of your CA server and elevate to root. 1. Logon to the terminal of your CA server and elevate to root.
$ sudo su $ sudo su
#
2. Create a private key called `ca-priv-key.pem` for the CA: 2. Create a private key called `ca-priv-key.pem` for the CA:

2
docs/install-manual.md
View File

@ -86,7 +86,7 @@ From your AWS home console, do the following:
## Step 2. Create your instances ## Step 2. Create your instances
In this step, you create five Linux hosts that are part of your default security In this step, you create five Linux hosts that are part of your default security
gorup. When complete, the example deployment contains three types of nodes: group. When complete, the example deployment contains three types of nodes:
| Node Description | Name | | Node Description | Name |
|--------------------------------------|-------------------------| |--------------------------------------|-------------------------|

2
docs/plan-for-production.md
View File

@ -306,7 +306,7 @@ network bandwidth.
If your Swarm nodes are balanced across multiple failure domains, the spread If your Swarm nodes are balanced across multiple failure domains, the spread
strategy evenly balance containers across those failure domains. However, strategy evenly balance containers across those failure domains. However,
spread on its own is not aware of the roles of any of those containers, so has spread on its own is not aware of the roles of any of those containers, so has
no inteligence to spread multiple instances of the same service across failure no intelligence to spread multiple instances of the same service across failure
domains. To achieve this you should use tags and constraints. domains. To achieve this you should use tags and constraints.
The **binpack** strategy runs as many containers as possible on a node, The **binpack** strategy runs as many containers as possible on a node,

2
docs/swarm_at_scale/04-deploy-app.md
View File

@ -84,7 +84,7 @@ repository](https://github.com/docker/swarm-microservice-demo-v1).
requirements, copies files from the build context into the container, requirements, copies files from the build context into the container,
exposes port `80` and tells the container which command to run. exposes port `80` and tells the container which command to run.
5. Spend time investigating the other parts of the application by viewing the `results-app/Dockefile` and the `vote-worker/Dockerfile` in the application. 5. Spend time investigating the other parts of the application by viewing the `results-app/Dockerfile` and the `vote-worker/Dockerfile` in the application.
## Step 2. Build custom images ## Step 2. Build custom images