fix: use lowercase for MCP server and client

Author: terry-xiaoyu

index.md

@@ -18,12 +18,12 @@ The MQTT transport protocol supports all the features of MCP and adds the follow
 
 - **Built-in Service Registry and Discovery**: MCP clients can discover available MCP servers from the MQTT broker.
 
-- **Built-in Load Balancing and Scalability**: MCP Servers can be scaled horizontally by adding more MCP server instances, while keeping the the MCP server side stateful.
+- **Built-in Load Balancing and Scalability**: MCP servers can be scaled horizontally by adding more MCP server instances, while keeping the the MCP server side stateful.
 
 Additionally, by setting access control permissions on the MQTT topics used by MCP clients and servers in the MQTT broker, authorization for clients and servers can be very flexibly implemented.
 
 ## Limitations
 
-MCP over MQTT is designed for remotely deployed MCP Servers, and the protocol requires a centralized MQTT broker to function. Although locally deployed MCP Servers can also use the MCP over MQTT, it may introduce additional deployment complexity.
+MCP over MQTT is designed for remotely deployed MCP servers, and the protocol requires a centralized MQTT broker to function. Although locally deployed MCP servers can also use the MCP over MQTT, it may introduce additional deployment complexity.
 
 We are not meant to replace the existing MCP transport layers (stdio and HTTP SSE), but to provide an alternative for edge computing and IoT applications, and for the backend services that want to use MQTT as their messaging protocol.

specification/2025-03-26/basic/mqtt_transport.md

@@ -14,7 +14,7 @@ It should be read in conjunction with the [MCP Specification](https://spec.model
 
   Multiple connections with the same `server-name` are considered multiple instances of the same MCP server and provide exactly the same service. When the MCP client sends an initialize message, it should select one of them according to a client-side determined strategy.
 
-  Multiple MCP Servers with different `server-name`s may still provide similar functions. In this case, when the client sends an initialize message, it should select one of them to establish a connection as needed. The selection criteria can be based on the client's permissions, recommendations from a LLM, or the user's choice.
+  Multiple MCP servers with different `server-name`s may still provide similar functions. In this case, when the client sends an initialize message, it should select one of them to establish a connection as needed. The selection criteria can be based on the client's permissions, recommendations from a LLM, or the user's choice.
 
   After connected to the MQTT broker, the broker may suggest a `server-name` to the MCP server by including a `MCP-SERVER-NAME` user property in the MQTT CONNECT message. If so, the MCP server **MUST** use this `server-name` as its server name. If the broker does not suggest a `server-name`, the MCP server **SHOULD** use a default `server-name` based on the functionality it provides.
 
@@ -79,7 +79,7 @@ The Client ID of the MCP server can be any string except `/`, `+` and `#`, refer
 
 ### MCP Client
 
-The Client ID of the MCP Client, referred to as `mcp-client-id`, can be any string except `/`, `+` and `#`, each time an initialization request is made, a different client-id must be used. It is recommended to use a hex string UUID.
+The Client ID of the MCP client, referred to as `mcp-client-id`, can be any string except `/`, `+` and `#`, each time an initialization request is made, a different client-id must be used. It is recommended to use a hex string UUID.
 
 ## MQTT Topics and Topic Filters
 
@@ -101,7 +101,7 @@ The Client ID of the MCP Client, referred to as `mcp-client-id`, can be any stri
 | Topic Name                                                             | Messages                                                                                               |
 |------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
 | `$mcp-server/capability/list-changed/{server-id}/{server-name}`     | capability list changed notification.                                                                  |
-| `$mcp-server/presence/{server-id}/{server-name}`                    | Presence messages for the MCP Server. <br> See [ServiceDiscovery](#service-discovery) for more details |
+| `$mcp-server/presence/{server-id}/{server-name}`                    | Presence messages for the MCP server. <br> See [ServiceDiscovery](#service-discovery) for more details |
 | `$mcp-server/capability/resource-updated/{server-id}/{server-name}` | Resource update notification.                                                                          |
 | `$mcp-rpc-endpoint/{mcp-client-id}/{server-name}`                     | RPC requests, responses and notifications.                                                             |