fix review comments

Author: the-gigi

docs/source/routing/self-hosted/managed-hosting/railway.mdx

@@ -26,7 +26,7 @@ The fastest way to deploy the Apollo Router on Railway is using the official tem
 
 1. **Deploy the template**:
    - Visit the [Apollo Router Template repository](https://github.com/apollographql/router-template)
-   - Click the "Deploy on Railway" button: [![Deploy on Railway](https://railway.app/button.svg)](https://railway.com/deploy/apollo-router)
+   - Click the **Deploy on Railway** button: [![Deploy on Railway](https://railway.app/button.svg)](https://railway.com/deploy/apollo-router)
 
 2. **Configure your deployment**:
    - **Template Name**: Enter a name for your deployment (e.g., `my-apollo-router`)
@@ -82,23 +82,23 @@ The Apollo Runtime container provides a production-ready router with sensible de
    - Select **Deploy from GitHub repo**
    - Connect and authorize your GitHub repository
 
-2. **Configure the service**:
-   - Railway will automatically detect your Dockerfile and configure the service
-   - The build and deployment process will start automatically
+2. **Railway automatically configures the service**:
+   - Railway detects your Dockerfile and configures the service
+   - The build and deployment process starts automatically
 
 3. **Set environment variables**:
    - In your project dashboard, go to the **Variables** tab
    - Add `APOLLO_KEY` and set it to your Graph API key
    - Add `APOLLO_GRAPH_REF` and set it to your graph reference
    - Railway automatically provides the `PORT` variable
 
-4. **Deploy**: Railway will automatically deploy your service after setting the environment variables
+4. **Automatic deployment**: Railway automatically redeploys your service when environment variables are added
 
 ## Apollo MCP Server
 
 The Apollo Runtime container includes an optional MCP (Model Context Protocol) server that provides AI assistants with structured access to your GraphQL schema and operations.
 
-### Enabling MCP Server
+### Enable the MCP Server
 
 The MCP server is disabled by default. To enable it, set the `MCP_ENABLE` environment variable to `1`:
 
@@ -111,14 +111,14 @@ The MCP server is disabled by default. To enable it, set the `MCP_ENABLE` enviro
 
 When enabled, the MCP server provides:
 - Schema introspection capabilities for AI assistants
-- Structured access to GraphQL operations  
+- Structured access to GraphQL operations
 - Enhanced development experience with AI tools
 
 ## Configuration options
 
 ### Environment variables
 
-The router accepts several environment variables for configuration:
+The router accepts multiple environment variables for configuration:
 
 - `APOLLO_KEY`: Your Graph API key (required)
 - `APOLLO_GRAPH_REF`: Your graph reference (required)
@@ -195,7 +195,7 @@ Railway automatically handles scaling based on your usage:
 ### Common issues
 
 1. **Service won't start**:
-   - Check that `APOLLO_KEY` and `APOLLO_GRAPH_REF` are correctly set in the Variables tab
+   - Check that `APOLLO_KEY` and `APOLLO_GRAPH_REF` are correctly set in the **Variables** tab
    - Verify your graph exists in GraphOS Studio
    - Check deployment logs in the Railway dashboard
 
@@ -211,7 +211,7 @@ Railway automatically handles scaling based on your usage:
    - Check that your Dockerfile is valid and the base image is accessible
    - Review build logs in the Railway dashboard for specific error messages
 
-### Getting help
+### Get help
 
 - Check the [Railway documentation](https://docs.railway.app/) for platform-specific issues
 - Visit the [Apollo Router documentation](/router) for router configuration

docs/source/routing/self-hosted/managed-hosting/render.mdx

@@ -26,7 +26,7 @@ The fastest way to deploy the Apollo Router on Render is using the official temp
 
 1. **Deploy the template**:
    - Visit the [Apollo Router Template repository](https://github.com/apollographql/router-template)
-   - Click the "Deploy to Render" button: [![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=github.com/apollographql/router-template)
+   - Click the **Deploy to Render** button: [![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=github.com/apollographql/router-template)
 
 2. **Configure your service**:
    - **Service Name**: Enter a name for your router service (e.g., `my-apollo-router`)
@@ -106,7 +106,7 @@ The Apollo Runtime container provides a production-ready router with sensible de
 
 2. **Configure the service**:
    - **Runtime**: Docker
-   - **Build Command**: Leave empty (Docker will handle the build)
+   - **Build Command**: Leave empty (Docker handles the build)
    - **Start Command**: Leave empty (defined in Dockerfile)
 
 3. **Set environment variables**:
@@ -120,7 +120,7 @@ The Apollo Runtime container provides a production-ready router with sensible de
 
 The Apollo Runtime container includes an optional MCP (Model Context Protocol) server that provides AI assistants with structured access to your GraphQL schema and operations.
 
-### Enabling MCP Server
+### Enable the MCP Server
 
 The MCP server is disabled by default. To enable it, set the `MCP_ENABLE` environment variable to `1`:
 
@@ -148,7 +148,7 @@ When enabled, the MCP server provides:
 
 ### Environment variables
 
-The router accepts several environment variables for configuration:
+The router accepts multiple environment variables for configuration:
 
 - `APOLLO_KEY`: Your Graph API key (required)
 - `APOLLO_GRAPH_REF`: Your graph reference (required)
@@ -171,7 +171,7 @@ To use a custom domain with your Render deployment:
 
 ## Security considerations
 
-**Important security settings to review before production deployment:**
+Important security settings to review before production deployment:
 
 ### CORS Configuration
 The template includes development-friendly CORS settings that may not be suitable for production:
@@ -196,7 +196,7 @@ cors:
 ## Monitoring and observability
 
 ### Render metrics
-Render provides built-in metrics for your service including:
+Render provides built-in metrics for your service:
 - CPU and memory usage
 - Request metrics
 - Response times
@@ -236,7 +236,7 @@ Render automatically handles scaling based on your service plan:
    - Verify your `APOLLO_KEY` has the correct permissions
    - Check that your `APOLLO_GRAPH_REF` format is correct (e.g., `graph-name@variant`)
 
-### Getting help
+### Get help
 
 - Check the [Render documentation](https://render.com/docs) for platform-specific issues
 - Visit the [Apollo Router documentation](/router) for router configuration