Fixing links

Author: BethWilke

articles/automation/automation-solution-vm-management.md

@@ -193,11 +193,11 @@ Selecting the solution displays the **Start-Stop-VM[workspace]** solution page.
 
 You can perform further analysis of the job records by clicking the donut tile. The solution dashboard shows job history and predefined log search queries. Switch to the log analytics advanced portal to search based on your search queries.
 
-## Update the solution
+## Update the feature
 
-If you've deployed a previous version of this solution, delete it from your account before deploying an updated release. Follow the steps to [remove the solution](#remove-the-solution) and then follow the steps to [deploy the solution](automation-solution-vm-management-enable.md).
+If you've deployed a previous version of this solution, delete it from your account before deploying an updated release. Follow the steps to [remove the solution](#remove-the-feature) and then follow the steps to [deploy the solution](automation-solution-vm-management-enable.md).
 
-## Remove the solution
+## Remove the feature
 
 If you no longer need to use the solution, you can delete it from the Automation account. Deleting the solution only removes the runbooks. It does not delete the schedules or variables that were created when the solution was added. Remove these assets manually if you aren't using them with other runbooks.
 

articles/automation/shared-resources/modules.md

@@ -32,7 +32,7 @@ When Automation executes runbook and DSC compilation jobs, it loads the modules
 
 The following table lists modules that Azure Automation imports by default when you create your Automation account. Automation can import newer versions of these modules. However, you can't remove the original version from your Automation account, even if you delete a newer version. Note that these default modules include several AzureRM modules. 
 
-Automation doesn't import the root Az module automatically into any new or existing Automation accounts. For more about working with these modules, see [Migrating to Az modules](#migrating-to-az-modules).
+Automation doesn't import the root Az module automatically into any new or existing Automation accounts. For more about working with these modules, see [Migrating to Az modules](#migrate-to-az-modules).
 
 > [!NOTE]
 > We don't recommend altering modules and runbooks in Automation accounts used for deployment of the [Start/Stop VMs during off-hours](../automation-solution-vm-management.md) feature.