minor changes

Author: dennispadia

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

@@ -44,10 +44,13 @@ Read the following SAP Notes and articles first:
 > [!IMPORTANT]
 > In Azure, RHEL high availability cluster with storage based fencing (fence_sbd) uses software-emulated watchdog. It is important to review [Software-Emulated Watchdog Known Limitations](https://access.redhat.com/articles/7034141) and [Support Policies for RHEL High Availability Clusters - sbd and fence_sbd](https://access.redhat.com/articles/2800691) when selecting SBD as the fencing mechanism.
 
-There are two options available for configuring the pacemaker cluster for RHEL with an SBD device. However, it's important to note that the fencing mechanism with SBD is supported on RHEL 8.8 and higher, RHEL 9.0 and higher.
+There are two options available for configuring the pacemaker cluster for RHEL with an SBD device.
 
 ### Use an SBD device
 
+> [!NOTE]
+> The fencing mechanism with SBD is supported on RHEL 8.8 and higher, as well as RHEL 9.0 and higher.
+
 You can configure the SBD device by using either of two options:
 
 * SBD with iSCSI target server

articles/sap/workloads/sap-hana-availability-one-region.md

@@ -103,7 +103,7 @@ In this scenario, data that's replicated to the HANA instance in the second VM i
 
 ### SAP HANA system replication with automatic failover
 
-In the standard and most common availability configuration within one Azure region, two Azure VMs running Linux with HA packages have a failover cluster defined. The HA Linux cluster is based on the `Pacemaker` framework using [SLES](./high-availability-guide-suse-pacemaker.md) or [RHEL](./high-availability-guide-rhel-pacemaker.md) with a `fencing device` [SLES](./high-availability-guide-suse-pacemaker.md#create-an-azure-fence-agent-device) or [RHEL](./high-availability-guide-rhel-pacemaker.md#create-a-fencing-device) as an example.
+In the standard and most common availability configuration within one Azure region, two Azure VMs running Linux with HA packages have a failover cluster defined. The HA Linux cluster is based on the `Pacemaker` framework using [SLES](./high-availability-guide-suse-pacemaker.md) or [RHEL](./high-availability-guide-rhel-pacemaker.md) with a `fencing device` [SLES](./high-availability-guide-suse-pacemaker.md#create-an-azure-fence-agent-device) or [RHEL](./high-availability-guide-rhel-pacemaker.md#azure-fence-agent-configuration) as an example.
 
 From an SAP HANA perspective, the replication mode that's used is synced and an automatic failover is configured. In the second VM, the SAP HANA instance acts as a hot standby node. The standby node receives a synchronous stream of change records from the primary SAP HANA instance. As transactions are committed by the application at the HANA primary node, the primary HANA node waits to confirm the commit to the application until the secondary SAP HANA node confirms that it received the commit record. SAP HANA offers two synchronous replication modes. For details and for a description of differences between these two synchronous replication modes, see the SAP article [Replication modes for SAP HANA system replication](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/c039a1a5b8824ecfa754b55e0caffc01.html).