Clarify MCP config precedence wording

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: loganrosen

content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md

@@ -91,7 +91,7 @@ You can configure MCP servers for a specific project by adding a JSON file to th
 | `.mcp.json` (in any directory from your working directory up to the repository root) | Local or per-checkout configuration; commonly placed at the project root |
 | `.github/mcp.json` | Shared configuration that is committed to the repository |
 
-When you start {% data variables.copilot.copilot_cli_short %} inside a Git repository, the CLI walks from your current working directory up to the repository root, loading the first MCP configuration file it finds at each directory level. If both files exist in the same directory, `.mcp.json` takes precedence over `.github/mcp.json`. When server names conflict, definitions in files closer to your working directory take precedence. Project-level definitions also take precedence over those in `~/.copilot/mcp-config.json`. For more information on relative trust, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference#mcp-server-trust-levels).
+When you start {% data variables.copilot.copilot_cli_short %} inside a Git repository, the CLI walks from your current working directory up to the repository root, loading MCP configuration files along the way. If both `.mcp.json` and `.github/mcp.json` exist in the same directory, `.mcp.json` takes precedence. When server names conflict, definitions in files closer to your working directory take precedence. Project-level definitions also take precedence over those in `~/.copilot/mcp-config.json`. For more information on relative trust, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference#mcp-server-trust-levels).
 
 Project-level files can use either the `mcpServers` top-level object shown in `~/.copilot/mcp-config.json`, or the bare top-level format where each key is an MCP server name. For example, this configuration uses the `mcpServers` object: