Apply editorial polish to v0.27.1 release docs

- Use singular "Client ID Metadata Document (CIMD)" to match RFC and PR #5085.
- Replace "registers itself" with "identifies itself to" so the lead-in does
  not contradict the CIMD bullet's "no registration round-trip" claim.
- Expand "HA" on first use in auth-k8s.mdx; flip the passive lead-in to
  active and parallel the redis-session-storage page.
- Capitalize "Standalone" in the storage-block code title to match its
  Sentinel and Cluster peers.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: github-actions[bot]

docs/toolhive/guides-cli/run-mcp-servers.mdx

@@ -684,10 +684,10 @@ thv run https://protected-api.com/mcp --name my-server
 ```
 
 If authentication is required, ToolHive will prompt you to complete the OAuth
-flow. When no client credentials are provided, ToolHive registers itself with
-the authorization server using one of two mechanisms:
+flow. When no client credentials are provided, ToolHive identifies itself to the
+authorization server using one of two mechanisms:
 
-- **Client ID Metadata Documents (CIMD).** If the authorization server's
+- **Client ID Metadata Document (CIMD).** If the authorization server's
   discovery document sets `client_id_metadata_document_supported: true`,
   ToolHive presents
   [`https://toolhive.dev/oauth/client-metadata.json`](https://toolhive.dev/oauth/client-metadata.json)

docs/toolhive/guides-k8s/auth-k8s.mdx

@@ -649,10 +649,11 @@ For a complete walkthrough, see
 By default, the embedded authorization server stores sessions in memory.
 Upstream tokens are lost when pods restart, requiring users to re-authenticate.
 For production deployments, configure a Redis backend by adding a `storage`
-block to your `MCPExternalAuthConfig`. Three connection modes are supported, and
-exactly one must be set:
+block to your `MCPExternalAuthConfig`. The `redis` block supports three
+connection modes; you must set exactly one:
 
-- **Sentinel** (`sentinelConfig`) - self-managed Redis with Sentinel-based HA
+- **Sentinel** (`sentinelConfig`) - self-managed Redis with Sentinel-based high
+  availability (HA)
 - **Standalone** (`addr` only) - managed Redis services that expose a single
   endpoint, such as GCP Memorystore Basic/Standard or Azure Cache for Redis
 - **Cluster** (`addr` with `clusterMode: true`) - managed Redis Cluster
@@ -677,7 +678,7 @@ storage:
         key: password
 ```
 
-```yaml title="storage block for MCPExternalAuthConfig - standalone"
+```yaml title="storage block for MCPExternalAuthConfig - Standalone"
 storage:
   type: redis
   redis: