Fix em dashes and title case per review feedback

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

Author: 2 people

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

@@ -460,7 +460,7 @@ Common configurations:
 - **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
-  connections to the same pod — subject to the same NAT limitations as
+  connections to the same pod - subject to the same NAT limitations as
   proxy-level affinity.
 - **Scale both** (`replicas: N`, `backendReplicas: M`): full horizontal scale.
   Redis session storage is required when `replicas > 1`.
@@ -501,8 +501,8 @@ timeout are both 30 seconds with no headroom, so long-lived SSE or streaming
 connections may be dropped if they exceed the drain window.
 
 No preStop hook is injected by the operator. If your workload requires
-additional time — for example, to let kube-proxy propagate endpoint removal
-before the pod stops accepting traffic — override
+additional time - for example, to let kube-proxy propagate endpoint removal
+before the pod stops accepting traffic - override
 `terminationGracePeriodSeconds` via `podTemplateSpec`:
 
 ```yaml

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

@@ -411,7 +411,7 @@ accesses the `name` field of the current repository. You can also use
 
 `maxParallel` controls how many iterations run concurrently **on the pod that
 received the composite tool request**. Iterations are not distributed across
-vMCP replicas — all parallel backend calls originate from a single pod
+vMCP replicas - all parallel backend calls originate from a single pod
 regardless of `spec.replicas`. When sizing your deployment, account for the
 per-pod fan-out: a `maxParallel: 50` forEach step can open up to 50 simultaneous
 connections to backend MCP servers from one pod. Ensure both the vMCP pod

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

@@ -1,5 +1,5 @@
 ---
-title: Scaling and Performance
+title: Scaling and performance
 description:
   How to scale Virtual MCP Server deployments vertically and horizontally.
 ---
@@ -122,7 +122,7 @@ spec:
 
 `ClientIP` affinity relies on the source IP reaching kube-proxy. When clients
 sit behind a NAT gateway, corporate proxy, or cloud load balancer (common in
-EKS, GKE, and AKS), all traffic appears to originate from the same IP — routing
+EKS, GKE, and AKS), all traffic appears to originate from the same IP - routing
 every client to the same pod and eliminating the benefit of horizontal scaling.
 This fails silently: the deployment appears healthy but only one pod handles all
 load.

docs/toolhive/guides-vmcp/tool-aggregation.mdx

@@ -149,7 +149,7 @@ spec:
 ### Annotation overrides
 
 Override MCP tool annotations to provide hints to LLM clients about tool
-behavior. Annotations are optional—only set the fields you want to override:
+behavior. Annotations are optional - only set the fields you want to override:
 
 ```yaml title="VirtualMCPServer resource"
 spec: