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

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: yrobla

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

@@ -455,11 +455,12 @@ actual MCP server and executes tools.
 
 ### Session routing for backend replicas
 
-MCP connections are stateful: once a client establishes a session with a
-specific backend pod, all subsequent requests in that session must reach the
-same pod. When `backendReplicas > 1` and Redis session storage is configured,
-the proxy runner uses Redis to store a session-to-pod mapping so every proxy
-runner replica knows which backend pod owns each session.
+For stateful MCP servers, once a client establishes a session with a specific
+backend pod, subsequent requests in that session need to reach the same pod.
+When `backendReplicas > 1` and Redis session storage is configured, the proxy
+runner uses Redis to store a session-to-pod mapping so every proxy runner
+replica knows which backend pod owns each session. Stateless backends can use
+non-sticky routing by setting `sessionAffinity` to `None`.
 
 When Redis session storage is configured and a backend pod is restarted or
 replaced, its entry in the Redis routing table is invalidated and the next