Changes as per finding

Author: dennispadia

articles/sap/workloads/disaster-recovery-sap-hana.md

@@ -61,7 +61,7 @@ Example of a multi-target system replication system. For more information, see [
 ![Diagram showing an example of a HANA scale-up multi-target system replication system.](./media/sap-hana-high-availability/sap-hana-high-availability-scale-up-hsr-multi-target.png)
 
 1. Deploy Azure resources for the third node. Depending on your requirements, you can use a different Azure region for disaster recovery purposes.  
-   Steps required for the third site are similar to [virtual machines for HANA scale-up cluster](./sap-hana-high-availability.md#deploy-for-linux). Third site will use Azure infrastructure, operating system and HANA version matching the existing Pacemaker cluster, with the following exceptions:
+   Steps required for the third site are similar to [virtual machines for HANA scale-up cluster](./sap-hana-high-availability.md#prepare-the-infrastructure). Third site will use Azure infrastructure, operating system and HANA version matching the existing Pacemaker cluster, with the following exceptions:
    - No load balancer deployed for third site and no integration with existing cluster load balancer for the VM of third site
    - Don't install OS packages SAPHanaSR, SAPHanaSR-doc and OS package pattern ha_sles on third site VM
    - No integration into the cluster for VM or HANA resources of the third site

articles/sap/workloads/sap-hana-high-availability.md

@@ -31,7 +31,7 @@ ms.author: radeltch
 [2388694]:https://launchpad.support.sap.com/#/notes/2388694
 [401162]:https://launchpad.support.sap.com/#/notes/401162
 
-[sles-for-sap-bp]:https://www.suse.com/documentation/sles-for-sap-12/
+[sles-for-sap-bp]:https://documentation.suse.com/sbp-supported.html
 
 [sap-swcenter]:https://launchpad.support.sap.com/#/softwarecenter
 
@@ -46,7 +46,6 @@ This article describes how to deploy and configure the VMs, install the cluster
 Before you begin, read the following SAP Notes and papers:
 
 - SAP Note [1928533]. The note includes:
-
   - The list of Azure VM sizes that are supported for the deployment of SAP software.
   - Important capacity information for Azure VM sizes.
   - The supported SAP software, operating system (OS), and database combinations.
@@ -65,10 +64,9 @@ Before you begin, read the following SAP Notes and papers:
 - [Azure Virtual Machines planning and implementation for SAP on Linux][planning-guide] guide.
 - [Azure Virtual Machines deployment for SAP on Linux][deployment-guide] guide.
 - [Azure Virtual Machines DBMS deployment for SAP on Linux][dbms-guide] guide.
-- [SUSE Linux Enterprise Server for SAP Applications 12 SP3 best practices guides][sles-for-sap-bp]:
-
-  - Setting up an SAP HANA SR Performance Optimized Infrastructure (SLES for SAP Applications 12 SP1). The guide contains all the required information to set up SAP HANA system replication for on-premises development. Use this guide as a baseline.
-  - Setting up an SAP HANA SR Cost Optimized Infrastructure (SLES for SAP Applications 12 SP1).
+- [SUSE Linux Enterprise Server for SAP Applications best practices guides][sles-for-sap-bp]:
+  - Setting up an SAP HANA SR Performance Optimized Infrastructure (SLES for SAP Applications). The guide contains all the required information to set up SAP HANA system replication for on-premises development. Use this guide as a baseline.
+  - Setting up an SAP HANA SR Cost Optimized Infrastructure (SLES for SAP Applications).
 
 ## Plan for SAP HANA high availability
 

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

@@ -25,6 +25,7 @@ az network nic ip-config address-pool add --address-pool MyBackendPool --ip-conf
 ```
 
 <details>
+
 <summary>Expand to view full CLI code</summary>
 
 ```azurecli-interactive

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

@@ -9,22 +9,22 @@ author: dennispadia
 ms.author: depadia
 ---
 
-Follow [create load balancer](https://learn.microsoft.com/azure/load-balancer/quickstart-load-balancer-standard-internal-portal#create-load-balancer) guide to set up a standard load balancer for a high availability SAP system using the Azure portal. During the set up of load balancer, follow below consideration.
+Follow [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 using the Azure portal. During the setup of load balancer, consider following points.
 
-1. **Frontend IP Configuration:** Create frontend IP. Select the same virtual network and subnet as that of your ASCS/ERS virtual machines.
+1. **Frontend IP Configuration:** Create frontend IP. Select the same virtual network and subnet same as your DB virtual machines.
 2. **Backend Pool:** Create backend pool and add DB VMs.
 3. **Inbound rules:** Create load balancing rule. Follow the same steps for both load balancing rules.
      - Frontend IP address: Select frontend IP
      - Backend pool: Select backend pool
      - Check "High availability ports"
      - Protocol: TCP
-           - Health Probe: Create health probe with below details
-             - Protocol: TCP
-             - Port: [eg: 625<instance-no.>]
-             - Interval: 5
+     - Health Probe: Create health probe with below details
+       - Protocol: TCP
+       - Port: [for example: 625<instance-no.>]
+       - Interval: 5
      - Idle timeout (minutes): 30
      - Check "Enable Floating IP"
 
 > [!NOTE]
 >
-> Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, isn't respected. So to control the number of successful or failed consecutive probes, set the property "probeThreshold" to 2. It is currently not possible to set this property using Azure portal, so use either the [Azure CLI](https://learn.microsoft.com/cli/azure/network/lb/probe?view=azure-cli-latest) or [PowerShell](https://learn.microsoft.com/powershell/module/az.network/new-azloadbalancerprobeconfig?view=azps-11.1.0) command.
+> Health probe configuration property numberOfProbes, otherwise known as "Unhealthy threshold" in Portal, isn't respected. So to control the number of successful or failed consecutive probes, set the property "probeThreshold" to 2. It is currently not possible to set this property using Azure portal, so use either the [Azure CLI](/cli/azure/network/lb/probe?view=azure-cli-latest) or [PowerShell](/powershell/module/az.network/new-azloadbalancerprobeconfig?view=azps-11.1.0) command.

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

@@ -27,6 +27,7 @@ $lb = New-AzLoadBalancer -ResourceGroupName MyResourceGroup -Name MyLB -Location
 ```
 
 <details>
+
 <summary>Expand to view full PowerShell code</summary>
 
 ```azurepowershell-interactive