incub 3

Author: Ankita Dutta

articles/site-recovery/migrate-overview.md

@@ -12,7 +12,7 @@ ms.custom: engagement-fy23
 
 # Migrating to Azure
 
-For migration, we recommend that you use the Azure Migrate service to migrate your VMs and servers to Azure, instead of using Azure Site Recovery service. Learn about [Azure Migrate](../migrate/migrate-services-overview.md).
+For migration, we recommend that you use the Azure Migrate service to migrate your virtual machines and servers to Azure, instead of using Azure Site Recovery service. Learn about [Azure Migrate](../migrate/migrate-services-overview.md).
 
 ## Why use Azure Migrate?
 
@@ -38,7 +38,7 @@ Site Recovery should be used:
 
 We recommend using Azure Migrate to migrate on-premises servers to Azure.  However, if you've already started your migration journey with Site Recovery, consider the following details:
 
-- If you're already using Azure Site Recovery to replicate your servers, you don't need to deploy a Migrate appliance. Remove the BCDR protection, and replicate with a new appliance.
+- If you're already using Azure Site Recovery to replicate your servers, you don't need to deploy a Migrate appliance. Remove the Business Continuity Disaster Recovery protection, and replicate with a new appliance.
 - However, there are benefits to conducting assessment, dependency analysis, and business case review with the Azure Migrate discovery appliance even for workloads that are already replicating.
 - There could be architecture changes required to support the workload in the long term. In this case, address the requirements while continuing to use Azure Site Recovery to replicate so that you don't lose protections.
 

articles/site-recovery/monitoring-common-questions.md

@@ -18,7 +18,7 @@ This article answers common questions about monitoring Azure [Site Recovery](sit
 Site Recovery uses a multi-step, asynchronous process to replicate machines to Azure.
 
 - In the penultimate step of replication, recent changes on the machine, along with metadata, are copied into a log/cache storage account.
-- These changes, along with the tag that identifies a recoverable point, are written to the storage account/managed disk in the target region.
+- These changes, along with the tag that identifies a recoverable point, is written to the storage account/managed disk in the target region.
 - Site Recovery can now generate a recoverable point for the machine.
 - At this point, the RPO has been met for the changes uploaded to the storage account so far. In other words, the machine RPO at this point is equal to amount of time that's elapsed from the timestamp corresponding to the recoverable point.
 - Now, Site Recovery picks the uploaded data from the storage account, and applies it to the replica disks created for the machine.
@@ -33,7 +33,7 @@ An incorrect system time on the replicating source machine, or on on-premises in
 ## Inbuilt Site Recovery logging
 
 
-### Why is the VM count in the vault infrastructure view different from the total count shown in Replicated Items?
+### Why is the virtual machine count in the vault infrastructure view different from the total count shown in Replicated Items?
 
 The vault infrastructure view is scoped by replication scenarios. Only machines in the currently selected replication scenario are included in the count for the view. In addition, we only count VMs that are configured to replicate to Azure. Failed over machines, or machines replicating back to an on-premises site, aren't counted in the view.
 
@@ -50,7 +50,7 @@ Only machines for which initial replication has completed are included in the co
 - AzureSiteRecoveryReplicationDataUploadRate and AzureSiteRecoveryProtectedDiskDataChurn are sent every five minutes. 
 - AzureSiteRecoveryJobs is sent at the trigger and completion of a job.
 - AzureSiteRecoveryEvents is sent whenever an event is generated. 
-- AzureSiteRecoveryReplicatedItems is sent whenever there is any environment change. Typically, the data refresh time is 15 minutes after a change. 
+- AzureSiteRecoveryReplicatedItems is sent whenever there's any environment change. Typically, the data refresh time is 15 minutes after a change. 
 
 ### How long is data kept in Azure Monitor logs? 
 
@@ -66,16 +66,16 @@ Typically the size of a log is 15-20 KB.
 
 ### Is there any cost for using built-in Azure Monitor alerts for Azure Site Recovery? 
 
-With built-in Azure Monitor alerts, alerts for critical operations/failures generate by default (that you can view in the portal or via non-portal interfaces) at no additional cost. However, to route these alerts to a notification channel (such as email), it incurs a minor cost for notifications beyond the free tier (of 1000 emails per month). [Learn more about Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
+With built-in Azure Monitor alerts, alerts for critical operations/failures generate by default (that you can view in the portal or via nonportal interfaces) at no extra cost. However, to route these alerts to a notification channel (such as email), it incurs a minor cost for notifications beyond the free tier (of 1,000 emails per month). [Learn more about Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
 
 ### Will the current email notification solution for Azure Site Recovery in Recovery Services vault continue to work? 
 
-As of today, the current email notification solution co-exists in parallel with the new built-in Azure Monitor alerts solution. we recommend you to try out the Azure Monitor based alerting to familiarize yourself with the new experience and leverage its capabilities.
+As of today, the current email notification solution coexists in parallel with the new built-in Azure Monitor alerts solution. We recommend you to try out the Azure Monitor based alerting to familiarize yourself with the new experience and use its capabilities.
 
 ### What is the difference between alert rule, alert processing rule and action group?
 
 - Alert rule: Refers to a user-created rule that specifies the condition on which an alert should be fired.
-- Alert processing rule (earlier called Action rule): Refers to a user-created rule that specifies the notification channels a particular fired alert should be routed to. You can also use alert processing rules to suppress notifications for a period of time. 
+- Alert processing rule (earlier called Action rule): Refers to a user-created rule that specifies the notification channels a particular fired alert should be routed to. You can also use alert processing rules to suppress notifications for time. 
 - Action group: Refers to the notification channel (such as email, ITSM endpoint, logic app, webhook, and so on) that a fired alert can be routed to.
 
 In the case of built-in Azure Monitor alerts, as alerts already generate by default, you don't need to create an alert rule. To route these alerts to a notification channel, you should create an alert processing rule and an action group for these alerts. [Learn more](site-recovery-monitor-and-troubleshoot.md#configure-email-notifications-for-alerts)