Updates from editor

Author: v-phoebh

support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md

@@ -29,7 +29,7 @@ You might also receive one of these common suberror codes:
 
 ## How to investigate
 
-You can view the lifecycle events of desktop flows in the queue from the monitor run details page, specifically in the [queue events section](/power-automate/desktop-flows/monitor-run-details#view-queue-events). These events provide detailed information about each launch attempt and can help you identify the underlying root cause of queue-based errors.
+You can view lifecycle events for desktop flows in the queue from the monitor run details page, specifically in the [queue events section](/power-automate/desktop-flows/monitor-run-details#view-queue-events). These events provide detailed information about each launch attempt and can help you identify the underlying root cause of queue-based errors.
 
 ## Cause
 

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -50,7 +50,7 @@ _Original KB number:_   4555406
 |EndpointDoNotExist|404|Attended</br>Unattended|The endpoint wasn't found.</br>Register your machine again and schedule new runs.</br>This error typically occurs when the machine registration is deleted during the run, such as when the machine is re-registered.|
 |GroupIsEmpty|400|Attended</br>Unattended|The machine group is empty.</br> Add machines to the group, then reschedule new runs.|
 |MSEntraMachineAlwaysPromptingForPassword|400|Unattended|For more information about this error code, see [An unattended desktop flow run fails with the MSEntraMachineAlwaysPromptingForPassword error](msentramachinealwayspromptingforpassword-error.md).|
-|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.</br>To solve this issue, see [Troubleshoot desktop flow run queue-based errors](troubleshoot-desktop-flow-run-queue-errors.md) and inspect [queue events in the monitor run details page](/power-automate/desktop-flows/monitor-run-details#view-queue-events).|
+|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.</br>To solve this issue, see [Troubleshoot desktop flow run queue-based errors](troubleshoot-desktop-flow-run-queue-errors.md) and inspect the [queue events in the monitor run details page](/power-automate/desktop-flows/monitor-run-details#view-queue-events).|
 |DesktopFlowsActionThrottled|429|Attended</br>Unattended|The desktop flow action failed because of throttling. This error code appears when too many desktop flows use the same connection. Check your connection usage and assign your desktop flows to multiple connections.|
 |DesktopFlowsActionTimeout|400|Attended</br>Unattended|The execution of the desktop flow action exceeded maximum duration.</br> Increase the time-out value that's set on the action or split the desktop flow into several shorter desktop flows.|
 |OnPremiseDataGatewayNotAvailable|502|Attended</br>Unattended|This error code only occurs when using an on-premises data gateway (deprecated) to connect to the machine. Check that the targeted machine and the data gateway on that machine are up and running.|