streamline next steps 4

Author: Ankita Dutta

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

@@ -86,6 +86,7 @@ If you have enabled Accelerated Networking on the source virtual machine after e
 The above process should also be followed for existing replicated virtual machines that didn't previously have Accelerated Networking enabled automatically by Site Recovery.
 
 ## Next steps
+
 - Learn more about [benefits of Accelerated Networking](../virtual-network/accelerated-networking-overview.md#benefits).
 - Learn more about limitations and constraints of Accelerated Networking for [Windows virtual machines](../virtual-network/accelerated-networking-overview.md#limitations-and-constraints) and [Linux virtual machines](../virtual-network/accelerated-networking-overview.md#limitations-and-constraints).
 - Learn more about [recovery plans](site-recovery-create-recovery-plans.md) to automate application failover.

articles/site-recovery/concepts-azure-to-azure-high-churn-support.md

@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 07/14/2023
+ms.date: 03/29/2024
 ms.author: ankitadutta
 ---
 
@@ -109,4 +109,8 @@ The following table summarizes Site Recovery limits:
 ## Cost Implications  
 
 - **High Churn** uses *Premium Block Blob* storage accounts which may have higher cost implications as compared to **Normal Churn** which uses *Standard* storage accounts. For more information, see [pricing](https://azure.microsoft.com/pricing/details/storage/blobs/).
-- For High churn VMs, more data changes may get replicated to target for **High churn** compared to **Normal churn**. This may lead to more network cost.
+- For High churn VMs, more data changes may get replicated to target for **High churn** compared to **Normal churn**. This may lead to more network cost.
+
+## Next steps
+
+[Set up disaster recovery for Azure VMs](azure-to-azure-tutorial-enable-replication.md).

articles/site-recovery/concepts-expressroute-with-site-recovery.md

@@ -56,6 +56,7 @@ If you are already using ExpressRoute to connect from your on-premises datacente
 You can replicate Azure virtual machines to any Azure region within the same geographic cluster as detailed [here](../site-recovery/azure-to-azure-support-matrix.md#region-support). If the chosen target Azure region is not within the same geopolitical region as the source, you might need to enable ExpressRoute Premium. For more details, check [ExpressRoute locations](../expressroute/expressroute-locations.md) and [ExpressRoute pricing](https://azure.microsoft.com/pricing/details/expressroute/).
 
 ## Next steps
+
 - Learn more about [ExpressRoute circuits](../expressroute/expressroute-circuit-peerings.md).
 - Learn more about [ExpressRoute routing domains](../expressroute/expressroute-circuit-peerings.md#peeringcompare).
 - Learn more about [ExpressRoute locations](../expressroute/expressroute-locations.md).

articles/site-recovery/concepts-network-security-group-with-site-recovery.md

@@ -67,6 +67,7 @@ Considering the [example scenario](concepts-network-security-group-with-site-rec
 Once the NSGs are created and configured, we recommend running a [test failover](azure-to-azure-tutorial-dr-drill.md) to verify scripted NSG associations and post-failover VM connectivity.
 
 ## Next steps
+
 -    Learn more about [Network Security Groups](../virtual-network/network-security-groups-overview.md#network-security-groups).
 -    Learn more about NSG [security rules](../virtual-network/network-security-groups-overview.md#security-rules).
 -    Learn more about [effective security rules](../virtual-network/diagnose-network-traffic-filter-problem.md) for an NSG.

articles/site-recovery/concepts-on-premises-to-azure-networking.md

@@ -161,4 +161,5 @@ In this scenario, the Azure VM gets a new IP address after failover. To setup a
 Site Recovery will now honor these settings and ensure that the virtual machine on failover is connected to the selected resource via the corresponding IP Address, if it is available in the target IP range. In this scenario, there's no need to failover the entire subnet. A DNS update will be required to update records for failed over machine to point to the new IP address of the virtual machine.
 
 ## Next steps
+
 [Learn about](site-recovery-active-directory.md) replicating on-premises Active Directory and DNS to Azure.

articles/site-recovery/concepts-traffic-manager-with-site-recovery.md

@@ -111,6 +111,7 @@ You can additionally optimize the DNS Time to Live (TTL) value for the Traffic M
 The TTL experienced by the client also does not increase if the number of DNS resolvers between the client and the authoritative DNS server increases. DNS resolvers ‘count down’ the TTL and only pass on a TTL value that reflects the elapsed time since the record was cached. This ensures that the DNS record gets refreshed at the client after the TTL, irrespective of the number of DNS Resolvers in the chain.
 
 ## Next steps
+
 - Learn more about Traffic Manager [routing methods](../traffic-manager/traffic-manager-routing-methods.md).
 - Learn more about [nested Traffic Manager profiles](../traffic-manager/traffic-manager-nested-profiles.md).
 - Learn more about [endpoint monitoring](../traffic-manager/traffic-manager-monitoring.md).

articles/site-recovery/delete-vault.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: how-to
-ms.date: 11/05/2019
+ms.date: 03/29/2024
 ms.author: ankitadutta 
 
 ---
@@ -69,4 +69,9 @@ $vault = Get-AzRecoveryServicesVault -Name "vaultname"
 Remove-AzRecoveryServicesVault -Vault $vault
 ```
 
-Learn more about [Get-AzRecoveryServicesVault](/powershell/module/az.recoveryservices/get-azrecoveryservicesvault), and [Remove-AzRecoveryServicesVault](/powershell/module/az.recoveryservices/remove-azrecoveryservicesvault).
+## Next steps
+
+Learn more about:
+
+-  [Get-AzRecoveryServicesVault](/powershell/module/az.recoveryservices/get-azrecoveryservicesvault)
+- [Remove-AzRecoveryServicesVault](/powershell/module/az.recoveryservices/remove-azrecoveryservicesvault).