From 64c8e6c6edfe85f29431039d6c27fcb79e12216c Mon Sep 17 00:00:00 2001
From: "Jose J. Escobar" <53836904+jescobar-docker@users.noreply.github.com>
Date: Mon, 23 Sep 2019 09:50:50 -0700
Subject: [PATCH] Update back-up-swarm.md (#9496)

- Typo on symbol
- Added word "manager" to clarify the type of nodes where the procedure will be repeated.
---
 ee/admin/backup/back-up-swarm.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ee/admin/backup/back-up-swarm.md b/ee/admin/backup/back-up-swarm.md
index 536feb9877..e019038e90 100644
--- a/ee/admin/backup/back-up-swarm.md
+++ b/ee/admin/backup/back-up-swarm.md
@@ -30,7 +30,7 @@ You must perform a manual backup on each manager node, because logs contain node
     [Lock your swarm to protect its encryption key](/engine/swarm/swarm_manager_locking.md).
 
 2.  Because you must stop the engine of the manager node before performing the backup, having three manager 
-    nodes is recommended for high availability [HA]). For a cluster to be operational, a majority of managers 
+    nodes is recommended for high availability (HA). For a cluster to be operational, a majority of managers 
     must be online. If less than 3 managers exists, the cluster is unavailable during the backup.
 
     > **Note**: During the time that a manager is shut down, your swarm is more vulnerable to
@@ -76,7 +76,7 @@ You must perform a manual backup on each manager node, because logs contain node
     ```
     systemctl start docker
     ```
-7. Except for step 1, repeat the previous steps for each node.
+7. Except for step 1, repeat the previous steps for each manager node.
 
 ### Where to go next