address comment

Author: peppescg

docs/toolhive/guides-ui/run-mcp-servers.md

@@ -104,8 +104,8 @@ states.
 ## Install a custom MCP server
 
 You're not limited to the MCP servers in the registry. You can run remote MCP
-providing a url or your own local custom MCP servers using Docker images or
-source packages.
+servers by providing a URL, or your own local custom MCP servers using Docker
+images or source packages.
 
 ### Remote MCP server
 
@@ -117,37 +117,37 @@ On the configuration form, enter:
 
 1. A unique **name** for the MCP server. [Required]
 
-2. the server **url** of the MCP server. [Required]
+2. The server **url** of the MCP server. [Required]
 
 3. The **transport protocol** that the MCP server uses. [Required] ToolHive
    supports server-sent events (SSE), and Streamable HTTP (default value) for
    real-time communication. The protocol must match what the MCP server
    supports.
 
-4. The authorization method (default **None** simple transparent forwarding).
+4. The authorization method (default **None**, simple transparent forwarding).
    ToolHive supports OAuth2/OIDC, and dynamic client registration.
 
    Selecting **OAuth2** authentication method:
-   - the **authorize URL** where users are redirected to authenticate and
+   - The **authorize URL** where users are redirected to authenticate and
      authorize your MCP. [Required]
-   - the **token url** where your application exchanges the authorization code
+   - The **token URL** where your application exchanges the authorization code
      for access tokens. [Required]
-   - the **client id** for your application registered with the OAuth provider.
+   - The **client ID** for your application registered with the OAuth provider.
      [Required]
-   - the **client secret** key that proves your application's identity.
+   - The **client secret** key that proves your application's identity.
      [Required]
-   - the **scopes** list of permissions your app is requesting
+   - The **scopes** list of permissions your app is requesting
 
    Selecting **OIDC** authentication method:
-   - the base **issuer URL** of the OIDC provider. [Required]
-   - the **client id** for your application registered with the OIDC provider.
+   - The base **issuer URL** of the OIDC provider. [Required]
+   - The **client ID** for your application registered with the OIDC provider.
      [Required]
-   - the **client secret** key that proves your application's identity.
+   - The **client secret** key that proves your application's identity.
      [Required]
-   - the **PKCE** Proof Key for Code Exchange (RFC 7636), automatically enables
+   - The **PKCE** Proof Key for Code Exchange (RFC 7636), automatically enables
      PKCE flow without client_secret
 
-5. the **callback port** for the authentication redirect.
+5. The **callback port** for the authentication redirect.
 
 Click **Install server** to run the MCP server.