Address editorial review feedback

- Replace em dash with hyphen in telemetry caBundleRef note
- Fix ambiguous "Both X and Y cannot" phrasing for authServerRef
- Add MCPServerEntry to MCPGroup description paragraph
- Align comparison table to parallel noun phrase structure

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ChrisJBurns

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

@@ -676,9 +676,9 @@ spec:
       issuer: 'https://mcp.example.com'
 ```
 
-Both `authServerRef` and `externalAuthConfigRef` cannot point to an
-`embeddedAuthServer` type simultaneously. The same `authServerRef` field is
-available on MCPRemoteProxy resources.
+`authServerRef` and `externalAuthConfigRef` cannot both reference an
+`embeddedAuthServer` type. The same `authServerRef` field is available on
+MCPRemoteProxy resources.
 
 :::
 

docs/toolhive/guides-k8s/telemetry-and-metrics.mdx

@@ -175,7 +175,7 @@ spec:
 
 :::note
 
-`caBundleRef` cannot be used when `insecure` is set to `true` — they are
+`caBundleRef` cannot be used when `insecure` is set to `true` - they are
 mutually exclusive.
 
 :::

docs/toolhive/guides-vmcp/configuration.mdx

@@ -11,8 +11,8 @@ VirtualMCPServer resource. For a complete field reference, see the
 
 Before creating a VirtualMCPServer, you need an
 [MCPGroup](../reference/crd-spec.md#apiv1alpha1mcpgroup) to organize the backend
-MCP servers. An MCPGroup is a logical container that groups related MCPServer
-and MCPRemoteProxy resources together.
+MCP servers. An MCPGroup is a logical container that groups related MCPServer,
+MCPRemoteProxy, and MCPServerEntry resources together.
 
 Create a basic MCPGroup:
 
@@ -140,12 +140,12 @@ spec:
 
 **When to use MCPServerEntry vs. MCPRemoteProxy:**
 
-|                     | MCPServerEntry                                                 | MCPRemoteProxy                                                                    |
-| ------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------------------- |
-| **Infrastructure**  | No pods, services, or deployments                              | Creates a proxy pod and service                                                   |
-| **Use case**        | Lightweight catalog entries for well-known remote servers      | When you need request transformation, caching, or the full proxy middleware chain |
-| **Discovery**       | Discovered by VirtualMCPServer through MCPGroup membership     | Discovered by VirtualMCPServer through MCPGroup membership                        |
-| **SSRF protection** | Built-in URL validation blocks internal and metadata endpoints | N/A (proxy runs inside the cluster)                                               |
+|                     | MCPServerEntry                                                 | MCPRemoteProxy                                                                              |
+| ------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| **Infrastructure**  | No pods, services, or deployments                              | Creates a proxy pod and service                                                             |
+| **Use case**        | Lightweight catalog entries for well-known remote servers      | Proxied connections requiring request transformation, caching, or the full middleware chain |
+| **Discovery**       | Discovered by VirtualMCPServer through MCPGroup membership     | Discovered by VirtualMCPServer through MCPGroup membership                                  |
+| **SSRF protection** | Built-in URL validation blocks internal and metadata endpoints | N/A (proxy runs inside the cluster)                                                         |
 
 :::note