From 7f47adcc961a522ec8e27f1303483e3539423e4e Mon Sep 17 00:00:00 2001 From: Robert Hencke Date: Thu, 27 Oct 2016 12:59:54 -0400 Subject: [PATCH] Minor wording & grammar fixes to deploy-infra.md. Use single term for key-value store. Fix a couple minor grammar issues. Add documentation link to supported key-value stores. --- 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 2e886cf510..946586371f 100644 --- a/swarm/swarm_at_scale/deploy-infra.md +++ b/swarm/swarm_at_scale/deploy-infra.md @@ -46,7 +46,7 @@ actual value. ## Task 1. Create the keystore server To enable a Docker container network and Swarm discovery, you must -supply deploy a key-value store. As a discovery backend, the keystore +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. @@ -54,7 +54,7 @@ An overlay network requires a key-value store. The key-value store holds information about the network state which includes discovery, networks, endpoints, IP addresses, and more. -Several different backends are supported. This example uses Consul container. 1. Create a "machine" named `keystore`. @@ -436,5 +436,5 @@ commands below, notice the label you are applying to each node. ## Next Step -Your key-store, load balancer, and Swarm cluster infrastructure is up. You are +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.