removing blockers

Author: Ankita Dutta

articles/site-recovery/encryption-feature-deprecation.md

@@ -31,7 +31,7 @@ To continue successful failover operations, and replications follow the steps me
 
 Follow these steps for each VM: 
 1.	[Disable replication](./site-recovery-manage-registration-and-protection.md#disable-protection-for-a-hyper-v-virtual-machine-replicating-to-azure-using-the-system-center-vmm-to-azure-scenario).
-2.	[Create a new replication policy](./hyper-v-azure-tutorial.md#set-up-a-replication-policy).
+2.	[Create a new replication policy](./hyper-v-azure-tutorial.md#enable-replication).
 3.	[Enable replication](./hyper-v-vmm-azure-tutorial.md#enable-replication) and select a storage account with SSE enabled.
 
 After completing the initial replication to storage accounts with SSE enabled, your VMs will be using Encryption at Rest with Azure Site Recovery.

articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md

@@ -263,7 +263,7 @@ After you finish the preceding tasks, continue with the setup of your on-premise
 infrastructure. Continue by completing one of the following tasks: 
 
 - [Deploy a configuration server for VMware and physical machines](./vmware-azure-deploy-configuration-server.md)
-- [Set up the Hyper-V environment for replication](./hyper-v-azure-tutorial.md#set-up-the-source-environment)
+- [Set up the Hyper-V environment for replication](./hyper-v-azure-tutorial.md#source-settings)
 
 After the setup is complete, enable replication for your source machines. Don't set up
 the infrastructure until after the private endpoints for the vault are created in the

articles/site-recovery/upgrade-2012R2-to-2016.md

@@ -60,7 +60,7 @@ The list of steps mentioned below applies to the user configuration from [Hyper-
 1. Follow the steps to perform the [rolling cluster upgrade.](/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade#cluster-os-rolling-upgrade-process) to execute the rolling cluster upgrade process.
 2. With every new Windows Server 2016 host that is introduced in the cluster, remove the reference of a Windows Server 2012 R2 host from Azure Site Recovery by following steps mentioned [here]. This should be the host you chose to drain & evict from the cluster.
 3. Once the *Update-VMVersion* command has been executed for all virtual machines, the upgrades have been completed. 
-4. Use the steps mentioned [here](./hyper-v-azure-tutorial.md#set-up-the-source-environment) to register the new Windows Server 2016 host to Azure Site Recovery. Please note that the Hyper-V site is already active and you just need to register the new host in the cluster. 
+4. Use the steps mentioned [here](./hyper-v-azure-tutorial.md#source-settings) to register the new Windows Server 2016 host to Azure Site Recovery. Please note that the Hyper-V site is already active and you just need to register the new host in the cluster. 
 5. Go to the Azure portal and verify the replicated health status inside the Recovery Services
 
 ## Upgrade Windows Server 2012 R2 hosts managed by stand-alone SCVMM 2012 R2 server