Fixing links

Author: BethWilke

articles/automation/automation-dsc-onboarding.md

@@ -62,7 +62,7 @@ To find the registration key and registration URL to use as parameters in the te
 You can enable 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 enable for State Configuration. In addition, WMF 5 must be installed on the computer that you are using for enabling the machines.
-1. Follow the directions in the section [Generating DSC metaconfigurations](#generating-dsc-metaconfigurations) to create a folder containing the required DSC metaconfigurations. 
+1. Follow the directions in [Generate DSC metaconfigurations](#generate-dsc-metaconfigurations) to create a folder containing the required DSC metaconfigurations. 
 1. Use the following cmdlet to apply the PowerShell DSC metaconfigurations remotely to the machines to enable. 
 
    ```powershell
@@ -87,7 +87,7 @@ You can enable Linux servers running on-premises or in other cloud environments
 
 3. If the PowerShell DSC Local Configuration Manager (LCM) defaults don't match your use case, or you want to enable machines that only report to Azure Automation State Configuration, follow steps 4-7. Otherwise, proceed directly to step 7.
 
-4. Follow the directions in the [Generating DSC metaconfigurations](#generating-dsc-metaconfigurations) section to produce a folder containing the required DSC metaconfigurations.
+4. Follow the directions in [Generate DSC metaconfigurations](#generate-dsc-metaconfigurations) section to produce a folder containing the required DSC metaconfigurations.
 
 5. Make sure that the latest version of [WMF 5](https://aka.ms/wmf5latest) is installed on the computer being used to enable your machines for State Configuration.
 

articles/automation/automation-dsc-overview.md

@@ -99,7 +99,7 @@ you also need to allow traffic between nodes. See the documentation for each DSC
 
 #### Proxy support
 
-Proxy support for the DSC agent is available in Windows version 1809 and later. This option is enabled by setting the values for `ProxyURL` and `ProxyCredential` in the [metaconfiguration script](automation-dsc-onboarding.md#generating-dsc-metaconfigurations)
+Proxy support for the DSC agent is available in Windows version 1809 and later. This option is enabled by setting the values for `ProxyURL` and `ProxyCredential` in the [metaconfiguration script](automation-dsc-onboarding.md#generate-dsc-metaconfigurations)
 used to register nodes.
 
 >[!NOTE]

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

@@ -10,13 +10,10 @@ ms.date: 04/16/2019
 ms.topic: conceptual
 manager: carmonm
 ---
-# Troubleshoot issues with Azure Automation State Configuration
+# Troubleshoot Azure Automation State Configuration issues
 
 This article provides information on troubleshooting issues that arise while you compile or deploy configurations in Azure Automation State Configuration.
 
->[!NOTE]
->This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version by following the steps in [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
-
 ## Diagnose an issue
 
 When you receive a compilation or deployment error for configuration, here are a few steps to help you diagnose the issue.
@@ -106,7 +103,7 @@ VM has reported a failure when processing extension 'Microsoft.Powershell.DSC /
 
 ### Cause
 
-This issue is caused by a bad or expired certificate. See [Certificate expiration and reregistration](../automation-dsc-onboarding.md#re-registering-a-node).
+This issue is caused by a bad or expired certificate. See [Re-register a node](../automation-dsc-onboarding.md#re-register-a-node).
 
 This issue might 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). 
 
@@ -234,11 +231,11 @@ You've used a credential in a configuration but didn't provide proper `Configura
 
 Make sure to pass in the proper `ConfigurationData` to set `PSDscAllowPlainTextPassword` to true for each node configuration that's mentioned in the configuration. See [Compiling DSC configurations in Azure Automation State Configuration](../automation-dsc-compile.md).
 
-## <a name="failure-processing-extension"></a>Scenario: "Failure processing extension" error when onboarding from a DSC extension
+## <a name="failure-processing-extension"></a>Scenario: "Failure processing extension" error when enabling a machine from a DSC extension
 
 ### Issue
 
-When you onboard by using a DSC extension, a failure occurs that contains the error:
+When you enable a machine by using a DSC extension, a failure occurs that contains the error:
 
 ```error
 VM has reported a failure when processing extension 'Microsoft.Powershell.DSC'. Error message: \"DSC COnfiguration 'RegistrationMetaConfigV2' completed with error(s). Following are the first few: Registration of the Dsc Agent with the server <url> failed. The underlying error is: The attempt to register Dsc Agent with Agent Id <ID> with the server <url> return unexpected response code BadRequest. .\".
@@ -251,7 +248,7 @@ This error typically occurs when the node is assigned a node configuration name
 ### Resolution
 
 * Make sure that you're assigning the node with a name that exactly matches the name in the service.
-* You can choose to not include the node configuration name, which results in onboarding the node but not assigning a node configuration.
+* You can choose to not include the node configuration name, which results in enabling the node but not assigning a node configuration.
 
 ## <a name="cross-subscription"></a>Scenario: "One or more errors occurred" error when registering a node by using PowerShell
 
@@ -269,10 +266,10 @@ This error occurs when you try to register a node in a separate subscription fro
 
 ### Resolution
 
-Treat the cross-subscription node as though it's defined for a separate cloud, or on-premises. Register the node by using one of these onboarding options:
+Treat the cross-subscription node as though it's defined for a separate cloud, or on-premises. Register the node by using one of these options for enabling machines:
 
-* 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).
+* Windows: [Physical/virtual Windows machines on-premises, or in a cloud other than Azure/AWS](../automation-dsc-onboarding.md#enable-physicalvirtual-windows-machines).
+* Linux: [Physical/virtual Linux machines on-premises, or in a cloud other than Azure](../automation-dsc-onboarding.md#enable-physicalvirtual-linux-machines).
 
 ## <a name="agent-has-a-problem"></a>Scenario: "Provisioning has failed" error message