Merge pull request #58758 from lahinson/etcd-quorum-not-collapsed-osdocs-5476

[OSDOCS-5476]: Updating etcd restore docs

Author: mburke5678

backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc

@@ -13,12 +13,15 @@ include::modules/dr-restoring-cluster-state-about.adoc[leveloffset=+1]
 
 // Restoring to a previous cluster state
 include::modules/dr-restoring-cluster-state.adoc[leveloffset=+1]
-include::modules/dr-scenario-cluster-state-issues.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 [id="additional-resources_dr-restoring-cluster-state"]
 == Additional resources
 
-* xref:../../../networking/accessing-hosts.adoc#accessing-hosts[Creating a bastion host to access {product-title} instances and the control plane nodes with SSH].
+* xref:../../../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Installing a user-provisioned cluster on bare metal]
+* xref:../../../networking/accessing-hosts.adoc#accessing-hosts[Creating a bastion host to access {product-title} instances and the control plane nodes with SSH]
+* xref:../../../installing/installing_bare_metal_ipi/ipi-install-expanding-the-cluster.adoc#replacing-a-bare-metal-control-plane-node_ipi-install-expanding[Replacing a bare-metal control plane node] 
+
+include::modules/dr-scenario-cluster-state-issues.adoc[leveloffset=+1]
+
 
-* xref:../../../installing/installing_bare_metal_ipi/ipi-install-expanding-the-cluster.adoc#replacing-a-bare-metal-control-plane-node_ipi-install-expanding[Replacing a bare-metal control plane node]. 

modules/dr-restoring-cluster-state.adoc

@@ -372,18 +372,22 @@ $ oc get pods -n openshift-ovn-kubernetes -o name | grep ovnkube-node | while re
 $ oc get  pods -n openshift-ovn-kubernetes | grep ovnkube-node
 ----
 
-. Delete and recreate other non-recovery, control plane machines, one by one. After these machines are recreated, a new revision is forced and etcd scales up automatically.
+. Delete and re-create other non-recovery, control plane machines, one by one. After the machines are re-created, a new revision is forced and etcd automatically scales up.
++
+** If you use a user-provisioned bare metal installation, you can re-create a control plane machine by using the same method that you used to originally create it. For more information, see "Installing a user-provisioned cluster on bare metal". 
 +
 [WARNING]
 ====
-For bare metal installations on installer-provisioned infrastructure, control plane machines are not recreated. For more information, see "Replacing a bare-metal control plane node".
+Do not delete and re-create the machine for the recovery host.
 ====
 +
-If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps. Otherwise, you must create the new control plane node using the same method that was used to originally create it.
+** If you are running installer-provisioned infrastructure, or you used the Machine API to create your machines, follow these steps:
 +
 [WARNING]
 ====
-Do not delete and recreate the machine for the recovery host.
+Do not delete and re-create the machine for the recovery host.
+
+For bare metal installations on installer-provisioned infrastructure, control plane machines are not re-created. For more information, see "Replacing a bare-metal control plane node".
 ====
 .. Obtain the machine for one of the lost control plane hosts.
 +
@@ -519,7 +523,7 @@ clustername-8qw5l-worker-us-east-1b-lrdxb   Running   m4.large    us-east-1   us
 clustername-8qw5l-worker-us-east-1c-pkg26   Running   m4.large    us-east-1   us-east-1c   3h28m   ip-10-0-170-181.ec2.internal   aws:///us-east-1c/i-06861c00007751b0a   running
 ----
 
-.. Create the new machine using the `new-master-machine.yaml` file:
+.. Create a machine by using the `new-master-machine.yaml` file:
 +
 [source,terminal]
 ----
@@ -551,7 +555,7 @@ It might take a few minutes for the new machine to be created. The etcd cluster
 
 .. Repeat these steps for each lost control plane host that is not the recovery host.
 
-. In a separate terminal window, log in to the cluster as a user with the `cluster-admin` role by using the following command:
+. In a separate terminal window, log in to the cluster as a user with the `cluster-admin` role by entering the following command:
 +
 [source,terminal]
 ----

post_installation_configuration/cluster-tasks.adoc

@@ -675,6 +675,13 @@ include::modules/disabling-etcd-encryption.adoc[leveloffset=+2]
 include::modules/backup-etcd.adoc[leveloffset=+2]
 include::modules/etcd-defrag.adoc[leveloffset=+2]
 include::modules/dr-restoring-cluster-state.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Installing a user-provisioned cluster on bare metal]
+* xref:../installing/index.adoc#replacing-a-bare-metal-control-plane-node_ipi-install-expanding[Replacing a bare-metal control plane node]
+
 include::modules/dr-scenario-cluster-state-issues.adoc[leveloffset=+2]
 
 [id="post-install-pod-disruption-budgets"]