Suggestions from PR review

Rajeswari-Mamilla · Rajeswari-Mamilla · commit 455bbf9cf99d · 2019-10-22T14:36:12.000+05:30
diff --git a/articles/site-recovery/vmware-azure-deploy-configuration-server.md b/articles/site-recovery/vmware-azure-deploy-configuration-server.md
@@ -32,14 +32,14 @@ Minimum hardware requirements for a configuration server are summarized in the f
 You require a user with **one of the following** permissions set in AAD (Azure Active Directory) to register configuration server with Azure Site Recovery services.
 
 1. User should have “Application developer” role to create application.
-   1. To verify, Sign in to Azure portal</br>
-   1. Navigate to Azure Active Directory > Roles and administrators</br>
-   1. Verify if "Application developer" role is assigned to the user. If not, use a user with this permission or reach out to [administrator to enable the permission](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal#assign-roles).
+    - To verify, Sign in to Azure portal</br>
+    - Navigate to Azure Active Directory > Roles and administrators</br>
+    - Verify if "Application developer" role is assigned to the user. If not, use a user with this permission or reach out to [administrator to enable the permission](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal#assign-roles).
     
-1. If the "Application developer" role cannot be assigned, ensure that "User can register application” flag is set as true for user to create identity. To enable above permissions,
-   1. Sign in to Azure portal
-   1. Navigate to Azure Active Directory > User settings
-   1. Under **App registrations", "Users can register applications" should be chosen as "Yes".
+2. If the "Application developer" role cannot be assigned, ensure that "User can register application” flag is set as true for user to create identity. To enable above permissions,
+    - Sign in to Azure portal
+    - Navigate to Azure Active Directory > User settings
+    - Under **App registrations", "Users can register applications" should be chosen as "Yes".
 
       ![AAD_application_permission](media/vmware-azure-deploy-configuration-server/AAD_application_permission.png)
 
@@ -129,17 +129,17 @@ If you want to add an additional NIC to the configuration server, add it before
 
 ## Upgrade the configuration server
 
-To upgrade the configuration server to the latest version, follow these [steps](vmware-azure-manage-configuration-server.md#upgrade-the-configuration-server). For detailed instructions on how to upgrade all Site Recovery components, click [here](service-updates-how-to.md).
+To upgrade the configuration server to the latest version, follow these [steps](vmware-azure-manage-configuration-server.md#upgrade-the-configuration-server). For detailed instructions on how to upgrade all Site Recovery components, visit [service update management](service-updates-how-to.md).
 
 ## Manage the configuration server
 
 To avoid interruptions in ongoing replication, ensure that IP address of the configuration server does not change after the configuration server has been registered to a vault. You can learn more about common configuration server management tasks [here](vmware-azure-manage-configuration-server.md).
 
 ## FAQ
 
-1. How long is the Licence provided on configuration server deployed through OVF is valid? What happens if I do not reactivate the License?
+1. How long is the License provided on configuration server deployed through OVF is valid? What happens if I do not reactivate the License?
 
-    The license provided with OVA template is an evaluation license valid for 180 days. Before expiry, you need to activate the license. Else, this can result in frequent shutdown of configuration server and thus cause hinderance to replication activities.
+    The license provided with OVA template is an evaluation license valid for 180 days. Before expiry, you need to activate the license. Else, it can result in frequent shutdown of configuration server and thus cause hindrance to replication activities. For additional details, refer to article on [manage configuration server license](vmware-azure-manage-configuration-server.md#update-windows-license).
 
 2. Can I use the VM, where the configuration server is installed, for different purposes?
 
diff --git a/articles/site-recovery/vmware-azure-manage-configuration-server.md b/articles/site-recovery/vmware-azure-manage-configuration-server.md
@@ -16,6 +16,10 @@ You set up an on-premises configuration server when you use [Azure Site Recovery
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
+## Update Windows license
+
+The license provided with the OVF template is an evaluation license valid for 180 days. For uninterrupted usage, you must activate Windows with a procured license. License update can be done either through a standalone key or KMS standard key. Guidance is available at [DISM Windows command line for running OS](https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-windows-edition-servicing-command-line-options). To obtain keys, refer to [KMS client set up](https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys).
+
 ## Access configuration server
 
 You can access the configuration server as follows:
@@ -288,10 +292,6 @@ For configuration server deployments before May 2016, certificate expiry was set
 3. On the blade with details of chosen configuration server, click **More** > **Refresh Server**.
 4. Monitor the progress of the job under **Recovery Services Vault** > **Monitoring** > **Site Recovery jobs**.
 
-## Update Windows license
-
-The license provided with the OVF template is an evaluation license valid for 180 days. For uninterrupted usage, you must activate Windows with a procured license.
-
 ## Failback requirements
 
 During reprotect and failback, the on-premises configuration server must be running and in a connected state. For successful failback, the virtual machine being failed back must exist in the configuration server database.
diff --git a/articles/site-recovery/vmware-azure-set-up-source.md b/articles/site-recovery/vmware-azure-set-up-source.md
@@ -13,7 +13,7 @@ ms.author: ramamill
 
 # Set up the source environment for VMware to Azure replication
 
-This article describes how to set up your source on-premises environment, to replicate VMware VMs to Azure. It includes steps for selecting your replication scenario, setting up an on-premises machine as the Site Recovery configuration server, and automatically discovering on-premises VMs. 
+This article describes how to set up your source on-premises environment, to replicate VMware VMs to Azure. Article includes steps for selecting your replication scenario, setting up an on-premises machine as the Site Recovery configuration server, and automatically discovering on-premises VMs. 
 
 ## Prerequisites
 
@@ -65,7 +65,7 @@ Exclude following folders from Antivirus software for smooth replication and to
   - C:\ProgramData\ASRSetupLogs
   - C:\ProgramData\LogUploadServiceLogs
   - C:\inetpub
-  - ASR server installation directory. For example: E:\Program Files (x86)\Microsoft Azure Site Recovery
+  - Site Recovery server installation directory. For example: E:\Program Files (x86)\Microsoft Azure Site Recovery
 
 ### If Antivirus Software is active on scale-out Process server/Master Target
 
@@ -77,7 +77,7 @@ Exclude following folders from Antivirus software
 4. C:\ProgramData\ASRSetupLogs
 5. C:\ProgramData\LogUploadServiceLogs
 6. C:\ProgramData\Microsoft Azure Site Recovery
-7. ASR load balanced process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery
+7. Azure Site Recovery load balanced process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery
 
 
 ## Next steps
diff --git a/includes/site-recovery-configuration-and-scaleout-process-server-requirements.md b/includes/site-recovery-configuration-and-scaleout-process-server-requirements.md
@@ -15,7 +15,7 @@ ms.custom: include file
 **Configuration/Process server requirements**
 
 
-## HARDWARE Requirements
+## Hardware Requirements
 
 **Component** | **Requirement** 
 --- | ---
@@ -34,7 +34,7 @@ Operating system | Windows Server 2012 R2 <br> Windows Server 2016
 Operating system locale | English (en-us)
 Windows Server roles | Don't enable these roles: <br> - Active Directory Domain Services <br>- Internet Information Services <br> - Hyper-V 
 Group policies | Don't enable these group policies: <br> - Prevent access to the command prompt. <br> - Prevent access to registry editing tools. <br> - Trust logic for file attachments. <br> - Turn on Script Execution. <br> [Learn more](https://technet.microsoft.com/library/gg176671(v=ws.10).aspx)
-IIS | - No pre-existing default website <br> - No preexisting website/application listening on port 443 <br>- Enable  [anonymous authentication](https://technet.microsoft.com/library/cc731244(v=ws.10).aspx) <br> - Enable [FastCGI](https://technet.microsoft.com/library/cc753077(v=ws.10).aspx) setting 
+IIS | - No pre-existing default website <br> - No pre-existing website/application listening on port 443 <br>- Enable  [anonymous authentication](https://technet.microsoft.com/library/cc731244(v=ws.10).aspx) <br> - Enable [FastCGI](https://technet.microsoft.com/library/cc753077(v=ws.10).aspx) setting 
 | 
 
 ## Network requirements
@@ -52,10 +52,10 @@ NIC type | VMXNET3 (if the Configuration Server is a VMware VM)
 \*.hypervrecoverymanager.windowsazure.com | Used for replication management operations and coordination
 https:\//management.azure.com | Used for replication management operations and coordination 
 *.services.visualstudio.com | Used for telemetry purposes (It is optional)
-time.nist.gov | Used to check time synchronization between system and global time.
+time.nist.gov | Used to check time synchronization between system and global time.s
 time.windows.com | Used to check time synchronization between system and global time.
-| <ul> <li> https:\//login.microsoftonline.com </li><li> https:\//secure.aadcdn.microsoftonline-p.com </li><li> https:\//login.live.com </li><li> https:\//graph.windows.net </li><li> https:\//login.windows.net </li><li> https:\//www.live.com </li><li> https:\//www.microsoft.com </li></ul> | OVF set up needs access to these URLs. They are used for access control and identity management by Azure Active Directory
-https:\//dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi  | To complete MySQL download. </br> In few regions, the download might be re-directed to CDN URL. Ensure that the CDN URL is also whitelisted, if required.
+| <ul> <li> https:\//login.microsoftonline.com </li><li> https:\//secure.aadcdn.microsoftonline-p.com </li><li> https:\//login.live.com </li><li> https:\//graph.windows.net </li><li> https:\//login.windows.net </li><li> https:\//www.live.com </li><li> https:\//www.microsoft.com </li></ul> | OVF set-up needs access to these URLs. They are used for access control and identity management by Azure Active Directory
+https:\//dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi  | To complete MySQL download. </br> In few regions, the download might be redirected to CDN URL. Ensure that the CDN URL is also whitelisted, if necessary.
 |
 
 ## Required software
@@ -72,7 +72,7 @@ The following table summarizes capacity requirements for the configuration serve
 
 **CPU** | **Memory** | **Cache disk** | **Data change rate** | **Replicated machines**
 --- | --- | --- | --- | ---
-8 vCPUs<br/><br/> 2 sockets * 4 cores \@ 2.5 GHz | 16GB | 300 GB | 500 GB or less | < 100 machines
+8 vCPUs<br/><br/> 2 sockets * 4 cores \@ 2.5 GHz | 16 GB | 300 GB | 500 GB or less | < 100 machines
 12 vCPUs<br/><br/> 2 socks  * 6 cores \@ 2.5 GHz | 18 GB | 600 GB | 500 GB-1 TB | 100 to 150 machines
 16 vCPUs<br/><br/> 2 socks  * 8 cores \@ 2.5 GHz | 32 GB | 1 TB | 1-2 TB | 150 -200 machines
 
