Merge pull request #114020 from BethWilke/branch144

Branch144

Author: garycentric

articles/automation/automation-edit-textual-runbook.md

@@ -16,7 +16,7 @@ The textual editor in Azure Automation can be used to edit [PowerShell runbooks]
 
 The textual editor includes a feature to insert code for cmdlets, assets, and child runbooks into a runbook. Instead of typing in the code yourself, you can select from a list of available resources and the editor inserts the appropriate code into the runbook.
 
-Each runbook in Azure Automation has two versions, Draft and Published. You edit the Draft version of the runbook and then publish it so it can be executed. The Published version cannot be edited. For more information, see [Publishing a runbook](manage-runbooks.md#publishing-a-runbook).
+Each runbook in Azure Automation has two versions, Draft and Published. You edit the Draft version of the runbook and then publish it so it can be executed. The Published version cannot be edited. For more information, see [Publish a runbook](manage-runbooks.md#publish-a-runbook).
 
 This article provides detailed steps for performing different functions with this editor. These are not applicable to [graphical runbooks](automation-runbook-types.md#graphical-runbooks). To work with these runbooks, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
 
@@ -78,7 +78,7 @@ Export-AzAutomationRunbook -Name $runbookName -AutomationAccountName $automation
 
 ### Change the contents of a runbook using Windows PowerShell
 
-The following sample commands show how to replace the existing contents of a runbook with the contents of a script file. This is the same sample procedure as in [To import a runbook from a script file with Windows PowerShell](manage-runbooks.md#importing-a-runbook).
+The following sample commands show how to replace the existing contents of a runbook with the contents of a script file. 
 
 ```powershell-interactive
 $resourceGroupName = "MyResourceGroup"

articles/automation/automation-hrw-run-runbooks.md

@@ -246,7 +246,7 @@ $SigningCert = ( Get-ChildItem -Path cert:\LocalMachine\My\<CertificateThumbprin
 Set-AuthenticodeSignature .\TestRunbook.ps1 -Certificate $SigningCert
 ```
 
-When a runbook has been signed, you must import it into your Automation account and publish it with the signature block. To learn how to import runbooks, see [Importing a runbook from a file into Azure Automation](manage-runbooks.md#importing-a-runbook).
+When a runbook has been signed, you must import it into your Automation account and publish it with the signature block. To learn how to import runbooks, see [Import a runbook](manage-runbooks.md#import-a-runbook).
 
 ## Work with signed runbooks on a Linux Hybrid Runbook Worker
 

articles/automation/automation-runbook-execution.md

@@ -152,7 +152,7 @@ it for different scenarios.
 
 7. Select **Publish** to save and publish the runbook.
 
-To verify that the runbook executes successfully you can follow the steps under [Test a runbook](manage-runbooks.md#testing-a-runbook) or [Start a runbook](start-runbooks.md).
+To verify that the runbook executes successfully you can follow the steps under [Test a runbook](manage-runbooks.md#test-a-runbook) or [Start a runbook](start-runbooks.md).
 If you do not initially see your test email, check your **Junk** and **Spam** folders.
 
 ## Clean Up

articles/automation/automation-send-email.md

@@ -9,7 +9,7 @@ ms.topic: conceptual
 
 # Update Azure PowerShell modules in Azure Automation
 
-To update the Azure modules in your Automation account you need to use the [Update Azure modules runbook](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update), which is available as open source. To start using the **Update-AutomationAzureModulesForAccount** runbook to update your Azure modules, download it from the [Update Azure modules runbook repository](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) on GitHub. You can then import it into your Automation account or run it as a script. To learn how to import a runbook in your Automation account, see [Import a runbook](manage-runbooks.md#importing-a-runbook).
+To update the Azure modules in your Automation account you need to use the [Update Azure modules runbook](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update), which is available as open source. To start using the **Update-AutomationAzureModulesForAccount** runbook to update your Azure modules, download it from the [Update Azure modules runbook repository](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) on GitHub. You can then import it into your Automation account or run it as a script. To learn how to import a runbook in your Automation account, see [Import a runbook](manage-runbooks.md#import-a-runbook).
 
 The most common PowerShell modules are provided by default in each Automation account. The Azure team updates the Azure modules regularly. Therefore, to keep the modules in your Automation accounts up to date, you should use the [Update-AutomationAzureModulesForAccount](https://github.com/Microsoft/AzureAutomation-Account-Modules-Update) runbook.
 

articles/automation/automation-update-azure-modules.md

@@ -22,6 +22,9 @@ You can enable Update Management for virtual machines (VMs) using the following
 
 An [Azure Resource Manager template](automation-update-management-deploy-template.md) is available to help you deploy Update Management to a new or existing Automation account and Log Analytics workspace in your subscription.
 
+> [!NOTE]
+> You can't use a machine configured with Update Management to run custom scripts from Azure Automation. This machine can only run the Microsoft-signed update script. 
+
 ## Update Management overview
 
 Machines that are managed by Update Management use the following configurations to perform assessment and to update deployments: