edit pass: start-stop-vm-and-update-agent-issues-linux

Author: paulth1

articles/automation/troubleshoot/start-stop-vm.md

@@ -187,6 +187,7 @@ Follow these steps to ensure that the solution is configured correctly.
 1. Ensure all VMs to be started or stopped have a `sequencestart` or `sequencestop` tag, depending on your situation. These tags need a positive integer as the value. VMs are processed in ascending order based on this value.
 1. Make sure the resource groups for the VMs to be started or stopped are in the `External_Start_ResourceGroupNames` or `External_Stop_ResourceGroupNames` variables, depending on your situation.
 1. Test your changes by executing the `SequencedStartStop_Parent` runbook with the `WHATIF` parameter set to True to preview your changes.
+
 For more information about how to use the solution to start and stop VMs in sequence, see [Start/Stop VMs in sequence](../automation-solution-vm-management.md).
 
 ## <a name="403"></a>Scenario: Start/Stop VMs during off hours job fails with 403 forbidden error

articles/automation/troubleshoot/update-agent-issues-linux.md

@@ -15,7 +15,7 @@ manager: carmonm
 
 There can be many reasons your machine isn't showing up as ready (healthy) in the Azure Automation Update Management solution. In Update Management, you can check the health of a Hybrid Runbook Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter for Azure machines from the Azure portal and non-Azure machines in the [offline scenario](#troubleshoot-offline). 
 
-A machine can be in the following three readiness states:
+A machine can be in three readiness states:
 
 * **Ready**: The Hybrid Runbook Worker is deployed and was last seen less than one hour ago.
 * **Disconnected**: The Hybrid Runbook Worker is deployed and was last seen over one hour ago.