From a00b0c48fe00ef1b27a5245c8442f410679b9120 Mon Sep 17 00:00:00 2001
From: user81230 <153269499+user81230@users.noreply.github.com>
Date: Mon, 13 May 2024 13:25:00 +0300
Subject: [PATCH] Update recover-control-plane.md (#11155)

#10844 Copy node instead of move
---
 docs/recover-control-plane.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/recover-control-plane.md b/docs/recover-control-plane.md
index 9174789cf..7cda08afb 100644
--- a/docs/recover-control-plane.md
+++ b/docs/recover-control-plane.md
@@ -8,6 +8,7 @@ Examples of what broken means in this context:
 * One or more bare metal node(s) suffer from unrecoverable hardware failure
 * One or more node(s) fail during patching or upgrading
 * Etcd database corruption
+  
 * Other node related failures leaving your control plane degraded or nonfunctional
 
 __Note that you need at least one functional node to be able to recover using this method.__
@@ -16,8 +17,8 @@ __Note that you need at least one functional node to be able to recover using th
 
 * Backup what you can
 * Provision new nodes to replace the broken ones
-* Move any broken etcd nodes into the "broken\_etcd" group, make sure the "etcd\_member\_name" variable is set.
-* Move any broken control plane nodes into the "broken\_kube\_control\_plane" group.
+* Copy any broken etcd nodes into the "broken\_etcd" group, make sure the "etcd\_member\_name" variable is set.
+* Copy any broken control plane nodes into the "broken\_kube\_control\_plane" group.
 * Place the surviving nodes of the control plane first in the "etcd" and "kube\_control\_plane" groups
 * Add the new nodes below the surviving control plane nodes in the "etcd" and "kube\_control\_plane" groups