From 33d336130deba647e39a1dfd80503177895d6fe7 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Thu, 8 Mar 2018 16:53:53 +0800 Subject: [PATCH] Update deploy-infra.md --- swarm/swarm_at_scale/deploy-infra.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/swarm/swarm_at_scale/deploy-infra.md b/swarm/swarm_at_scale/deploy-infra.md index 9ef1c4cc9e..80215010fe 100644 --- a/swarm/swarm_at_scale/deploy-infra.md +++ b/swarm/swarm_at_scale/deploy-infra.md @@ -41,7 +41,7 @@ actual value. ## Task 1. Create the keystore server To enable a Docker container network and Swarm discovery, you must -deploy (or supply) a key-value store. As a discovery backend, the key-value store +deploy (or supply) a key-value store. As a discovery backend, the key-value store maintains an up-to-date list of cluster members and shares that list with the Swarm manager. The Swarm manager uses this list to assign tasks to the nodes. @@ -138,7 +138,7 @@ support the container network you create later. the manager. This is key for the manager when it connects to other machines in the cluster. -4. Test your work by using displaying the Docker daemon logs from the host. +4. Test your work by displaying the Docker daemon logs from the host. ```bash $ docker-machine ssh manager @@ -427,7 +427,7 @@ commands below, notice the label you are applying to each node. The command is acting on the Swarm port, so it returns information about the entire cluster. You have a manager and no nodes. -## Next Step +## Next step Your key-value store, load balancer, and Swarm cluster infrastructure are up. You are ready to [build and run the voting application](deploy-app.md) on it.