瀏覽代碼

Merge pull request #25610 from lixiaobing10051267/masterSwarm

optimize some descriptions for swarm nodes.md
(cherry picked from commit 81fca603a4c828a7bca882cd504cc32b0a7b0d1d)

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
Sebastiaan van Stijn 9 年之前
父節點
當前提交
6e122d9bd5
共有 1 個文件被更改,包括 2 次插入2 次删除
  1. 2 2
      docs/swarm/how-swarm-mode-works/nodes.md

+ 2 - 2
docs/swarm/how-swarm-mode-works/nodes.md

@@ -42,12 +42,12 @@ manager. If the manager in a single-manager swarm fails, your services will
 continue to run, but you will need to create a new cluster to recover.
 
 To take advantage of swarm mode's fault-tolerance features, Docker recommends
-you implement an odd number of nodes nodes according to your organization's
+you implement an odd number of nodes according to your organization's
 high-availability requirements. When you have multiple managers you can recover
 from the failure of a manager node without downtime.
 
 * A three-manager swarm tolerates a maximum loss of one manager.
-* A five-manager swarm tolerates a maximum simultaneous loss two
+* A five-manager swarm tolerates a maximum simultaneous loss of two
 manager nodes.
 * An `N` manager cluster will tolerate the loss of at most
 `(N-1)/2` managers.