Use the imperative mood for instructions and avoid "You can".

```suggestion
Reference environment variables directly in your configuration file using the `${env.VAR_NAME}` syntax. Use this syntax for existing environment variables that don't follow the `APOLLO_MCP_*` naming convention.
```

Use the imperative mood for instructions and active voice.

```suggestion
Provide a fallback value using the `${env.VAR_NAME:-default}` syntax. If the environment variable is not set, Apollo MCP Server uses the default value:
```

Use active voice and remove bolding used for emphasis.

```suggestion
Apollo MCP Server uses the default value when the variable is unset or empty. This matches bash and Apollo Router behavior.
```

Remove bolding used for emphasis, use active voice, and use present tense.

```suggestion
Nested references are not expanded. Apollo MCP Server treats default values as literal text. If your default contains `${env.OTHER}`, it appears literally in the output:
```

Remove bolding used for emphasis and use present tense.

```suggestion
Quotes don't escape closing braces. Brace matching in default values is purely depth-based. A `}` inside quotes terminates the placeholder:
```

Remove the filler word "still" and replace the idiomatic "wins" with clearer language describing the system behavior.

```suggestion
`APOLLO_MCP_*` environment variables take precedence over expanded values in the config file. For example, if you set both `${env.MY_ENDPOINT}` in the config and `APOLLO_MCP_ENDPOINT` as an environment variable, the system uses `APOLLO_MCP_ENDPOINT`.
```

Specify the code block's language for syntax highlighting.

```suggestion
```text
```