review-2

Author: v-thpra

learn-pr/azure/protect-on-premises-infrastructure-with-azure-site-recovery/includes/2-azure-site-recovery-overview.md

@@ -18,7 +18,7 @@ As part of your BCDR plan, identify the recovery time objectives (RTOs) and reco
 
 ### Recovery time objective
 
-An RTO is a measure of the maximum amount of time your business can survive after a disaster until normal service must be restored in order to avoid unacceptable consequences associated with a break in continuity. Let's assume your RTO is 12 hours, which means that operations can continue for 12 hours without the business's core services functioning. If the downtime is any longer, your business would be seriously harmed.
+An RTO is a measure of the maximum amount of time your business can survive after a disaster until normal service must be restored to avoid any unacceptable consequences resulting from the break in continuity. Let's assume your RTO is 12 hours, which means that operations can continue for 12 hours without the business's core services functioning. If the downtime is any longer, your business would be seriously harmed.
 
 ### Recovery point objective
 
@@ -75,4 +75,4 @@ The status of the recovery job and the replicated virtual machine is accessed vi
 - **Warning**: There's an issue that could impact replication.
 - **Critical**: A critical replication error was detected.
 
-If all goes well, the replicated VM status is set to *Performed successfully*. If a test wasn't done, the status is set to *Test recommended*. The VM is also set to *Test recommended* if it's been more than six months since the last test.
+If all goes well, the replicated VM status is set to *Performed successfully*. If a test wasn't done, the status is set to *Test recommended*. The VM is also set to *Test recommended* if the last test was more than six months ago.

learn-pr/azure/protect-on-premises-infrastructure-with-azure-site-recovery/includes/3-workloads-supported-azure-site-recovery.md

@@ -24,7 +24,7 @@ Site Recovery provides application-aware replication for many types of workloads
 
 ### Active Directory and DNS
 
-Active Directory and DNS can be configured for an automated failover. Typically, they're completed first in the scope of the overall recovery plan. In this way, the Active Directory instance and DNS name resolution are available for when the other applications are failed over. You can have Active Directory up and running in a few minutes. Site Recovery protects the virtual machine that hosts your domain controller and DNS.
+Active Directory and DNS can be configured for an automated failover. Typically, they're completed first in the scope of the overall recovery plan. In this way, the Active Directory instance and Domain Name System (DNS) name resolution are available for when the other applications are failed over. You can have Active Directory up and running in a few minutes. Site Recovery protects the virtual machine that hosts your domain controller and DNS.
 
 ### SQL Server
 

learn-pr/azure/protect-on-premises-infrastructure-with-azure-site-recovery/includes/4-run-disaster-recovery-drill.md

@@ -6,7 +6,7 @@ In this unit, you gain an understanding of recovery time and recovery point obje
 
 ## Disaster recovery drill
 
-With Site Recovery, you can do a full disaster recovery test without affecting your existing live environment. Recovery plans are created within Site Recovery to allow the automation of recovery tasks and to model an app around its dependencies. Such as, the need for Active Directory or DNS to function. BCDR plans also allow you to test your disaster recovery.
+With Site Recovery, you can do a full disaster recovery test without affecting your existing live environment. Recovery plans are created within Site Recovery to allow the automation of recovery tasks and to model an app around its dependencies. Such as, the need for Active Directory or the Domain Name System (DNS) to function. BCDR plans also allow you to test your disaster recovery.
 
 After a BCDR plan is created in the Azure portal, it can be executed for test purposes. Follow these steps:
 
@@ -30,7 +30,7 @@ In the dashboard, you can monitor replicated items and test failovers. Each repl
 
 **(2) Replicated items** - **Healthy**: Replication is running normally with no warnings. **Warning** means that one or more issues were identified that could affect replication. **Critical** means that one or more critical replication errors were identified.
 
-**(3) Failover test success** - **Test recommended**: Specific machines haven't had a failover since Site Recovery protection was enabled. **Performed successfully** means that one or more machines replicated successfully. **Not applicable** means that machines aren't currently eligible for a test failover.
+**(3) Failover test success** - **Test recommended**: Indicates a machine that hasn't had a failover since Site Recovery protection was enabled. **Performed successfully** means that one or more machines replicated successfully. **Not applicable** means that machines aren't currently eligible for a test failover.
 
 **(4) Configuration issues** - **Missing configurations**: A necessary setting is missing. **Missing resources** means that a specified resource can't be found or isn't available. An example is a deleted resource such as a virtual network. **Subscription quota** shows the amount of resource available for your subscription and whether there's enough to do a failover. **Software updates** shows the availability of new software updates and information about out-of-date software.