fixing validation errors

Author: paulth1

articles/site-recovery/site-recovery-plan-capacity-vmware.md

@@ -36,7 +36,7 @@ CPU | Memory | Cache disk size | Data change rate | Protected machines
 8 vCPUs (2 sockets * 4 cores \@ 2.5 GHz) | 16 GB | 300 GB | 500 GB or less | Use to replicate fewer than 100 machines.
 12 vCPUs (2 sockets * 6 cores \@ 2.5 GHz) | 18 GB | 600 GB | 501 GB to 1 TB | Use to replicate 100 to 150 machines.
 16 vCPUs (2 sockets * 8 cores \@ 2.5 GHz) | 32 GB | 1 TB | >1 TB to 2 TB | Use to replicate 151 to 200 machines.
-Deploy another configuration server by using an [OVF template](vmware-azure-deploy-configuration-server.md#deployment-of-configuration-server-through-ova-template). | | | | Deploy a new configuration server if you're replicating more than 200 machines.
+Deploy another configuration server by using an [OVF template](vmware-azure-deploy-configuration-server.md#deploy-a-configuration-server-through-an-ova-template). | | | | Deploy a new configuration server if you're replicating more than 200 machines.
 Deploy another [process server](vmware-azure-set-up-process-server-scale.md#download-installation-file). | | | >2 TB| Deploy a new scale-out process server if the overall daily data change rate is greater than 2 TB.
 
 In these configurations:
@@ -48,7 +48,7 @@ In these configurations:
 
 The process server is the component that handles data replication in Azure Site Recovery. If the daily change rate is greater than 2 TB, you must add scale-out process servers to handle the replication load. To scale out, you can:
 
-* Increase the number of configuration servers by deploying by using an [OVF template](vmware-azure-deploy-configuration-server.md#deployment-of-configuration-server-through-ova-template). For example, you can protect up to 400 machines by using two configuration servers.
+* Increase the number of configuration servers by deploying by using an [OVF template](vmware-azure-deploy-configuration-server.md#deploy-a-configuration-server-through-an-ova-template). For example, you can protect up to 400 machines by using two configuration servers.
 * Add [scale-out process servers](vmware-azure-set-up-process-server-scale.md#download-installation-file). Use the scale-out process servers to handle replication traffic instead of (or in addition to) the configuration server.
 
 The following table describes this scenario:

articles/site-recovery/vmware-azure-troubleshoot-configuration-server.md

@@ -120,7 +120,7 @@ If you install applications other than the configuration server on the virtual m
 
 The configuration server must be a single purpose server and using it as a shared server is unsupported. 
 
-For more information, see the configuration FAQ in [Deploy a configuration server](vmware-azure-deploy-configuration-server.md#faq). 
+For more information, see the configuration FAQ in [Deploy a configuration server](vmware-azure-deploy-configuration-server.md#faqs). 
 
 ## Remove the stale entries for protected items from the configuration server database 
 
@@ -183,7 +183,7 @@ To update the configuration server, run the [unified setup](service-updates-how-
 
 ## Azure Active Directory application creation failure
 
-You have insufficient permissions to create an application in Azure Active Directory (AAD) using the [Open Virtualization Application (OVA)](vmware-azure-deploy-configuration-server.md#deployment-of-configuration-server-through-ova-template
+You have insufficient permissions to create an application in Azure Active Directory (AAD) using the [Open Virtualization Application (OVA)](vmware-azure-deploy-configuration-server.md#deploy-a-configuration-server-through-an-ova-template
 ) template.
 
 To resolve the issue, sign in to the Azure portal and do one of the following:

articles/site-recovery/vmware-physical-azure-config-process-server-overview.md

@@ -22,7 +22,7 @@ For disaster recovery of on-premises VMware VMs and physical servers, you need a
 **Components**  | The configuration server machine runs all on-premises Site Recovery components, which include the configuration server, process server, and master target server.<br/><br/> When you set up the configuration server, all the components are installed automatically. | [Read](vmware-azure-common-questions.md#configuration-server) the configuration server FAQ.
 **Role** | The configuration server coordinates communications between on-premises and Azure, and manages data replication. | Learn more about the architecture for [VMware](vmware-azure-architecture.md) and [physical server](physical-azure-architecture.md) disaster recovery to Azure.
 **VMware requirements** | For disaster recovery of on-premises VMware VMs, you must install and run the configuration server as a on-premises, highly available VMware VM. | [Learn about](vmware-azure-deploy-configuration-server.md#prerequisites) the prerequisites.
-**VMware deployment** | We recommend that you deploy the configuration server using a downloaded OVA template. This method provides a simply way to set up a configuration server that complies with all requirements and prerequisites.<br/><br/> If for some reason you're unable to deploy a VMware VM using an OVA template, you can set up the configuration server machines manually, as described below for physical machine disaster recovery. | [Deploy](vmware-azure-deploy-configuration-server.md#deployment-of-configuration-server-through-ova-template) with an OVA template.
+**VMware deployment** | We recommend that you deploy the configuration server using a downloaded OVA template. This method provides a simply way to set up a configuration server that complies with all requirements and prerequisites.<br/><br/> If for some reason you're unable to deploy a VMware VM using an OVA template, you can set up the configuration server machines manually, as described below for physical machine disaster recovery. | [Deploy](vmware-azure-deploy-configuration-server.md#deploy-a-configuration-server-through-an-ova-template) with an OVA template.
 **Physical server requirements** | For disaster recovery on on-premises physical servers, you deploy the configuration server manually. | [Learn about](physical-azure-set-up-source.md#prerequisites) the prerequisites.
 **Physical server deployment** | If it can't be installed as a VMware VM, you can install it on a physical server. | [Deploy](physical-azure-set-up-source.md#set-up-the-source-environment) the configuration server manually.