updated the suse and rhel docs for sap ascs/ers cluster with note for 3 node cluster

Author: Anjan Banerjee

articles/sap/workloads/high-availability-guide-rhel-multi-sid.md

@@ -544,7 +544,7 @@ This article assumes that:
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ### Proceed with the SAP installation

articles/sap/workloads/high-availability-guide-rhel-netapp-files.md

@@ -732,7 +732,7 @@ The following items are prefixed with either:
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ## SAP NetWeaver application server preparation

articles/sap/workloads/high-availability-guide-rhel-nfs-azure-files.md

@@ -651,7 +651,7 @@ The following items are prefixed with:
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ## SAP NetWeaver application server preparation

articles/sap/workloads/high-availability-guide-rhel.md

@@ -552,7 +552,7 @@ The following items are prefixed with:
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ## SAP NetWeaver application server preparation
@@ -848,7 +848,7 @@ Follow these steps to install an SAP application server.
    By enabling the `priority-fencing-delay` property, the cluster introduces a delay in the fencing action, specifically on the node hosting ASCS resource, allowing the node to win the fence race.
 
    > [!NOTE]
-   > The property priority-fencing-delay is only applicable for ENSA2 running on two-node cluster.
+   > The property `priority-fencing-delay` is only applicable for ENSA2 running on two-node cluster.
 
    Run the following command to delete the firewall rule.
 

articles/sap/workloads/high-availability-guide-suse-multi-sid.md

@@ -534,7 +534,7 @@ The following picture shows how the resources would look like in the High Availa
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ### Proceed with the SAP installation

articles/sap/workloads/high-availability-guide-suse-netapp-files.md

@@ -757,7 +757,7 @@ sudo crm_mon -r
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 ## SAP NetWeaver application server preparation
 

articles/sap/workloads/high-availability-guide-suse-nfs-azure-files.md

@@ -648,7 +648,7 @@ sudo crm_mon -r
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ## SAP NetWeaver application server preparation

articles/sap/workloads/high-availability-guide-suse-nfs-simple-mount.md

@@ -809,7 +809,7 @@ sudo crm_mon -r
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster. 
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster. 
 
 
 ## Prepare the SAP application server

articles/sap/workloads/high-availability-guide-suse.md

@@ -610,7 +610,7 @@ sudo crm_mon -r
 > [!Note]
 > SAP ASCS/ERS cluster can be extended from 2-node to 3-node cluster with 3rd node as a spare node for failover of ASCS or ERS services.
 > - 3-node setup can only be used for SAP systems using SAP Enqueue Replication Server 2 (ENSA2).
-> - The cluster property ‘priority-fencing-delay’ should not be used in a 3-node cluster.
+> - The cluster property `priority-fencing-delay` should not be used in a 3-node cluster.
 
 
 ## SAP NetWeaver application server preparation
@@ -1039,7 +1039,7 @@ The following tests are a copy of the test cases in the best practices guides of
    Additionally, in ENSA 2 configuration, to prioritize the node hosting the ASCS resource over the other node during a split brain scenario, recommendation is to configure [`priority-fencing-delay`](https://documentation.suse.com/sle-ha/15-SP3/single-html/SLE-HA-administration/#pro-ha-storage-protect-fencing) property in the cluster. Enabling priority-fencing-delay property allows the cluster to introduce an extra delay in the fencing action specifically on the node hosting the ASCS resource, allowing the ASCS node to win the fence race.
 
    > [!NOTE]
-   > The property priority-fencing-delay is only applicable for ENSA2 running on two-node cluster.
+   > The property `priority-fencing-delay` is only applicable for ENSA2 running on two-node cluster.
 
    Execute following command to delete the firewall rule.