Merge pull request #114580 from DCtheGeek/dmc-buildreport-20200508

Correct Build Report errors

Author: PRMerger14

articles/automation/automation-dsc-remediate.md

@@ -42,7 +42,7 @@ Similar functionality isn't currently available for Linux servers.
 The only option is to repeat the registration process.
 For Azure nodes, you can correct drift from the Azure portal
 or using Az module cmdlets. Details about this process are documented in 
-[Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md#onboard-a-vm-using-azure-portal).
+[Onboarding machines for management by Azure Automation State Configuration](automation-dsc-onboarding.md#enable-a-vm-using-azure-portal).
 For hybrid nodes, you can correct drift using the included Python scripts.
 See [PowerShell DSC for Linux repo](https://github.com/Microsoft/PowerShell-DSC-for-Linux#performing-dsc-operations-from-the-linux-computer).
 

articles/automation/compose-configurationwithcompositeresources.md

@@ -32,9 +32,9 @@ page while on either the **Configurations** or the **Compiled configurations** t
 
 Once the new configuration is saved, it is submitted for compilation. Status of the
 compilation job can be viewed like any imported configuration. For more information, see [Viewing a
-compilation job](automation-dsc-getting-started.md#viewing-a-compilation-job).
+compilation job](automation-dsc-getting-started.md#view-a-compilation-job).
 
-When compilation has completed successfully, the new configuration appears in the **Compiled configurations** tab. Then you can assign the configuration to a managed node, using the steps in [Reassigning a node to a different node configuration](automation-dsc-getting-started.md#reassigning-a-node-to-a-different-node-configuration).
+When compilation has completed successfully, the new configuration appears in the **Compiled configurations** tab. Then you can assign the configuration to a managed node, using the steps in [Reassigning a node to a different node configuration](automation-dsc-getting-started.md#reassign-a-node-to-a-different-node-configuration).
 
 ## Next steps
 

articles/azure-monitor/platform/agent-windows.md

@@ -172,8 +172,8 @@ Configuration MMAgent
 ```
 
 4. Update the `ProductId` value in the script with the product code extracted from the latest version of the agent install package using the methods recommended earlier. 
-5. [Import the MMAgent.ps1 configuration script](../../automation/automation-dsc-getting-started.md#importing-a-configuration-into-azure-automation) into your Automation account. 
-5. [Assign a Windows computer or node](../../automation/automation-dsc-getting-started.md#onboarding-an-azure-vm-for-management-with-azure-automation-state-configuration) to the configuration. Within 15 minutes, the node checks its configuration and the agent is pushed to the node.
+5. [Import the MMAgent.ps1 configuration script](../../automation/automation-dsc-getting-started.md#import-a-configuration-into-azure-automation) into your Automation account. 
+6. [Assign a Windows computer or node](../../automation/automation-dsc-getting-started.md#enable-an-azure-resource-manager-vm-for-management-with-state-configuration) to the configuration. Within 15 minutes, the node checks its configuration and the agent is pushed to the node.
 
 ## Verify agent connectivity to Log Analytics