docs: apply suggestion for migration

Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>

docs/pages/admin-guides/migrate-plans.mdx

@@ -235,14 +235,15 @@ To migrate Teleport agents:
    upgrades the `stable/rolling` channel has all released versions.
 
 
-1. If you are using the Teleport Community Edition, [uninstall Teleport](./management/admin/uninstall-teleport.mdx)
-   and install the enterprise version. You can confirm if the `teleport` binary
-   is enterprise by running `teleport version`. The output will contain the words
-   `Teleport Enterprise`. The enterprise version of the `teleport`
+1. If you are using Teleport Community Edition, [uninstall Teleport](./management/admin/uninstall-teleport.mdx)
+   and install the enterprise edition of the `teleport` binary. You can confirm if the binary
+   is correct by running `teleport version`. The output will contain the words
+   `Teleport Enterprise`. The enterprise edition of the `teleport`
    binary should be used when connecting to Teleport Enterprise (Cloud) or
    Teleport Enterprise (Self-Hosted).
 
 
+
 1. Update the `proxy_server` or `auth_servers` field in each Agent configuration
    file to point to the address of your new Teleport Enterprise cluster. By
    default, on Linux servers, the configuration is located in the