Update docs/source/deploy.mdx

Co-authored-by: Michelle Mabuyo <[email protected]>

Author: lennyburdette

docs/source/deploy.mdx

@@ -59,6 +59,10 @@ To learn more, review the [Apollo Runtime container documentation](/graphos/rout
 
 ### Using a load balancer
 
-Because [MCP is a stateful protocol](https://modelcontextprotocol.io/docs/learn/architecture#lifecycle-management), the default configuration of most load balancers is incorrect. When the MCP client initializes a session with Apollo MCP Server, it receives a session identifier unique to that server instance. If the load balancer routes subsequent requests to a different instance, Apollo MCP Server will reject the request as unauthorized. 
+Because [MCP is a stateful protocol](https://modelcontextprotocol.io/docs/learn/architecture#lifecycle-management), you need to configure your load balancer to keep each session on the _same server instance_.
 
-To run Apollo MCP Server in a high-availability, multi-instance setup, you must configure your load balancer to use session affinity ("sticky sessions") based on the `mcp-session-id` header. Load balancers offered by major cloud vendors do not support header-based affinity, so you will need software like Nginx, HAProxy, or Istio/Envoy Proxy in front of your Apollo MCP instances.
+When the MCP client initializes a session with Apollo MCP Server, it receives a session identifier unique to that server instance through the `mcp-session-id` header. You must enable session affinity ("sticky sessions") in your load balancer so that all requests that share the same `mcp-session-id` are routed to the same backend instance. 
+
+If the load balancer routes subsequent requests to a different instance, Apollo MCP Server will reject the request as unauthorized.
+
+Many load balancers offered by major cloud vendors don't support header-based session affinity. If yours does not, use software such as Nginx, HAProxy, or Envoy/Istio in front of your Apollo MCP Server instances.