Fix review findings: StatefulSet→Deployment, redundant paragraph, nits

- Align MCPServer backend workload type with CRD reference (Deployment,
  not StatefulSet)
- Remove redundant closing paragraph in scaling guide
- Add Redis address comment in vMCP scaling example
- Use precise CRD description for forEach collection field

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

Author: 2 people

docs/toolhive/guides-k8s/run-mcp-k8s.mdx

@@ -443,8 +443,8 @@ kubectl -n <NAMESPACE> describe mcpserver <NAME>
 
 ## Horizontal scaling
 
-MCPServer creates two separate workloads: a proxy runner Deployment and a
-backend MCP server StatefulSet. You can scale each independently:
+MCPServer creates two separate Deployments: a proxy runner and a backend MCP
+server. You can scale each independently:
 
 - `spec.replicas` controls the proxy runner pod count
 - `spec.backendReplicas` controls the backend MCP server pod count
@@ -459,7 +459,7 @@ Common configurations:
   auth and connection overhead is the bottleneck with a single backend.
 - **Scale only the backend** (omit `replicas`, `backendReplicas: M`): useful
   when tool execution is CPU/memory-bound and the proxy is not a bottleneck. The
-  backend StatefulSet uses client-IP session affinity to route repeated
+  backend Deployment uses client-IP session affinity to route repeated
   connections to the same pod - subject to the same NAT limitations as
   proxy-level affinity.
 - **Scale both** (`replicas: N`, `backendReplicas: M`): full horizontal scale.
@@ -512,7 +512,7 @@ spec:
       terminationGracePeriodSeconds: 60
 ```
 
-The same 30-second default applies to the backend StatefulSet.
+The same 30-second default applies to the backend Deployment.
 
 :::
 

docs/toolhive/guides-vmcp/composite-tools.mdx

@@ -389,11 +389,11 @@ spec:
 
 | Field           | Description                                           | Default |
 | --------------- | ----------------------------------------------------- | ------- |
-| `collection`    | Template expression that produces an array            | —       |
+| `collection`    | Template expression that resolves to a JSON array     | -       |
 | `itemVar`       | Variable name for the current item                    | item    |
 | `maxParallel`   | Maximum concurrent iterations (max 50)                | 10      |
 | `maxIterations` | Maximum total iterations (max 1000)                   | 100     |
-| `step`          | Inner step definition (tool call to execute per item) | —       |
+| `step`          | Inner step definition (tool call to execute per item) | -       |
 | `onError`       | Error handling: `abort` (stop) or `continue` (skip)   | abort   |
 
 :::note

docs/toolhive/guides-vmcp/scaling-and-performance.mdx

@@ -75,7 +75,7 @@ spec:
   replicas: 3
   sessionStorage:
     provider: redis
-    address: redis-master.toolhive-system.svc.cluster.local:6379
+    address: redis-master.toolhive-system.svc.cluster.local:6379 # Update to match your Redis Service location
     db: 0
     keyPrefix: vmcp-sessions
     passwordRef:
@@ -134,9 +134,6 @@ a dedicated vMCP instance per team instead.
 
 :::
 
-For stateful backends, vertical scaling or dedicated instances per team/use case
-are recommended instead of horizontal scaling.
-
 ## Next steps
 
 - [Explore Kubernetes operator guides](../guides-k8s/index.mdx) for managing MCP