Minor changes and add reference link to cost optimization scenario

Author: dennispadia

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

@@ -599,7 +599,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Update the /usr/sap/sapservices file
 
-   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
+   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
 
    ```
    sudo vi /usr/sap/sapservices
@@ -611,7 +611,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    # LD_LIBRARY_PATH=/usr/sap/QAS/ERS01/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/QAS/ERS01/exe/sapstartsrv pf=/usr/sap/QAS/ERS01/profile/QAS_ERS01_anftstsapers -D -u qasadm
    ```
 
-1. **[1]** Create the SAP cluster resources
+2. **[1]** Create the SAP cluster resources
 
    If using enqueue server 1 architecture (ENSA1), define the resources as follows:
 
@@ -739,7 +739,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
     #      rsc_sap_QAS_ERS01  (ocf::heartbeat:SAPInstance):   Started anftstsapcl1
    ```
 
-1. **[A]** Add firewall rules for ASCS and ERS on both nodes
+3. **[A]** Add firewall rules for ASCS and ERS on both nodes
    Add the firewall rules for ASCS and ERS on both nodes.
    ```
    # Probe Port of ASCS
@@ -1284,6 +1284,7 @@ Follow these steps to install an SAP application server.
 
 ## Next steps
 
+* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
 * [HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
 * [Azure Virtual Machines planning and implementation for SAP][planning-guide]
 * [Azure Virtual Machines deployment for SAP][deployment-guide]

articles/virtual-machines/workloads/sap/high-availability-guide-rhel-nfs-azure-files.md

@@ -585,7 +585,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Update the /usr/sap/sapservices file
 
-   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
+   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
 
     ```bash
     sudo vi /usr/sap/sapservices
@@ -868,6 +868,7 @@ Thoroughly test your Pacemaker cluster. [Execute the typical failover tests](./h
 
 ## Next steps
 
+* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
 * [HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
 * [Azure Virtual Machines planning and implementation for SAP][planning-guide]
 * [Azure Virtual Machines deployment for SAP][deployment-guide]

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

@@ -481,7 +481,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
 
 1. **[A]** Update the /usr/sap/sapservices file
 
-   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file. Do not comment out the SAP HANA instance if it will be used with HANA SR.
+   To prevent the start of the instances by the sapinit startup script, all instances managed by Pacemaker must be commented out from /usr/sap/sapservices file.
 
    <pre><code>
    sudo vi /usr/sap/sapservices
@@ -493,7 +493,7 @@ The following items are prefixed with either **[A]** - applicable to all nodes,
    # LD_LIBRARY_PATH=/usr/sap/<b>NW1</b>/ERS<b>02</b>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/<b>NW1</b>/ERS<b>02</b>/exe/sapstartsrv pf=/usr/sap/<b>NW1</b>/ERS<b>02</b>/profile/<b>NW1</b>_ERS<b>02</b>_<b>nw1-aers</b> -D -u <b>nw1</b>adm
    </code></pre>
 
-1. **[1]** Create the SAP cluster resources
+2. **[1]** Create the SAP cluster resources
 
   If using enqueue server 1 architecture (ENSA1), define the resources as follows:
 
@@ -1036,6 +1036,7 @@ Follow these steps to install an SAP application server.
 
 ## Next steps
 
+* To deploy cost optimization scenario where PAS and AAS instance is deployed with SAP NetWeaver HA cluster on RHEL, see [Install SAP Dialog Instance with SAP ASCS/SCS high availability VMs on RHEL](high-availability-guide-rhel-with-dialog-instance.md)
 * [HA for SAP NW on Azure VMs on RHEL for SAP applications multi-SID guide](./high-availability-guide-rhel-multi-sid.md)
 * [Azure Virtual Machines planning and implementation for SAP][planning-guide]
 * [Azure Virtual Machines deployment for SAP][deployment-guide]