Minor style updates

Author: DMallare

docs/source/routing/cloud/migrate-to-self-hosted.mdx

@@ -6,7 +6,7 @@ description: Migrate all Apollo GraphOS cloud graphs (Serverless and Dedicated)
 
 The Serverless and Dedicated plans end on [TODO SUNSET DATE]. After this date, cloud routers are no longer available.
 
-If you are on a Serverless or Dedicated plan, you will need to migrate your graphs to use self-hosted routers by [TODO SUNSET DATE]. After migration, move your organization to a [supported plan](https://www.apollographql.com/pricing).
+If you are on a Serverless or Dedicated plan, ymigrate your graphs to use self-hosted routers by [TODO SUNSET DATE]. After migrating your graphs, move your organization to a [supported plan](https://www.apollographql.com/pricing).
 
 During the migration window, your cloud router continues to receive traffic, schema updates, and configuration updates. The migration window ends on [TODO SUNSET DATE].
 
@@ -32,7 +32,7 @@ In Studio, navigate to your graph's **Cloud Router** page and click the **Router
 
 [TODO SCREENSHOT]
 
-If you cannot access the Cloud Router page (for example, if you have already changed your graph's hosting mode), use the Rover CLI to export the configuration.
+If you can't access the Cloud Router page (for example, if you have already changed your graph's hosting mode), use the Rover CLI to export the configuration.
 
 #### Using the Rover CLI
 
@@ -79,21 +79,21 @@ After you migrate all graphs to self-hosted mode, navigate to [TODO] to move you
 
 ## Frequently asked questions
 
-### What happens to my running cloud routers when I change my graph's hosting mode?
+### What happens to your running cloud routers when you change your graph's hosting mode?
 
-Changing a graph's hosting mode does not affect running cloud routers. Cloud routers continue to receive traffic, emit telemetry, and receive schema and configuration updates until a [shutdown event occurs for Serverless routers](/graphos/routing/cloud/serverless#automatic-deletion-of-unused-routers) or the migration period ends on [TODO SUNSET DATE].
+Changing a graph's hosting mode doesn't affect running cloud routers. Cloud routers continue to receive traffic, emit telemetry, and receive schema and configuration updates until a [shutdown event occurs for Serverless routers](/graphos/routing/cloud/serverless#automatic-deletion-of-unused-routers) or the migration period ends on [TODO SUNSET DATE].
 
-### How do I retrieve and update the configuration of my running cloud routers after converting to self-hosted mode?
+### How do you retrieve and update the configuration of your running cloud routers after converting to self-hosted mode?
 
-Use the [Rover CLI's `cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch) to fetch your cloud router configuration:
+Use the [`cloud config fetch` command](/rover/commands/cloud#cloud-config-fetch) to fetch your cloud router configuration:
 
 ```bash showLineNumbers={false}
 rover cloud config fetch <GRAPH_REF> > router.yaml
 ```
 
-Use the [Rover CLI's `cloud config update` command](/rover/commands/cloud#cloud-config-update) to update your running cloud routers' configuration. For example, to apply changes from a local `router.yaml`:
+Use the [`cloud config update` command](/rover/commands/cloud#cloud-config-update) to update your running cloud routers' configuration. For example, to apply changes from a local `router.yaml`:
 
-```bash
+```bash showLineNumbers={false}
 rover cloud config update --file router.yaml <GRAPH_REF>
 ```