fix typos

Author: genlin

support/azure/automation/runbooks/runbook-fails-on-hybrid-worker.md

@@ -25,11 +25,11 @@ Connectivity problems are a common cause of issues with Hybrid Runbook Workers.
 | Runbooks behave differently on a Hybrid Worker than in Azure Automation. | See [Runbook permissions](/azure/automation/automation-hrw-run-runbooks#runbook-permissions) for information on authentication differences. |
 | Error: No certificate was found. | Follow the [No Certificate Found](/azure/automation/troubleshoot/hybrid-runbook-worker#no-cert-found) section in the troubleshooting guide. |
 | You need to troubleshoot a custom runbook. | See [Troubleshoot runbook issues](/azure/automation/troubleshoot/runbooks). |
-| Need to check job status. | Review [job details and statuses](/azure/automation/automation-runbook-execution#job-statuses). |
+| You need to check job status. | Review [job details and statuses](/azure/automation/automation-runbook-execution#job-statuses). |
 | Hybrid worker doesn't run jobs or is unresponsive. | Troubleshoot using [Hybrid Runbook Worker diagnostics](/azure/automation/troubleshoot/hybrid-runbook-worker). |
 | Runbooks suddenly stopped working. | Ensure you've [migrated to managed identity](/azure/automation/migrate-run-as-accounts-managed-identity?tabs=sa-managed-identity#cert-renewal) and that webhooks haven't expired. |
 | Need help with passing parameters into a webhook. | See [Start a runbook from a webhook](/azure/automation/automation-webhooks#parameters-used-when-the-webhook-starts-a-runbook). |
-| Using both `Az` and `AzureRM` modules. | This scenario isn't supported. Use only [Az modules in runbooks](/azure/automation/automation-update-azure-modules). |
+| You want to use both `Az` and `AzureRM` modules in runbook. | This scenario isn't supported. Use only [Az modules in runbooks](/azure/automation/automation-update-azure-modules). |
 | Can't start or schedule a runbook. | Verify that the runbook is in a [published state](/azure/automation/manage-runbooks#publish-a-runbook). |
 | Runbook is suspended or failed unexpectedly. | Review [job statuses](/azure/automation/automation-runbook-execution#job-statuses). Add logging to the runbook using [output streams](/azure/automation/automation-runbook-output-and-messages#working-with-message-streams). If the job fails three times, check [Automation limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#automation-limits) and consider using a [Hybrid Worker](/azure/automation/automation-hybrid-runbook-worker). |
 
@@ -49,7 +49,7 @@ Connectivity problems are a common cause of issues with Hybrid Runbook Workers.
 |-----------|----------------|
 | Unexpected password prompt appears when using `sudo`. | See [Linux runbook worker prompts for password](/azure/automation/troubleshoot/hybrid-runbook-worker#prompt-for-password). |
 | Log file shows "The specified class does not exist." | See [Class does not exist error](/azure/automation/troubleshoot/hybrid-runbook-worker#class-does-not-exist). |
-| Linux job is stuck in **Running** state | 1. Switch to `sudo` permissions: `sudo su`<br>2. Check to make sure that `hwd` service is running: `systemctl status hwd.service`<br>3. Open the following file in Hybrid Worker: `vi /lib/systemd/system/hwd.service`<br>4. Update the setting from `CPUQuota=25%` to `CPUQuota=` to make the usage unrestricted as the following: <br><br>`[Unit]`<br>`Description=HW Service`<br>`After=network.target`<br>`[Service]`<br>`Type=simple`<br>`ExecStart=/usr/bin/python3 .../automationWorkerStarterScript.py`<br>`TimeoutStartSec=5`<br>`Restart=always`<br>`RestartSec=10s`<br>`TimeoutStopSec=600`<br>`CPUQuota=`<br>`KillMode=process`<br>`[Install]`<br>`WantedBy=multi-user.target`<br><br> 5. Restart `hwd` service: `systemctl daemon-reload`and `systemctl restart hwd.service`<br>|
+| Linux job is stuck in **Running** state | 1. Switch to `sudo` permissions: `sudo su`<br>2. Check to make sure that `hwd` service is running: `systemctl status hwd.service`<br>3. Open the following file in Hybrid Worker: `vi /lib/systemd/system/hwd.service`<br>4. Update the setting from `CPUQuota=25%` to `CPUQuota=` to make the usage unrestricted as shown in the following example: <br><br>`[Unit]`<br>`Description=HW Service`<br>`After=network.target`<br>`[Service]`<br>`Type=simple`<br>`ExecStart=/usr/bin/python3 .../automationWorkerStarterScript.py`<br>`TimeoutStartSec=5`<br>`Restart=always`<br>`RestartSec=10s`<br>`TimeoutStopSec=600`<br>`CPUQuota=`<br>`KillMode=process`<br>`[Install]`<br>`WantedBy=multi-user.target`<br><br> 5. Restart `hwd` service: <br>`systemctl daemon-reload` <br> `systemctl restart hwd.service`<br>|
 
 ## Other error messages