Update deploy.mdx

Author: lennyburdette

docs/source/deploy.mdx

@@ -63,6 +63,6 @@ Because [MCP is a stateful protocol](https://modelcontextprotocol.io/docs/learn/
 
 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.
+If the load balancer routes subsequent requests to a different instance, Apollo MCP Server rejects the request because it doesn't recognize the session id.
 
-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.
+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 the Apollo MCP Server instances.