Merge pull request #212651 from rdeltcheva/sapha-smp-1

Minor fixes based on feedback

Author: prmerger-automator[bot]

articles/virtual-machines/workloads/sap/get-started.md

@@ -13,7 +13,7 @@ ms.assetid: ad8e5c75-0cf6-4564-ae62-ea1246b4e5f2
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 09/14/2022
+ms.date: 09/27/2022
 ms.author: juergent
 ms.custom: H1Hack27Feb2017
 
@@ -66,6 +66,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- September 27, 2022: Minor changes in [HA for SAP ASCS/ERS with NFS simple mount](./high-availability-guide-suse-nfs-simple-mount.md) on SLES 15 for SAP Applications to adjust mount instructions
 - September 14, 2022 Release of updated SAP on Oracle guide with new and updated content [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms_guide_oracle.md)
 - September 8, 2022: Change in [SAP HANA scale-out HSR with Pacemaker on Azure VMs on SLES](./sap-hana-high-availability-scale-out-hsr-suse.md) to add instructions for deploying /hana/shared (only) on NFS on Azure Files
 - September 6, 2022: Add managed identity for pacemaker fence agent [Set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure](high-availability-guide-suse-pacemaker.md) on SLES and [Setting up Pacemaker on RHEL in Azure](high-availability-guide-rhel-pacemaker.md) RHEL

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

@@ -13,7 +13,7 @@ ms.service: virtual-machines-sap
 ms.topic: tutorial
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 08/05/2022
+ms.date: 09/27/2022
 ms.author: radeltch
 
 ---
@@ -268,10 +268,10 @@ When you plan your deployment with NFS on Azure Files, consider the following im
 1. Delegate a subnet to Azure NetApp Files, as described in [these instructions](../../../azure-netapp-files/azure-netapp-files-delegate-subnet.md).  
 1. Deploy Azure NetApp Files volumes by following [these instructions](../../../azure-netapp-files/azure-netapp-files-create-volumes.md). Deploy the volumes in the designated Azure NetApp Files [subnet](/rest/api/virtualnetwork/subnets). The IP addresses of the Azure NetApp 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. This example uses two Azure NetApp Files volumes: `sapNW1` and `trans`. The file paths that are mounted to the corresponding mount points are:  
+   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. This example uses two Azure NetApp Files volumes: `sapnw1` and `trans`. The file paths that are mounted to the corresponding mount points are:  
 
-   - Volume `sapNW1` (`nfs://10.27.1.5/usrsapnw1/sapmntNW1`)
-   - Volume `sapNW1` (`nfs://10.27.1.5/usrsapnw1/usrsapNW1`)
+   - Volume `sapnw1` (`nfs://10.27.1.5/sapnw1/sapmntNW1`)
+   - Volume `sapnw1` (`nfs://10.27.1.5/sapnw1/usrsapNW1`)
    - Volume `trans` (`nfs://10.27.1.5/trans`)
 
 
@@ -391,7 +391,7 @@ The following items are prefixed with:
     ```bash
     # Temporarily mount the volume.
     sudo mkdir -p /saptmp
-    sudo mount -t nfs sapnfs.file.core.windows.net:/sapnfsafs/sapnw1 /saptmp -o vers=4,minorversion=1,sec=sys
+    sudo mount -t nfs sapnfsafs.file.core.windows.net:/sapnfsafs/sapnw1 /saptmp -o vers=4,minorversion=1,sec=sys
     # Create the SAP directories.
     sudo cd /saptmp
     sudo mkdir -p sapmntNW1
@@ -455,7 +455,7 @@ The instructions in this section are applicable only if you're using Azure NetAp
        cat /sys/module/nfs/parameters/nfs4_disable_idmapping
        # If you need to set nfs4_disable_idmapping to Y:
        mkdir /mnt/tmp
-       mount 10.27.1.5:/sapmnt/<b>qas</b> /mnt/tmp
+       mount 10.27.1.5:/sapnw1 /mnt/tmp
        umount  /mnt/tmp
        echo "Y" > /sys/module/nfs/parameters/nfs4_disable_idmapping
        # Make the configuration permanent.