more edits

TedA-M · TedA-M · commit 47d40dfaf00d · 2020-02-12T11:06:56.000-08:00
diff --git a/articles/site-recovery/azure-to-azure-common-questions.md b/articles/site-recovery/azure-to-azure-common-questions.md
@@ -9,7 +9,7 @@ ms.topic: conceptual
 ---
 # Common questions: Azure-to-Azure disaster recovery
 
-This article answers common questions about disaster recovery for when you use [Azure Site Recovery](site-recovery-overview.md).
+This article answers common questions about disaster recovery of Azure VMs to another Azure region for when you use [Azure Site Recovery](site-recovery-overview.md).
 
 ## General
 
@@ -23,7 +23,7 @@ Every instance that is protected with Azure Site Recovery is free for the first
 
 ### During the first 31 days, will I incur any other Azure charges?
 
-Yes. Even though Azure Site Recovery is free during the first 31 days of a protected instance, you might incur charges for Azure Storage, storage transactions, and data transfers. A recovered Virtual Machine might also incur Azure compute charges. Get complete details on pricing at [Azure Site Recovery pricing](https://azure.microsoft.com/pricing/details/site-recovery)
+Yes. Even though Azure Site Recovery is free during the first 31 days of a protected instance, you might incur charges for Azure Storage, storage transactions, and data transfers. A recovered Virtual Machine might also incur Azure compute charges. Get complete details on pricing at [Azure Site Recovery pricing](https://azure.microsoft.com/pricing/details/site-recovery).
 
 ### What are the best practices for Azure Virtual Machines disaster recovery?
 
@@ -41,11 +41,11 @@ The Site Recovery team and Azure capacity management team plan for sufficient in
 
 ### Can I replicate VMs enabled through Azure disk encryption?
 
-Yes. Site Recovery supports disaster recovery of VMs that have Azure disk encryption (ADE) enabled. When you enable replication, Azure copies all the required disk encryption keys and secrets from the source region to the target region in the user context. If you don't have the appropriate permissions, your security administrator can use a script to copy the keys and secrets.
+Yes. Site Recovery supports disaster recovery of VMs that have Azure Disk Encryption enabled. When you enable replication, Azure copies all the required disk encryption keys and secrets from the source region to the target region in the user context. If you don't have the appropriate permissions, your security administrator can use a script to copy the keys and secrets.
 
-- Site Recovery supports ADE for Azure VMs that are running Windows.
-- Site Recovery supports ADE version 0.1, which has a schema that requires Azure Active Directory (Azure AD). Site Recovery also supports version 1.1, which doesn't require Azure AD. [Learn more about the extension schemata for Azure disk encryption](../virtual-machines/extensions/azure-disk-enc-windows.md#extension-schemata).
-  - For ADE version 1.1, you have to use the Windows VMs with managed disks.
+- Site Recovery supports Azure Disk Encryption for Azure VMs that are running Windows.
+- Site Recovery supports Azure Disk Encryption version 0.1, which has a schema that requires Azure Active Directory (Azure AD). Site Recovery also supports version 1.1, which doesn't require Azure AD. [Learn more about the extension schemata for Azure disk encryption](../virtual-machines/extensions/azure-disk-enc-windows.md#extension-schemata).
+  - For Azure Disk Encryption version 1.1, you have to use the Windows VMs with managed disks.
   - [Learn more](azure-to-azure-how-to-enable-replication-ade-vms.md) about enabling replication for encrypted VMs.
 
 ### Can I replicate VMs to another subscription?
@@ -72,8 +72,7 @@ Yes, adding new disks to replicated VMs and enabling replication for them is sup
 
 For example, let's say a VM has a single disk and you add a new one. There might be a replication point that was created before you added the disk. This replication point will show that it consists of "1 of 2 disks."
 
-Site Recovery doesn’t support “hot remove” of a disk from a replicated VM. If you remove a VM disk, you need to disable and then re-enable replication for the VM.
-
+Site Recovery doesn’t support "hot remove" of a disk from a replicated VM. If you remove a VM disk, you need to disable and then re-enable replication for the VM.
 
 ### How often can I replicate to Azure?
 
@@ -167,27 +166,27 @@ Yes, if you increase the retention period from 24 hours to 72 hours, Site Recove
 
 ## Multi-VM consistency
 
-### What is Multi-VM consistency?
+### What is multi-VM consistency?
 
 Multi-VM consistency ensures that the recovery point is consistent across all the replicated virtual machines.
 
 Site Recovery provides a **Multi-VM consistency** option, which creates a replication group of all the machines.
 
 When you fail over the virtual machines, they'll have shared crash-consistent and app-consistent recovery points.
 
-Go through the tutorial to [enable Multi-VM consistency](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-tutorial-enable-replication#enable-replication-for-a-vm).
+Go through the tutorial to [enable multi-VM consistency](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-tutorial-enable-replication#enable-replication-for-a-vm).
 
-### Can I fail over a single virtual machine within a Multi-VM consistency replication group?
+### Can I fail over a single virtual machine within a multi-VM consistency replication group?
 
 When you select the **Multi-VM consistency** option, you're stating that the application has a dependency on all the virtual machines within a group. Single virtual machine failover isn't allowed.
 
-### How many virtual machines can I replicate as a part of a Multi-VM consistency replication group?
+### How many virtual machines can I replicate as a part of a multi-VM consistency replication group?
 
 You can replicate 16 virtual machines together in a replication group.
 
-### When should I enable Multi-VM consistency?
+### When should I enable multi-VM consistency?
 
-Because Multi-VM consistency is CPU intensive, enabling it can affect workload performance. Use Multi-VM consistency only if machines are running the same workload and you need consistency across multiple machines. For example, if you have two SQL Server instances and two web servers in an application, you should have Multi-VM consistency for the SQL Server instances only.
+Because multi-VM consistency is CPU intensive, enabling it can affect workload performance. Use multi-VM consistency only if machines are running the same workload and you need consistency across multiple machines. For example, if you have two SQL Server instances and two web servers in an application, you should have multi-VM consistency for the SQL Server instances only.
 
 ## Failover
 
@@ -292,6 +291,7 @@ Yes, you can purchase [reserved Azure VMs](https://azure.microsoft.com/pricing/r
 ### Is replication data sent to the Site Recovery service?
 
 No, Site Recovery doesn't intercept replicated data, and it doesn't have any information about what's running on your VMs. Only the metadata needed to orchestrate replication and failover is sent to the Site Recovery service.  
+
 Site Recovery is ISO 27001:2013, 27018, HIPAA, and DPA certified. The service is undergoing SOC2 and FedRAMP JAB assessments.
 
 ### Does Site Recovery encrypt replication?
diff --git a/articles/site-recovery/azure-to-azure-troubleshoot-replication.md b/articles/site-recovery/azure-to-azure-troubleshoot-replication.md
@@ -21,7 +21,7 @@ The following sections describe causes and solutions.
 ## <a name="high-data-change-rate-on-the-source-virtal-machine"></a>High data change rate on the source virtual machine
 
 Azure Site Recovery creates an event if the data change rate on the source virtual machine is higher than the supported limits. To see whether the problem is because of high churn, go to **Replicated items** > **VM** > **Events - last 72 hours**.
-You should see the event “Data change rate beyond supported limits”:
+You should see the event "Data change rate beyond supported limits":
 
 ![Azure Site Recovery page that shows a high data change rate that is too high](./media/site-recovery-azure-to-azure-troubleshoot/data_change_event.png)
 
@@ -33,7 +33,7 @@ If you select the event, you should see the exact disk information:
 
 The following table provides the Azure Site Recovery limits. These limits are based on our tests, but they can't cover all possible application input-output (I/O) combinations. Actual results can vary based on your application I/O mix.
 
-There are two limits to consider: data churn per disk and data churn per virtual machine. Let's look at the Premium P20 disk in the following table for an example. For a single VM, Site Recovery can handle 5 MB/s of churn per disk with a maximum of five such disks. Site Recovery's limit is 25 MB/s of total churn per VM.
+There are two limits to consider: data churn per disk and data churn per virtual machine. Let's look at the Premium P20 disk in the following table for an example. For a single VM, Site Recovery can handle 5 MB/s of churn per disk with a maximum of five such disks. Site Recovery has a limit of 25 MB/s of total churn per VM.
 
 **Replication storage target** | **Average I/O size for source disk** |**Average data churn for source disk** | **Total data churn per day for source data disk**
 ---|---|---|---
@@ -80,7 +80,7 @@ For Site Recovery replication to work, it needs the VM to provide outbound conne
 
 ## Error ID 153006 - No app-consistent recovery point available for the VM in the past "X" minutes
 
-Some of the most common issues are listed below:
+Following are some of the most common issues.
 
 #### Known issue in SQL server 2008/2008 R2
 
@@ -109,7 +109,7 @@ To locate the errors in the file, search for the string "vacpError" by opening t
 
 	Ex: vacpError:220#Following disks are in FilteringStopped state [\\.\PHYSICALDRIVE1=5, ]#220|^|224#FAILED: CheckWriterStatus().#2147754994|^|226#FAILED to revoke tags.FAILED: CheckWriterStatus().#2147754994|^|
 
-In the above example **2147754994** is the error code that tells you about the failure as shown below.
+In the preceding example, **2147754994** is the error code that tells you about the failure following this sentence.
 
 #### VSS writer is not installed - Error 2147221164
 
@@ -131,12 +131,13 @@ If VSS is disabled:
 
 **How to fix**: To generate the application consistency tag, Azure Site Recovery uses VSS. Check whether the Azure Site Recovery VSS Provider service is installed.
 
-Use the following commands to reinstall the VSS Provider:
-1. Uninstall existing provider: `C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Uninstall.cmd`
-1. Reinstall: `C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd`
+Use the following commands to reinstall VSS Provider:
+1. Uninstall existing provider: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Uninstall.cmd
+1. Reinstall VSS Provider: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\InMageVSSProvider_Install.cmd
 
 Verify that the startup type of the VSS Provider service is set to **Automatic**.
-    - Restart the following services:
-        - VSS service
-        - Azure Site Recovery VSS Provider
-        - VDS service
+
+Restart the following services:
+- VSS service
+- Azure Site Recovery VSS Provider
+- VDS service
diff --git a/articles/site-recovery/site-recovery-extension-troubleshoot.md b/articles/site-recovery/site-recovery-extension-troubleshoot.md
@@ -88,7 +88,7 @@ Most agent-related or extension-related failures for Linux VMs are caused by iss
 
 ### The Site Recovery extension fails to update or load
 
-The extension status shows as "Empty," "NotReady," or Transitioning.
+The extension status shows as "Empty," "NotReady," or "Transitioning."
 
 #### Solution
 
diff --git a/articles/site-recovery/site-recovery-sap.md b/articles/site-recovery/site-recovery-sap.md
@@ -34,11 +34,11 @@ Before you begin, ensure that you know how to do the following tasks:
 
 You can use Site Recovery to implement a disaster recovery solution in the following scenarios:
 * You have SAP systems running in one Azure datacenter, and you're replicating them to another Azure datacenter (Azure-to-Azure disaster recovery). 
-   * For more information, see [Azure-to-Azure replication architecture](https://aka.ms/asr-a2a-architecture).
+   For more information, see [Azure-to-Azure replication architecture](https://aka.ms/asr-a2a-architecture).
 * You have SAP systems running on VMware (or physical) servers on-premises. You're also replicating the SAP systems to a disaster recovery site in an Azure datacenter (VMware-to-Azure disaster recovery). 
-   * This scenario requires some additional components. For more information, see [VMware-to-Azure replication architecture](https://aka.ms/asr-v2a-architecture).
+   This scenario requires some additional components. For more information, see [VMware-to-Azure replication architecture](https://aka.ms/asr-v2a-architecture).
 * You have SAP systems running on Hyper-V on-premises. You're also replicating the SAP systems to a disaster recovery site in an Azure datacenter (Hyper-V-to-Azure disaster recovery).
-   * This scenario requires some additional components. For more information, see [Hyper-V-to-Azure replication architecture](https://aka.ms/asr-h2a-architecture).
+   This scenario requires some additional components. For more information, see [Hyper-V-to-Azure replication architecture](https://aka.ms/asr-h2a-architecture).
 
 In this article, we use an **Azure-to-Azure** disaster recovery scenario. The scenario shows you the SAP disaster recovery capabilities of Site Recovery. Because Site Recovery replication isn't application-specific, the process that's described is expected to also apply to other scenarios.
 
@@ -67,12 +67,12 @@ The Web Dispatcher component works as a load balancer for SAP traffic among the
 The SMLG transaction manages login groups for ABAP application servers. It uses the load-balancing function within the message server of the Central Services to distribute workload among SAP application server pools for SAPGUIs and RFC traffic. You can replicate this management by using Site Recovery.
 
 #### VMs running SAP Central Services clusters
-This reference architecture runs Central Services on VMs in the application tier. The Central Services is a potential single point of failure when in a single VM—typical deployment and high availability isn't a requirement.
+This reference architecture runs Central Services on VMs in the application tier. Central Services is a potential single point of failure when in a single VM. Typical deployment and high availability aren't requirements.
 
-To implement a high availability solution, you can use either a shared disk cluster or a file share cluster. To configure VMs for a shared disk cluster, use Windows Server Failover Cluster. We recommend that you use Cloud Witness as a quorum witness.
+To implement a high availability solution, you can use either a shared disk cluster or a file share cluster. To configure VMs for a shared disk cluster, use Windows Server Failover Cluster. We recommend that you use the cloud witness as a quorum witness.
 
  > [!NOTE]
- > Because Site Recovery does not replicate the cloud witness, we recommend that you deploy cloud witness in the disaster recovery region.
+ > Because Site Recovery does not replicate the cloud witness, we recommend that you deploy the cloud witness in the disaster recovery region.
 
 To support the failover cluster environment, [SIOS DataKeeper Cluster Edition](https://azuremarketplace.microsoft.com/marketplace/apps/sios_datakeeper.sios-datakeeper-8) does the cluster shared volume function. In the function, SIOS DataKeeper Cluster replicates independent disks owned by the cluster nodes. Because Azure does not natively support shared disks, it requires solutions provided by SIOS.
 
@@ -94,23 +94,23 @@ Following are the steps for setting up the disaster recovery:
 1. Do a test failover
 1. Do a failover
 
-Below is the recommendation for disaster recovery of each tier used in this example.
+Following is the recommendation for disaster recovery of each tier used in this example.
 
  **SAP tiers** | **Recommendation**
  --- | ---
 **SAP Web Dispatcher pool** |  Replicate by using Site Recovery 
 **SAP Application server pool** |  Replicate by using Site Recovery 
 **SAP Central Services cluster** |  Replicate by using Site Recovery 
 **Active directory virtual machines** |  Use Active directory replication 
-**SQL Database servers** |  Use SQL always on replication
+**SQL Database servers** |  Use SQL Server Always On replication
 
 ## Replicate virtual machines
 
 To start replicating all the SAP application virtual machines to the Azure disaster recovery datacenter, follow the guidance in [Replicate a virtual machine to Azure](azure-to-azure-walkthrough-enable-replication.md).
 
-* For guidance on protecting Active Directory and DNS, see [how to protect Active Directory and DNS](site-recovery-active-directory.md).
+* For guidance on protecting Active Directory and DNS, learn [how to protect Active Directory and DNS](site-recovery-active-directory.md).
 
-* For guidance on protecting database tier running on SQL server, see [how to protect SQL Server](site-recovery-sql.md).
+* For guidance on protecting database tier running on SQL server, learn [how to protect SQL Server](site-recovery-sql.md).
 
 ## Networking configuration
 
@@ -131,11 +131,11 @@ A recovery plan supports the sequencing of various tiers in a multi-tier applica
 ### Add scripts to the recovery plan
 For your applications to function correctly, you might need to do some operations on the Azure virtual machines. Do these operations after the failover or during a test failover. You can also automate some post-failover operations. For example, update the DNS entry, and change bindings and connections by adding corresponding scripts to the recovery plan.
 
-You can deploy the most used Site Recovery scripts into your Automation account by selecting **Deploy to Azure**. When you use any published script, follow the guidance in the script.
+You can deploy the most used Site Recovery scripts into your Azure Automation account by selecting **Deploy to Azure**. When you use any published script, follow the guidance in the script.
 
 [![Deploy to Azure](https://azurecomcdn.azureedge.net/mediahandler/acomblog/media/Default/blog/c4803408-340e-49e3-9a1f-0ed3f689813d.png)](https://aka.ms/asr-automationrunbooks-deploy)
 
-1. Add a pre-action script to Group 1 to fail over the SQL Availability group. Use the ASR-SQL-FailoverAG script published in the sample scripts. Follow the guidance in the script and make the required changes in the script appropriately.
+1. Add a pre-action script to Group 1 to fail over the SQL Server availability group. Use the ASR-SQL-FailoverAG script published in the sample scripts. Follow the guidance in the script and make the required changes in the script appropriately.
 1. Add a post-action script to attach a load balancer onto the failed-over virtual machines of the Web tier (Group 1). Use the ASR-AddSingleLoadBalancer script published in the sample scripts. Follow the guidance in the script and make the required changes in the script as needed.
 
 ![SAP Recovery Plan](./media/site-recovery-sap/sap_recovery_plan.png)
