minor edits

Author: haywoodsloan

support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md

@@ -357,10 +357,14 @@ Admins can use the [Microsoft.PowerApps.Administration.PowerShell](https://www.p
 Get-AdminFlowWithMigratingTriggerUrl -EnvironmentName <EnvironmentName>
 ```
 
-The cmdlet outputs the `DisplayName` and `FlowName` (ID) of each flow whose trigger URL will be migrated. 
+The cmdlet outputs the `DisplayName` and `FlowName` (ID) of each flow whose trigger URL will be migrated.
 
-Note: For smoother retrieval of all impacted flows at tenant level, You can use Get-AdminPowerAppEnvironment [script](https://learn.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/get-adminpowerappenvironment?view=pa-ps-latest) to list all environments in a tenant and subsequently use the Get-AdminFlowWithMigratingTriggerUrl to list impacted flows in the environment.
+To find all impacted flows across a tenant:
 
-```
-Get-AdminPowerAppEnvironment
-```
+1. Use [Get-AdminPowerAppEnvironment](/powershell/module/microsoft.powerapps.administration.powershell/get-adminpowerappenvironment) to list all app environments in the tenant:
+
+   ```powershell
+   Get-AdminPowerAppEnvironment
+   ```
+
+1. Then use `Get-AdminFlowWithMigratingTriggerUrl` to list the impacted flows for each environment.