Merge pull request #100791 from openshift-cherrypick-robot/cherry-pick-100785-to-enterprise-4.20

[enterprise-4.20] OSDOCS#12987: Two-node OpenShift cluster with fencing Follow Up

Author: kalexand-rh

installing/installing_two_node_cluster/installing_tnf/install-post-tnf.adoc

@@ -6,11 +6,11 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-The following sections help with recovering from issues in a two-node OpenShift cluster with fencing.
-
 :FeatureName: Two-node OpenShift cluster with fencing
 include::snippets/technology-preview.adoc[leveloffset=+1]
 
+Use the following sections help you with recovering from issues in a two-node OpenShift cluster with fencing.
+
 // Manually recovering from a disruption event when automated recovery is unavailable
 include::modules/installation-manual-recovering-when-auto-recovery-is-unavail.adoc[leveloffset=+1]
 
@@ -30,4 +30,4 @@ include::modules/installation-replacing-control-plane-nodes.adoc[leveloffset=+1]
 * xref:../../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd-restoring_backing-up-etcd[Restoring etcd from a backup].
 
 // Verifying etcd health in a two-node OpenShift cluster with fencing
-include::modules/installation-verifying-etcd-health.adoc[leveloffset=+1]
+include::modules/installation-verifying-etcd-health.adoc[leveloffset=+1]

installing/installing_two_node_cluster/installing_tnf/install-tnf.adoc

@@ -6,11 +6,11 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can deploy a two-node OpenShift cluster with fencing by using either the installer-provisioned infrastructure or the user-provisioned infrastructure installation method. The following examples provide sample `install-config.yaml` configurations for both methods.
-
 :FeatureName: Two-node OpenShift cluster with fencing
 include::snippets/technology-preview.adoc[leveloffset=+1]
 
+You can deploy a two-node OpenShift cluster with fencing by using either the installer-provisioned infrastructure or the user-provisioned infrastructure installation method. The following examples provide sample `install-config.yaml` configurations for both methods.
+
 // Sample install-config.yaml for a two-node installer-provisioned infrastructure cluster with fencing
 include::modules/installation-sample-install-config-two-node-fencing-ipi.adoc[leveloffset=+1]
 

modules/installation-manual-recovering-when-auto-recovery-is-unavail.adoc

@@ -158,4 +158,4 @@ If manual recovery is still required and it fails, collect a must-gather and SOS
 
 .Verification
 
-For information about verifying that both control plane nodes and etcd are operating correctly, see "Verifying etcd health in a two-node OpenShift cluster with fencing".
+For information about verifying that both control plane nodes and etcd are operating correctly, see "Verifying etcd health in a two-node OpenShift cluster with fencing".

modules/installation-sample-install-config-two-node-fencing-ipi.adoc

@@ -67,4 +67,4 @@ sshKey: '<ssh_public_key>'
 * `featureSet`: Set this field to `TechPreviewNoUpgrade` to enable two-node OpenShift cluster deployments.  
 * `platform.baremetal.apiVIPs` and `platform.baremetal.ingressVIPs` : Virtual IPs for the API and Ingress endpoints. Ensure they are reachable by all nodes and external clients.  
 * `pullSecret`: Contains credentials required to pull container images for the cluster components.  
-* `sshKey`: The SSH public key for accessing cluster nodes after installation.
+* `sshKey`: The SSH public key for accessing cluster nodes after installation.