Fix typo and clarify MachineNotFound error steps

Author: fnedjadi

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

@@ -66,4 +66,4 @@ _Original KB number:_   4555406
 |AccountLockedOut|400|Unattended|This error occurs when an internal system policy has prevented an account from creating a session on the machine because of too many sign-in attempts or password change attempts for the account. It's related to an on-premises configuration, not Power Automate licenses. Check that password rotation policies don't interfere with your scheduled runs, causing many incorrect sign-in attempts. If this error occurs regularly, work with your IT administrator to review sign-in attempt logs and account lockout policies.|
 |LogonTypeNotGranted|400|Unattended|For more information, see [troubleshooting documentation for logon type not granted](logon-type-has-not-been-granted.md).|
 |UnallowedTenantForConnectWithSignIn|403|Attended|This error occurs when using a [connect with sign-in](/power-automate/desktop-flows/desktop-flow-connections#connect-with-sign-in-for-attended-runs) connection on an Active Directory (AD) domain-joined machine without adding your tenant to the allowlist. </br> For more information, see ["UnallowedTenantForConnectWithSignIn" error in a Power Automate desktop flow](troubleshoot-unallowed-tenant-for-connect-with-sign-in.md).|
-|MachineNotFound|404|Attended</br>Unattended|This error occurs when the machine was unregistered durring a run or if the CDS organization has been migrated to a different region.</br> Please ensure the machine is properly registered, confirm that your script does not re-register the machine during a run and verify the connections.|
+|MachineNotFound|404|Attended</br>Unattended|This error can occur when the machine is unregistered during a run or if the CDS organization has been migrated to a different region. Verify that:</br>- Your machine is still registered by viewing its status in the machine runtime application.</br>- Your desktop flows connection is not broken in the Power Automate portal.</br>- Your script does not register the run during.|