Update reload-the-page.md

Author: Cloud-Writer

SharePoint/SharePointOnline/workflows/reload-the-page.md

@@ -41,7 +41,7 @@ This error occurs if SharePoint 2013 Workflows are in a suspended state for the
 
 You can remove the current SharePoint site's suspension by removing SharePoint 2013 Workflows that have exceeded their limits. Use the Workflow Settings page, or delete workflows using SharePoint Designer.
 
-The cleanup process isn't instant. It takes time and the Workflow Health switches to a **Connected** status when it's done:
+The cleanup process isn't instant. It takes time and the Workflow Health switches to a **Connected** status when it is done:
 
 :::image type="content" source="./media/reload-the-page/workflow-connected.png" alt-text="Screenshot of the Workflow Health page showing workflow status as connected.":::
 
@@ -51,7 +51,7 @@ You can identify the workflows to be removed by using the **ShowScopeDebugInfo()
 
 ### How to run the ShowScopeDebugInfo() Function
 
-1. On the site that is having the Workflow problem, select Settings (the gear icon), and then select **Site Settings** > **Workflow Settings** > **Workflow Health**.
+1. On the site that's having the Workflow problem, select Settings (the gear icon), and then select **Site Settings** > **Workflow Settings** > **Workflow Health**.
     - You can also access Workflow Health from a URL. Example URL: `https://contoso.sharepoint.com/sites/test/_layouts/15/WorkflowServiceHealth.aspx` - in this example, replace *contoso* with your domain, and *test* with the name of the SharePoint site.
 1. Open the Developer tools from the browser (Microsoft Edge or Google Chrome is recommended).
     - For Microsoft Edge, press the F12 key to toggle open Developer Tools.
@@ -106,6 +106,6 @@ You can identify the workflows to be removed by using the **ShowScopeDebugInfo()
 
     **Workflows are suspended**
 
-1. Once a Workflow or Workflows are removed, a cleanup process is started. You can track the progress by refreshing the Workflow Service Health page and executing the ShowScopeDebugInfo function. **ActiveMessageCount**, **ScopeSizeInBytes**, and **CorrelationFilterCount** will go down, depending on which limit was exceeded.  **ActiveMessageCount** is the slowest and might take days to clear up, but it isn’t blocking. Once the core of the cleanup background job is done, the Workflow Service Health page will no longer display **Workflows are suspended**, and the **StatusDetails** will no longer have a value.
+1. Once a Workflow or Workflows are removed, a cleanup process is started. You can track the progress by refreshing the Workflow Service Health page and executing the ShowScopeDebugInfo function. **ActiveMessageCount**, **ScopeSizeInBytes**, and **CorrelationFilterCount** will go down, depending on which limit was exceeded. **ActiveMessageCount** is the slowest and might take days to clear up, but it isn’t blocking. Once the core of the cleanup background job is done, the Workflow Service Health page will no longer display **Workflows are suspended**, and the **StatusDetails** will no longer have a value.
 
 If you can't fix the issue by removing workflows, you might opt to open a support request. If you choose to open a support request, gather some additional information about the workflow health by using the **ShowScopeDebugInfo()** function. For more information about the **ShowScopeDebugInfo()** function, see [Gather SharePoint 2013 Workflow troubleshooting data with ShowScopeDebugInfo](./gather-workflow-data.md).