Merge pull request #270342 from ankitaduttaMSFT/QS

doc bugs

Author: prmerger-automator[bot]

articles/site-recovery/site-recovery-overview.md

@@ -3,7 +3,7 @@ title: About Azure Site Recovery
 description: Provides an overview of the Azure Site Recovery service, and summarizes disaster recovery and migration deployment scenarios.
 ms.topic: overview
 ms.service: site-recovery
-ms.date: 02/07/2024
+ms.date: 03/27/2024
 ms.custom: MVC
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -39,7 +39,7 @@ Site Recovery can manage replication for:
 **Simple BCDR solution** | Using Site Recovery, you can set up and manage replication, failover, and failback from a single location in the Azure portal.
 **Azure VM replication** | You can set up disaster recovery of Azure VMs from a primary region to a secondary region or from Azure Public MEC to the Azure region or from one Azure Public MEC to another Azure Public MEC connected to the same Azure region.
 **VMware VM replication** | You can replicate VMware VMs to Azure using the improved Azure Site Recovery replication appliance that offers better security and resilience than the configuration server. For more information, see [Disaster recovery of VMware VMs](vmware-azure-about-disaster-recovery.md).
-**On-premises VM replication** | You can replicate on-premises VMs and physical servers to Azure, or to a secondary on-premises datacenter. Replication to Azure eliminates the cost and complexity of maintaining a secondary datacenter.
+**On-premises VM replication** | You can replicate on-premises VMs and physical servers to Azure. Replication to Azure eliminates the cost and complexity of maintaining a secondary datacenter.
 **Workload replication** | Replicate any workload running on supported Azure VMs, on-premises Hyper-V and VMware VMs, and Windows/Linux physical servers.
 **Data resilience** | Site Recovery orchestrates replication without intercepting application data. When you replicate to Azure, data is stored in Azure storage, with the resilience that provides. When failover occurs, Azure VMs are created based on the replicated data. This also applies to Public MEC to Azure region Azure Site Recovery scenario. In case of Azure Public MEC to Public MEC Azure Site Recovery scenario (the ASR functionality for Public MEC is in preview state), data is stored in the Public MEC.
 **RTO and RPO targets** | Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce RTO further by integrating with [Azure Traffic Manager](./concepts-traffic-manager-with-site-recovery.md).

articles/site-recovery/vmware-azure-tutorial-prepare-on-premises.md

@@ -3,7 +3,7 @@ title: Prepare for VMware VM disaster recovery with Azure Site Recovery
 description: Learn how to prepare on-premises VMware servers for disaster recovery to Azure using the Azure Site Recovery service.
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 11/12/2019
+ms.date: 03/27/2024
 ms.custom: MVC
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -117,6 +117,6 @@ If you plan to fail back to your on-premises site, there are a number of [prereq
 ## Next steps
 
 Set up disaster recovery. If you're replicating multiple VMs, plan capacity.
-> [!div class="nextstepaction"]
-> [Set up disaster recovery to Azure for VMware VMs](vmware-azure-tutorial.md)
-> [Perform capacity planning](site-recovery-deployment-planner.md).
+
+- [Set up disaster recovery to Azure for VMware VMs](vmware-azure-set-up-replication-tutorial-modernized.md)
+- [Perform capacity planning](site-recovery-deployment-planner.md).