From ca9bb6e4455201d56868ae769100c8ad086e81f5 Mon Sep 17 00:00:00 2001 From: Vincent Demeester Date: Mon, 22 Aug 2016 09:17:32 +0200 Subject: [PATCH] Merge pull request #25899 from yuexiao-wang/fix-overview Optimize description for Feature highlights (cherry picked from commit d2fa978d4d66622a197eb98f9a77fa217e25f449) Signed-off-by: Charles Smith --- docs/swarm/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/swarm/index.md b/docs/swarm/index.md index 4ed9722fcfc..55d78b6ea92 100644 --- a/docs/swarm/index.md +++ b/docs/swarm/index.md @@ -34,7 +34,7 @@ a swarm. * **Decentralized design:** Instead of handling differentiation between node roles at deployment time, the Docker Engine handles any specialization at runtime. You can deploy both kinds of nodes, managers and workers, using the -Docker Engine. This means you can build an entire Swarm from a single disk +Docker Engine. This means you can build an entire swarm from a single disk image. * **Declarative service model:** Docker Engine uses a declarative approach to @@ -50,7 +50,7 @@ adding or removing tasks to maintain the desired state. the cluster state and reconciles any differences between the actual state your expressed desired state. For example, if you set up a service to run 10 replicas of a container, and a worker machine hosting two of those replicas -crashes, the manager will create two new replicas to replace the ones that +crashes, the manager will create two new replicas to replace the replicas that crashed. The swarm manager assigns the new replicas to workers that are running and available.