Merge pull request #266640 from ankitaduttaMSFT/nextsteps

streamline next steps

Author: prmerger-automator[bot]

articles/site-recovery/avs-tutorial-dr-drill-azure.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC
 
@@ -72,7 +72,7 @@ When you run a test failover, the following actions happen:
 2. Failover processes the data, so that an Azure VM can be created. If you select the latest recovery point, a recovery point is created from the data.
 3. An Azure VM is created from the data processed in the previous step.
 
-Run the test failover as follows:
+**Run the test failover as follows:**
 
 1. In **Settings** > **Replicated Items**, select the VM, and then select **+Test Failover**.
 2. Select the **Latest processed** recovery point for this tutorial. This step fails over the VM to the latest available point in time. The time stamp is shown.
@@ -99,5 +99,4 @@ If you want to connect to Azure VMs by using Remote Desktop Protocol (RDP) or Se
 
 ## Next step
 
-> [!div class="nextstepaction"]
-> [Learn more about running a failover](avs-tutorial-failover.md)
+- [Learn more about running a failover](avs-tutorial-failover.md).

articles/site-recovery/avs-tutorial-failover.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 ---
@@ -97,8 +97,7 @@ If you encounter any connectivity problems after failover, follow the [troublesh
 
 After failover, reprotect the Azure VMs to the Azure VMware Solution private cloud. Then, after the VMs are reprotected and replicating to the Azure VMware Solution private cloud, fail back from Azure when you're ready.
 
-> [!div class="nextstepaction"]
-> [Reprotect Azure VMs](avs-tutorial-reprotect.md)
 
-> [!div class="nextstepaction"]
-> [Fail back from Azure](avs-tutorial-failback.md)
+- Learn how to [reprotect Azure VMs](avs-tutorial-reprotect.md).
+- Learn how to [fail back from Azure](avs-tutorial-failback.md).
+

articles/site-recovery/avs-tutorial-prepare-avs.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 ---
@@ -74,10 +74,12 @@ Make sure that the VMware vCenter server and VMs comply with requirements:
 * Verify that the Azure VMware Solution VMs that you'll replicate to Azure comply with [Azure VM requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements).
 * For Linux VMs, ensure that no two devices or mount points have the same names. These names must be unique and aren't case-sensitive. For example, you can't name two devices for the same VM as *device1* and *Device1*.
 
+
 ## Prepare to connect to Azure VMs after failover
 
 After failover, you might want to connect to the Azure VMs from your Azure VMware Solution network.
 
+
 ### Connect to a Windows VM by using RDP
 
 Before failover, enable Remote Desktop Protocol (RDP) on the Azure VMware Solution VM:
@@ -93,6 +95,7 @@ There should be no Windows updates pending on the VM when you trigger a failover
 
 After failover, check **Boot diagnostics** to view a screenshot of the VM. If you can't connect, check that the VM is running and review [troubleshooting tips](https://social.technet.microsoft.com/wiki/contents/articles/31666.troubleshooting-remote-desktop-connection-after-failover-using-asr.aspx).
 
+
 ### Connect to Linux VMs by using SSH
 
 On the Azure VMware Solution VM before failover:
@@ -104,16 +107,14 @@ After failover, allow incoming connections to the SSH port for the network secur
 
 You can check **Boot diagnostics** to view a screenshot of the VM.
 
+
 ## Failback requirements
 
 If you plan to fail back to your Azure VMware Solution cloud, there are several [prerequisites for failback](avs-tutorial-reprotect.md#before-you-begin). You can prepare these now, but you don't need to. You can prepare after you fail over to Azure.
 
-## Next steps
 
-> [!div class="nextstepaction"]
-> [Set up disaster recovery](avs-tutorial-replication.md)
+## Next steps
 
-If you're replicating multiple VMs:
+- Learn how to [set up disaster recovery](avs-tutorial-replication.md).
+- If you're replicating multiple VMs, perform [capacity planning](site-recovery-deployment-planner.md).
 
-> [!div class="nextstepaction"]
-> [Perform capacity planning](site-recovery-deployment-planner.md)

articles/site-recovery/avs-tutorial-prepare-azure.md

@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 
@@ -108,11 +108,6 @@ The virtual network takes a few seconds to create. After it's created, it appear
 
 Learn more about:
 
-> [!div class="nextstepaction"]
-> [Preparing your infrastructure](avs-tutorial-prepare-avs.md)
-
-> [!div class="nextstepaction"]
-> [Azure networks](../virtual-network/virtual-networks-overview.md)
-
-> [!div class="nextstepaction"]
-> [Managed disks](../virtual-machines/managed-disks-overview.md)
+- [Preparing your infrastructure](avs-tutorial-prepare-avs.md)
+- [Azure networks](../virtual-network/virtual-networks-overview.md)
+- [Managed disks](../virtual-machines/managed-disks-overview.md).