Merge pull request #106467 from MGoedtel/task1665806d

updated UM tutorial article

Author: v-shils

articles/automation/automation-tutorial-update-management.md

@@ -4,7 +4,7 @@ description: This article provides an overview of how to use Azure Automation Up
 services: automation
 ms.subservice: update-management
 ms.topic: tutorial
-ms.date: 01/21/2020
+ms.date: 03/04/2020
 ms.custom: mvc
 ---
 # Manage updates and patches for your Azure VMs
@@ -38,9 +38,9 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 First, enable Update Management on your VM for this tutorial:
 
-1. In the [Azure portal](https://portal.azure.com) menu, select **Virtual machines** or search for and select **Virtual machines** from the **Home** page.
-1. Select the VM for which you want to enable Update Management.
-1. On the VM page, under **OPERATIONS**, select **Update management**. The **Enable Update Management** pane opens.
+1. In the [Azure portal](https://portal.azure.com), from the left-hand pane select **Virtual machines** or search for and select **Virtual machines** from the **Home** page.
+2. Select the VM for which you want to enable Update Management.
+3. On the VM page, under **Operations**, select **Update management**. The **Enable Update management** pane opens.
 
 Validation is performed to determine whether Update Management is enabled for this VM. This validation includes checks for a Log Analytics workspace and linked Automation account, and whether the Update Management solution is enabled in the workspace.
 
@@ -52,23 +52,23 @@ If any of the following prerequisites were found to be missing during onboarding
 
 * [Log Analytics](../azure-monitor/platform/data-platform-logs.md) workspace
 * An [Automation account](./automation-offering-get-started.md)
-* A [Hybrid Runbook Worker](./automation-hybrid-runbook-worker.md) (enabled on the VM)
+* A [Hybrid Runbook Worker](./automation-hybrid-runbook-worker.md) enabled on the VM
 
-Under **Update Management**, set the location, Log Analytics workspace, and Automation account to use. Then, select **Enable**. If these options aren't available, it means that another automation solution is enabled for the VM. In that case, the same workspace and Automation account must be used.
+Under **Update management**, set the location, Log Analytics workspace, and Automation account to use. Then, select **Enable**. If these options aren't available, it means that another Automation solution is enabled for the VM. In that case, the same workspace and Automation account must be used.
 
 ![Enable the Update Management solution window](./media/automation-tutorial-update-management/manageupdates-update-enable.png)
 
-Enabling the solution can take up to a few minutes. During this time, don't close the browser window. After the solution is enabled, information about missing updates on the VM flows to Azure Monitor logs. It can take between 30 minutes and 6 hours for the data to be available for analysis.
+Enabling the solution can take several minutes. During this time, don't close the browser window. After the solution is enabled, information about missing updates on the VM flows to Azure Monitor logs. It can take between 30 minutes and 6 hours for the data to be available for analysis.
 
 ## View update assessment
 
 After Update Management is enabled, the **Update management** pane opens. If any updates are identified as missing, a list of missing updates is shown on the **Missing updates** tab.
 
-Under **INFORMATION LINK**, select the update link to open the support article for the update. You can learn important information about the update.
+Under **Information link**, select the update link to open the support article for the update. You can learn important information about the update.
 
 ![View update status](./media/automation-tutorial-update-management/manageupdates-view-status-win.png)
 
-Click anywhere else on the update to open the **Log Search** pane for the selected update. The query for the log search is predefined for that specific update. You can modify this query or create your own query to view detailed information about the updates that are deployed or missing in your environment.
+Click anywhere else on the update to open the **Log search** pane for the selected update. The query for the log search is predefined for that specific update. You can modify this query or create your own query to view detailed information about the updates that are deployed or missing in your environment.
 
 ![View update status](./media/automation-tutorial-update-management/logsearch.png)
 
@@ -105,15 +105,15 @@ Under **Action groups**, select **Create New**. An action group is a group of ac
 
 In the **Action group name** box, enter a name for the alert and a short name. The short name is used in place of a full action group name when notifications are sent by using this group.
 
-Under **Actions**, enter a name for the action, like **Email Notifications**. Under **ACTION TYPE**, select **Email/SMS/Push/Voice**. Under **DETAILS**, select **Edit details**.
+Under **Actions**, enter a name for the action, like **Email notifications**. Under **Action type**, select **Email/SMS/Push/Voice**. Under **Details**, select **Edit details**.
 
 In the **Email/SMS/Push/Voice** pane, enter a name. Select the **Email** check box, and then enter a valid email address.
 
 ![Configure an email action group](./media/automation-tutorial-update-management/configure-email-action-group.png)
 
-In the **Email/SMS/Push/Voice** pane, select **OK**. In the **Add action group** pane, select **OK**.
+In the **Email/SMS/Push/Voice** pane, select **Ok**. In the **Add action group** pane, select **Ok**.
 
-To customize the subject of the alert email,  under **Create rule**, under **Customize Actions**, select **Email subject**. When you're finished, select **Create alert rule**. The alert tells you when an update deployment succeeds, and which machines were part of that update deployment run.
+To customize the subject of the alert email,  under **Create rule**, under **Customize actions**, select **Email subject**. When you're finished, select **Create alert rule**. The alert tells you when an update deployment succeeds, and which machines were part of that update deployment run.
 
 ## Schedule an update deployment
 
@@ -133,7 +133,7 @@ Under **New update deployment**, specify the following information:
 
 * **Groups to update (preview)**: Define a query based on a combination of subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. To learn more, see [Dynamic Groups](automation-update-management-groups.md)
 
-* **Machines to update**: Select a Saved search, Imported group, or pick Machine from the drop-down and select individual machines. If you choose **Machines**, the readiness of the machine is shown in the **UPDATE AGENT READINESS** column. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
+* **Machines to update**: Select a Saved search, Imported group, or pick Machine from the drop-down and select individual machines. If you choose **Machines**, the readiness of the machine is shown in the **Update agent readiness** column. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
 
 * **Update classification**: Select the supported update classifications available for each product that can be included in the update deployment. For this tutorial, leave all types selected.
 
@@ -157,7 +157,7 @@ Under **New update deployment**, specify the following information:
 
 * **Schedule settings**: The **Schedule Settings** pane opens. The default start time is 30 minutes after the current time. You can set the start time to any time from 10 minutes in the future.
 
-   You can also specify whether the deployment occurs once, or set up a recurring schedule. Under **Recurrence**, select **Once**. Leave the default as 1 day and select **OK**. This sets up a recurring schedule.
+   You can also specify whether the deployment occurs once, or set up a recurring schedule. Under **Recurrence**, select **Once**. Leave the default as 1 day and select **Ok**. This sets up a recurring schedule.
 
 * **Pre-scripts + Post-scripts**: Select the scripts to run before and after your deployment. To learn more, see [Manage Pre and Post scripts](pre-post-scripts.md).