Apply changes from PM review

Co-authored-by: Ralitza Deltcheva <[email protected]>

Author: 2 people

articles/virtual-machines/workloads/sap/ha-setup-with-fencing-device.md

@@ -55,7 +55,7 @@ If you're an existing customer with HANA Large Instances already provisioned, yo
 - Customer name (for example, Microsoft)
 - HANA system identifier (SID) (for example, H11)
 
-After the fencing device is configured, the Microsoft Service Management team will provide you with the fencing block device (SBD) name and IP address of the iSCSI storage. You can use this information to configure fencing setup. 
+After the fencing device is configured, the Microsoft Service Management team will provide you with the SBD name and IP address of the iSCSI storage. You can use this information to configure fencing setup. 
 
 Follow the steps in the following sections to set up HA by using the fencing device.
 

articles/virtual-machines/workloads/sap/hana-large-instance-virtual-machine-migration.md

@@ -50,7 +50,7 @@ You can migrate to Azure VMs for all HLI scenarios. Common deployment models for
 | 2 | [Single node with Multiple Components in One System (MCOS)](./hana-supported-scenario.md#single-node-mcos) | Yes | - |
 | 3 | [Single node with DR using storage replication](./hana-supported-scenario.md#single-node-with-dr-using-storage-replication) | No | Storage replication isn't available with Azure virtual platform; change current DR solution to either HSR or backup/restore. |
 | 4 | [Single node with DR (multipurpose) using storage replication](./hana-supported-scenario.md#single-node-with-dr-multipurpose-using-storage-replication) | No | Storage replication isn't available with Azure virtual platform; change current DR solution to either HSR or backup/restore. |
-| 5 | [HSR with fencing for high availability](./hana-supported-scenario.md#hsr-with-fencing-for-high-availability) | Yes | No preconfigured SBD for target VMs.  Select and deploy a fencing solution.  Possible options: Azure Fencing Agent (supported for both [RHEL](./high-availability-guide-rhel-pacemaker.md), [SLES](./high-availability-guide-suse-pacemaker.md)), and fencing block device (SBD). |
+| 5 | [HSR with fencing for high availability](./hana-supported-scenario.md#hsr-with-fencing-for-high-availability) | Yes | No preconfigured SBD for target VMs.  Select and deploy a fencing solution.  Possible options: Azure Fencing Agent (supported for both [RHEL](./high-availability-guide-rhel-pacemaker.md), [SLES](./high-availability-guide-suse-pacemaker.md)), and SBD. |
 | 6 | [HA with HSR, DR with storage replication](./hana-supported-scenario.md#high-availability-with-hsr-and-dr-with-storage-replication) | No | Replace storage replication for DR needs with either HSR or backup/restore. |
 | 7 | [Host auto failover (1+1)](./hana-supported-scenario.md#host-auto-failover-11) | Yes | Use Azure NetApp Files (ANF) for shared storage with Azure VMs. |
 | 8 | [Scale-out with standby](./hana-supported-scenario.md#scale-out-with-standby) | Yes | BW/4HANA with M128s, M416s, M416ms VMs using ANF for storage only. |

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

@@ -192,7 +192,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    <pre><code> # Run the following command until the status of both nodes is online
    sudo pcs status
    # Cluster name: nw1-azr
-   # WARNING: no fencing devices and stonith-enabled is not false
+   # WARNING: no stonith devices and stonith-enabled is not false
    # Stack: corosync
    # Current DC: <b>prod-cl1-1</b> (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum
    # Last updated: Fri Aug 17 09:18:24 2018

articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md

@@ -33,7 +33,8 @@ This article discusses how to set up Pacemaker on SUSE Linux Enterprise Server (
 [sles-nfs-guide]:high-availability-guide-suse-nfs.md
 [sles-guide]:high-availability-guide-suse.md
 
-In Azure, you have two options for setting up fencing in the Pacemaker cluster for SLES. You can use an Azure fence agent, which restarts a failed node via the Azure APIs, or you can use a fencing block device (SBD device).
+In Azure, you have two options for setting up fencing in the Pacemaker cluster for SLES. You can use an Azure fence agent, which restarts a failed node via the Azure APIs, or you can use SBD device.
+
 
 ### Use an SBD device
 
@@ -709,7 +710,8 @@ Make sure to assign the custom role to the service principal at all VM (cluster
       # Address for ring0 [10.0.0.6] <b>Select Enter</b>
       # Port for ring0 [5405] <b>Select Enter</b>
       # Do you wish to use SBD (y/n)? <b>n</b>
-      #WARNING: Not configuring SBD - fencing will be disabled.
+      #WARNING: Not configuring SBD - STONITH will be disabled.
+
       # Do you wish to configure an administration IP (y/n)? <b>n</b>
       </code></pre>
 

articles/virtual-machines/workloads/sap/large-instance-high-availability-rhel.md

@@ -441,7 +441,7 @@ In this section, you initialize the cluster. This section uses the same two host
 
 	WARNINGS:
 
-	No fencing devices and `stonith-enabled` is not false
+	No stonith devices and `stonith-enabled` is not false
 
 	Stack: corosync
 

articles/virtual-machines/workloads/sap/monitor-sap-on-azure.md

@@ -50,7 +50,7 @@ Data collection in AMS depends on the providers that you configure. During publi
 
 High availability (HA) Pacemaker cluster data includes:
 
-- Node, resource, and fencing block device (SBD) status
+- Node, resource, and SBD status
 - Pacemaker location constraints
 - Quorum votes and ring status