edit pass: two-sap-hana-articles

Author: paulth1

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

@@ -128,7 +128,7 @@ The following instructions assume that you already deployed your [Azure virtual
 
    As you deploy the volumes, be sure to select the NFSv4.1 version. Deploy the volumes in the designated Azure NetApp Files subnet. The IP addresses of the Azure NetApp Files volumes are assigned automatically.
 
-   Keep in mind that the Azure NetApp Files resources and the Azure VMs must be in the same Azure virtual network or in peered Azure virtual networks. For example, hanadb1-data-mnt00001, hanadb1-log-mnt00001, and so on are the volume names, and nfs://10.3.1.4/hanadb1-data-mnt00001, nfs://10.3.1.4/hanadb1-log-mnt00001, and so on are the file paths for the Azure NetApp Files volumes.
+   The Azure NetApp Files resources and the Azure VMs must be in the same Azure virtual network or in peered Azure virtual networks. For example, hanadb1-data-mnt00001, hanadb1-log-mnt00001, and so on are the volume names, and nfs://10.3.1.4/hanadb1-data-mnt00001, nfs://10.3.1.4/hanadb1-log-mnt00001, and so on are the file paths for the Azure NetApp Files volumes.
 
    On **hanadb1**:
    - Volume hanadb1-data-mnt00001 (nfs://10.3.1.4:/hanadb1-data-mnt00001)

includes/sap-load-balancer-db-portal.md

@@ -9,23 +9,22 @@ author: dennispadia
 ms.author: depadia
 ---
 
-Follow the steps in the [Create load balancer](../articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md#create-load-balancer) guide to set up a standard load balancer for a high-availability SAP system by using the Azure portal. During the setup of the load balancer, consider the following points:
+Follow the steps in [Create load balancer](../articles/load-balancer/quickstart-load-balancer-standard-internal-portal.md#create-load-balancer) to set up a standard load balancer for a high-availability SAP system by using the Azure portal. During the setup of the load balancer, consider the following points:
 
-1. **Front-end IP configuration:** Create a front-end IP. Select the same virtual network and subnet same as your database virtual machines.
-1. **Back-end pool:** Create a back-end pool and add database VMs.
+1. **Frontend IP Configuration:** Create a front-end IP. Select the same virtual network and subnet name as your database virtual machines.
+1. **Backend Pool:** Create a back-end pool and add database VMs.
 1. **Inbound rules:** Create a load-balancing rule. Follow the same steps for both load-balancing rules.
      - **Frontend IP address**: Select a front-end IP.
      - **Backend pool**: Select a back-end pool.
      - **High-availability ports**: Select this option.
-     - **Protocol**: TCP
-     - **Health probe**: Create a health probe with the following details:
-       - **Protocol**: TCP
-       - **Port**: [for example: 625<instance-no.>]
-       - **Interval**: 5
-       - **Probe threshold**: 2
-     - **Idle timeout (minutes)**: 30
+     - **Protocol**: Select **TCP**.
+     - **Health Probe**: Create a health probe with the following details:
+       - **Protocol**: Select **TCP**.
+       - **Port**: For example, **625<instance-no.>**.
+       - **Interval**: Enter **5**.
+       - **Probe Threshold**: Enter **2**.
+     - **Idle timeout (minutes)**: Enter **30**.
      - **Enable Floating IP**: Select this option.
 
 > [!NOTE]
->
-> The health probe configuration property `numberOfProbes`, otherwise known as "Unhealthy threshold" in the portal, isn't respected. To control the number of successful or failed consecutive probes, set the property `probeThreshold` to 2. It's currently not possible to set this property by using the Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe) or a [PowerShell](/powershell/module/az.network/set-azloadbalancerprobeconfig) command.
+> The health probe configuration property `numberOfProbes`, otherwise known as **Unhealthy threshold** in the portal, isn't respected. To control the number of successful or failed consecutive probes, set the property `probeThreshold` to `2`. It's currently not possible to set this property by using the Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe) or the [PowerShell](/powershell/module/az.network/set-azloadbalancerprobeconfig) command.