Merge branch 'master' of https://github.com/Rajani-janaki-ram/azure-docs-pr

Rajani-Janaki-Ram · Rajani-Janaki-Ram · commit 16c69dcde0f8 · 2019-08-08T15:44:05.000+05:30
diff --git a/articles/site-recovery/azure-to-azure-customize-networking.md b/articles/site-recovery/azure-to-azure-customize-networking.md
@@ -24,34 +24,34 @@ The following key resource configurations can be provided for the failover VM wh
 
 - [Internal Load Balancer](https://docs.microsoft.com/azure/load-balancer/load-balancer-standard-overview#what-is-standard-load-balancer)
 - [Public IP](https://docs.microsoft.com/azure/virtual-network/virtual-network-ip-addresses-overview-arm#public-ip-addresses)
-- [Network Security Group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group) both for the subnet and for the NIC.
+- [Network Security Group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group) both for the subnet and for the NIC
 
 ## Pre-requisites
 
 - Ensure that you plan your recovery side configurations in advance.
-- You need to pre-create the networking resources in advance, provide it as an input so that Azure Site Recovery service can honor these settings and ensure that the failover VM adheres to these settings.
+- You need to create the networking resources in advance. Provide it as an input so that Azure Site Recovery service can honor these settings and ensure that the failover VM adheres to these settings.
 
 ## Steps to customize failover networking configurations
 
 1. Navigate to **Replicated Items**. 
 2. Click on the desired Azure VM.
-3. Click on **Compute and Network**, and **Edit**. You will notice that the NIC configuration settings include the corresponding resources at the source 
+3. Click on **Compute and Network**, and **Edit**. You will notice that the NIC configuration settings include the corresponding resources at the source. 
 
      ![customize](media/azure-to-azure-customize-networking/edit-networking-properties.png)
 
-4. Click **Edit** near the NIC you want to configure, in the next blade that opens up, select the corresponding pre-created resources in the target.
+4. Click **Edit** near the NIC you want to configure. In the next blade that opens up, select the corresponding pre-created resources in the target.
 
     ![NIC-drilldown](media/azure-to-azure-customize-networking/nic-drilldown.png) 
 
-5. Click **Ok**
+5. Click **OK**.
 
 Site Recovery will now honor these settings and ensure that the VM on failover is connected to the selected resource via the corresponding NIC.
 
 ## Troubleshooting
 
 ### Unable to view or select a resource
 
-If you are unable to select or view a networking resource, please go through the following checks & conditions
+If you are unable to select or view a networking resource, please go through the following checks & conditions:
 
 - The target field for a networking resource is only enabled if the source VM had a corresponding input. This is based on the principle that for a disaster recovery scenario, you would want either the exact or a scaled down version of your source.
 - For each of the networking resources in question some filters are applied in the dropdown to ensure that the failover VM can attach itself to the resource selected and the failover reliability is maintained. These filters are based on the same networking conditions that would have been verified when you configured the source VM.
@@ -61,7 +61,7 @@ Internal load balancer validations:
 1. Subscription and Region of LB and the target VM should be the same.
 2. The virtual network associated with the Internal Load Balancer and that of the target VMshould be the same.
 3. The target VM’s Public IP SKU and the Internal Loadbalancer's SKU should be the same.
-4. If the target VM is configured to be placed in an availability zone, then check if the load balancer is zone redundant or part of any availability zone. (Basic SKU Load Balancers do not support zones and will not be shown in the drop-down in this case)
+4. If the target VM is configured to be placed in an availability zone, then check if the load balancer is zone redundant or part of any availability zone. (Basic SKU Load Balancers do not support zones and will not be shown in the drop-down in this case.)
 5. Ensure that the Internal LoadBalancer has a pre-created backend pool and front-end configuration.
 
 
@@ -75,4 +75,4 @@ Network security group:
 
 
 > [!WARNING]
-> If the target VM is associated to an Availability Set, then you  need to associate the Public IP/Internal Load balancer of the same SKU as that of other VM's Public IP/Internal Load balancer in the Availability Set. Failure to do so could result in failover failure.
+> If the target VM is associated to an Availability Set, then you  need to associate the Public IP/Internal Load balancer of the same SKU as that of other VM's Public IP/Internal Load balancer in the Availability Set. Failure to do so could result in failover failure.
