Update job-not-start-as-expected.md

Author: Celiazhou1

support/azure/automation/runbooks/job-not-start-as-expected.md

@@ -1,20 +1,20 @@
 ---
-title: Troubleshoot issues with runbook execution start time
+title: Troubleshoot Issues with Runbook Execution Start Time
 description: Discusses an issue where jobs don't start as expected in Azure Automation.
-ms.date: 06/23/2025
+ms.date: 06/25/2025
 ms.reviewer: adoyle, v-weizhu
 ms.service: azure-automation
 ms.custom: sap:Runbook not working as expected
 ---
 # Troubleshoot issues with runbook execution start time in Azure Automation
 
-Process automation in Azure Automation lets you create and manage PowerShell, a PowerShell workflow, and graphical runbooks. Automation executes your runbooks based on the logic defined within them.
+Process automation in Azure Automation allows you to create and manage PowerShell, a PowerShell workflow, and graphical runbooks. Automation executes your runbooks based on the logic defined within them.
 
 ## Service-level agreement (SLA)
 
-The SLA for runbook automation is 30 minutes. It's expected that 99.999 percent of runbooks start within 5 minutes of the scheduled time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
+The SLA for runbook automation is 30 minutes. It's expected that 99.999 percent of runbooks start within five minutes of the scheduled time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
 
-The *SLA for the Automation Service - Process Automation* defines the following:
+The *SLA for the Automation Service - Process Automation* defines the following terms:
 
 - "Delayed Jobs" is the total number of Jobs, for a given Microsoft Azure subscription, that fail to start within 30 minutes of their Planned Start Times.
 - "Job" means the execution of a Runbook.
@@ -23,12 +23,12 @@ The *SLA for the Automation Service - Process Automation* defines the following:
 
 > [!NOTE]
 >
-> - Azure Automation enables recovery of runbooks deleted in last 29 days - Restore the deleted runbook by running a PowerShell script as a job in your Automation account. For more information, see [Restore deleted runbook](/azure/automation/manage-runbooks#restore-deleted-runbook).
-> - Before opening a case, follow the steps in [Data to collect when opening a case for Azure Automation](/azure/automation/troubleshoot/collect-data-microsoft-azure-automation-case). This process helps us resolve your case as quickly as possible.
+> - Azure Automation enables the recovery of runbooks deleted in the last 29 days. You can restore the deleted runbook by running a PowerShell script as a job in your Automation account. For more information, see [Restore deleted runbook](/azure/automation/manage-runbooks#restore-deleted-runbook).
+> - Before opening a case, follow the steps in [Data to collect when opening a case for Azure Automation](/azure/automation/troubleshoot/collect-data-microsoft-azure-automation-case). This process helps resolve your case as quickly as possible.
 
 ## References
 
 - [Start a runbook in Azure Automation](/azure/automation/start-runbooks)
 - [Azure Automation runbook types](/azure/automation/automation-runbook-types)
 
-[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]