validation

Author: Ja-Dunn

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

@@ -45,7 +45,7 @@ For information on using **xDscDiagnostics**, see [Using xDscDiagnostics to anal
 
 ### 3. Ensure that nodes and the Automation workspace have required modules
 
-DSC depends on modules installed on the node. When you use Azure Automation State Configuration, import any required modules into your Automation account by following the steps in [Import Modules](../shared-resources/modules.md#importing-modules). Configurations can also have a dependency on specific versions of modules. For more information, see [Troubleshoot modules](shared-resources.md#modules).
+DSC depends on modules installed on the node. When you use Azure Automation State Configuration, import any required modules into your Automation account by following the steps in [Import Modules](../shared-resources/modules.md#import-modules). Configurations can also have a dependency on specific versions of modules. For more information, see [Troubleshoot modules](shared-resources.md#modules).
 
 ## <a name="unsupported-characters"></a>Scenario: A configuration with special characters can't be deleted from the portal
 

articles/automation/troubleshoot/runbooks.md

@@ -35,7 +35,7 @@ When you receive errors during runbook execution in Azure Automation, you can us
 
 3. **Ensure that your nodes and Automation workspace have the required modules.** 
 
-    If your runbook imports any modules, verify that they are available to your Automation account using the steps in [Import modules](../shared-resources/modules.md#importing-modules). Update your PowerShell modules to the latest version by following the instructions at [Update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md). For more troubleshooting information, see [Troubleshoot modules](shared-resources.md#modules).
+    If your runbook imports any modules, verify that they are available to your Automation account using the steps in [Import modules](../shared-resources/modules.md#import-modules). Update your PowerShell modules to the latest version by following the instructions at [Update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md). For more troubleshooting information, see [Troubleshoot modules](shared-resources.md#modules).
 
 4. **Do if your runbook is suspended or unexpectedly fails.**
 
@@ -623,7 +623,7 @@ This error is probably caused by using an incomplete migration from AzureRM to A
 
 ### Resolution
 
-We don't recommend the use of Az and AzureRM cmdlets in the same runbook. To learn more about the correct use of these modules, see [Migrating to Az modules](../shared-resources/modules.md#migrating-to-az-modules).
+We don't recommend the use of Az and AzureRM cmdlets in the same runbook. To learn more about the correct use of these modules, see [Migrating to Az modules](../shared-resources/modules.md#migrate-to-az-modules).
 
 ## <a name="access-denied-azure-sandbox"></a>Scenario: Access denied when using Azure sandbox for runbook or application