Fixing links

Author: BethWilke

articles/automation/automation-dsc-onboarding.md

@@ -81,9 +81,9 @@ The best way to register VMs from other Azure subscriptions is to use the DSC ex
 
 To find the registration key and registration URL to use as parameters in the template, see the [Onboarding securely using registration](#onboarding-securely-using-registration) section in this article.
 
-## Onboarding physical/virtual Windows machines on-premises, or in a cloud other than Azure (including AWS EC2 instances)
+## Onboarding physical/virtual Windows machines
 
-You can onboard Windows servers running on-premises or in other cloud environments to Azure Automation State Configuration. The servers must have [outbound access to Azure](automation-dsc-overview.md#network-planning).
+You can onboard Windows servers running on-premises or in other cloud environments (including AWS EC2 instances) to Azure Automation State Configuration. The servers must have [outbound access to Azure](automation-dsc-overview.md#network-planning).
 
 1. Make sure that the latest version of [WMF 5](https://aka.ms/wmf5latest) is installed on the machines to onboard to Azure Automation State Configuration. In addition, WMF 5 must be installed on the computer that you are using for the onboarding operation.
 1. Follow the directions in the section [Generating DSC metaconfigurations](#generating-dsc-metaconfigurations) to create a folder containing the required DSC metaconfigurations. 
@@ -96,7 +96,7 @@ You can onboard Windows servers running on-premises or in other cloud environmen
 1. If you can't apply the PowerShell DSC metaconfigurations remotely, copy the **metaconfigurations** folder to the machines that you are onboarding. Then add code to call [Set-DscLocalConfigurationManager](https://docs.microsoft.com/powershell/module/psdesiredstateconfiguration/set-dsclocalconfigurationmanager?view=powershell-5.1) locally on the machines.
 1. Using the Azure portal or cmdlets, verify that the machines to onboard appear as State Configuration nodes registered in your Azure Automation account.
 
-## Onboarding physical/virtual Linux machines on-premises, or in a cloud other than Azure
+## Onboarding physical/virtual Linux machines
 
 You can onboard Linux servers running on-premises or in other cloud environments to Azure Automation State Configuration. The servers must have [outbound access to Azure](automation-dsc-overview.md#network-planning).
 

articles/automation/automation-onboard-solutions.md

@@ -73,7 +73,7 @@ Now that the solutions are enabled, you can add an Azure VM to onboard to those
 
 ## Install and update modules
 
-It's required to update to the latest Azure modules and import the [Az.OperationalInsights](https://docs.microsoft.com/en-us/powershell/module/az.operationalinsights/?view=azps-3.7.0) module to successfully automate solution onboarding.
+It's required to update to the latest Azure modules and import the [Az.OperationalInsights](https://docs.microsoft.com/powershell/module/az.operationalinsights/?view=azps-3.7.0) module to successfully automate solution onboarding.
 
 ## Update Azure Modules
 

articles/automation/troubleshoot/desired-state-configuration.md

@@ -107,7 +107,7 @@ VM has reported a failure when processing extension 'Microsoft.Powershell.DSC /
 
 ### Cause
 
-This issue is caused by a bad or expired certificate.  For more information, see [Certificate expiration and reregistration](../automation-dsc-onboarding.md#re-register-a-node).
+This issue is caused by a bad or expired certificate.  For more information, see [Certificate expiration and reregistration](../automation-dsc-onboarding.md#re-registering-a-node).
 
 This issue could also be caused by a proxy configuration not allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning). 
 
@@ -273,8 +273,8 @@ Treat the cross-subscription node as though it lives in a separate cloud, or on-
 
 Follow the steps below to register the node.
 
-* Windows - [Physical/virtual Windows machines on-premises, or in a cloud other than Azure/AWS](../automation-dsc-onboarding.md#onboard-physicalvirtual-windows-machines-on-premises-or-in-a-cloud-other-than-azure).
-* Linux - [Physical/virtual Linux machines on-premises, or in a cloud other than Azure](../automation-dsc-onboarding.md#onboard-physicalvirtual-linux-machines-on-premises-or-in-a-cloud-other-than-azure).
+* Windows - [Physical/virtual Windows machines on-premises, or in a cloud other than Azure/AWS](../automation-dsc-onboarding.md#onboarding-physicalvirtual-windows-machines).
+* Linux - [Physical/virtual Linux machines on-premises, or in a cloud other than Azure](../automation-dsc-onboarding.md#onboarding-physicalvirtual-linux-machines).
 
 ### <a name="agent-has-a-problem"></a>Scenario: Error message - "Provisioning Failed"
 

articles/virtual-machines/extensions/dsc-overview.md

@@ -70,8 +70,7 @@ three values will need to be provided.
 - RegistrationKey - a shared secret used to register nodes with the service
 - NodeConfigurationName - the name of the Node Configuration (MOF) to pull from the service to configure the server role
 
-This information can be seen in the
-[Azure portal](../../automation/automation-dsc-onboarding.md#onboard-vms-by-using-the-azure-portal) or you can use PowerShell.
+This information can be seen in the Azure portal or you can use PowerShell.
 
 ```powershell
 (Get-AzAutomationRegistrationInfo -ResourceGroupName <resourcegroupname> -AutomationAccountName <accountname>).Endpoint