From 85c00d77d811bdecb016c149f187041855208cf0 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Tue, 20 Nov 2018 12:08:16 -0800 Subject: [PATCH] Incorporate missed feedback from David --- datacenter/dtr/2.5/reference/cli/restore.md | 2 +- datacenter/ucp/3.0/reference/cli/restore.md | 2 +- reference/dtr/2.6/cli/restore.md | 2 +- reference/ucp/3.1/cli/restore.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/datacenter/dtr/2.5/reference/cli/restore.md b/datacenter/dtr/2.5/reference/cli/restore.md index 70786d022c..94a6071668 100644 --- a/datacenter/dtr/2.5/reference/cli/restore.md +++ b/datacenter/dtr/2.5/reference/cli/restore.md @@ -22,7 +22,7 @@ with configuration data from a `tar` file generated by `docker/dtr backup`. There are three steps you can take to recover an unhealthy DTR cluster: 1. If the majority of replicas are healthy, remove the unhealthy nodes from - the cluster, and join new ones for high availability. + the cluster, and join new nodes for high availability. 2. If the majority of replicas are unhealthy, use this command to revert your cluster to a single DTR replica. 3. If you can't repair your cluster to a single replica, you'll have to diff --git a/datacenter/ucp/3.0/reference/cli/restore.md b/datacenter/ucp/3.0/reference/cli/restore.md index e5d966e5d1..6552c6b4f9 100644 --- a/datacenter/ucp/3.0/reference/cli/restore.md +++ b/datacenter/ucp/3.0/reference/cli/restore.md @@ -45,7 +45,7 @@ backup file under /config/backup.tar, and run the restore command with the Notes: - * Please run `uninstall-ucp` before attempting the restore operation on an + * Run `uninstall-ucp` before attempting the restore operation on an existing UCP cluster. * If your swarm-mode cluster has lost quorum and the original set of managers diff --git a/reference/dtr/2.6/cli/restore.md b/reference/dtr/2.6/cli/restore.md index ea2d4ccb16..a832c00031 100644 --- a/reference/dtr/2.6/cli/restore.md +++ b/reference/dtr/2.6/cli/restore.md @@ -22,7 +22,7 @@ with configuration data from a `tar` file generated by `docker/dtr backup`. There are three steps you can take to recover an unhealthy DTR cluster: 1. If the majority of replicas are healthy, remove the unhealthy nodes from - the cluster, and join new ones for high availability. + the cluster, and join new nodes for high availability. 2. If the majority of replicas are unhealthy, use this command to revert your cluster to a single DTR replica. 3. If you can't repair your cluster to a single replica, you'll have to diff --git a/reference/ucp/3.1/cli/restore.md b/reference/ucp/3.1/cli/restore.md index e5d966e5d1..6552c6b4f9 100644 --- a/reference/ucp/3.1/cli/restore.md +++ b/reference/ucp/3.1/cli/restore.md @@ -45,7 +45,7 @@ backup file under /config/backup.tar, and run the restore command with the Notes: - * Please run `uninstall-ucp` before attempting the restore operation on an + * Run `uninstall-ucp` before attempting the restore operation on an existing UCP cluster. * If your swarm-mode cluster has lost quorum and the original set of managers