Address review findings from Copilot and code review

- Fix ConfigMap source example: use volumes/volumeMounts with file
  path instead of CRD-level configMapRef inside configYAML
- Fix URL source example: use file.url instead of CRD-level
  url.endpoint inside configYAML
- Fix file source docs: clarify file.path and file.url are mutually
  exclusive within the file block
- Add MCPServerEntry transport options (sse and streamable-http)
- Fix resource type count: "three" → "four" in K8s intro
- Align "running" → "ready" in vMCP quickstart preceding text

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

Author: ChrisJBurns

docs/toolhive/guides-k8s/intro.mdx

@@ -67,7 +67,7 @@ or Gateway. To learn how to expose your MCP servers and connect clients, see
 
 ## Which resource type should I use?
 
-The operator introduces three resource types for MCP workloads. Choose based on
+The operator introduces four resource types for MCP workloads. Choose based on
 where your MCP server runs and how many servers you need to manage:
 
 | Resource             | Use when                                                                                                 |

docs/toolhive/guides-registry/configuration.mdx

@@ -286,16 +286,16 @@ registries:
     sources: ['remote']
 ```
 
-The fields `file` and `url` are mutually exclusive.
+Within the `file` block, `path` and `url` are mutually exclusive.
 
 **Configuration options:**
 
-- `path` (required): Path to the registry file on the filesystem. Mutually
-  exclusive with `url`
-- `url` (required): URL is the HTTP/HTTPS URL to fetch the registry file from.
-  Mutually exclusive with `file`
-- `timeout` (optional): The timeout for HTTP requests when using URL, defaults
-  to 30s, ignored when `file` is specified
+- `file.path` (required): Path to the registry file on the filesystem. Mutually
+  exclusive with `file.url`
+- `file.url` (required): HTTP/HTTPS URL to fetch the registry file from.
+  Mutually exclusive with `file.path`
+- `file.timeout` (optional): The timeout for HTTP requests when using `url`,
+  defaults to 30s
 
 ### Managed registry
 

docs/toolhive/guides-registry/deploy-operator.mdx

@@ -181,22 +181,29 @@ precedence over `branch`.
 
 ### ConfigMap source
 
-Read from a Kubernetes ConfigMap. Ideal for registry data managed within the
-cluster.
+Read from a Kubernetes ConfigMap. Mount the ConfigMap as a volume and reference
+the file path in `configYAML`.
 
 ```yaml title="registry-configmap.yaml"
 apiVersion: toolhive.stacklok.dev/v1alpha1
 kind: MCPRegistry
 metadata:
   name: configmap-registry
 spec:
+  volumes:
+    - name: registry-data
+      configMap:
+        name: registry-data
+  volumeMounts:
+    - name: registry-data
+      mountPath: /data/registry
+      readOnly: true
   configYAML: |
     sources:
       - name: local
         format: upstream
-        configMapRef:
-          name: registry-data
-          key: registry.json
+        file:
+          path: /data/registry/registry.json
         syncPolicy:
           interval: '15m'
     registries:
@@ -273,8 +280,8 @@ spec:
     sources:
       - name: remote
         format: upstream
-        url:
-          endpoint: https://example.com/registry.json
+        file:
+          url: https://example.com/registry.json
         syncPolicy:
           interval: '1h'
     registries:

docs/toolhive/guides-vmcp/configuration.mdx

@@ -104,9 +104,11 @@ metadata:
 spec:
   groupRef: my-group # Reference to the MCPGroup
   remoteURL: https://mcp.example.com/mcp
-  transport: streamable-http
+  transport: streamable-http # or sse
 ```
 
+The `transport` field is required and accepts `streamable-http` or `sse`.
+
 MCPServerEntry supports optional configuration for authentication and TLS:
 
 ```yaml

docs/toolhive/guides-vmcp/quickstart.mdx

@@ -104,7 +104,7 @@ Apply the resources:
 kubectl apply -f mcpservers.yaml
 ```
 
-Wait for both servers to be running:
+Wait for both servers to be ready:
 
 ```bash
 kubectl get mcpservers -n toolhive-system -w