lint

Signed-off-by: ChrisJBurns <[email protected]>

Author: ChrisJBurns

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

@@ -94,10 +94,9 @@ flowchart LR
 
 ### StreamableHTTP transport flow
 
-For MCP servers using StreamableHTTP transport, the proxy creates both
-a pod and a headless service. This allows direct HTTP communication between
-the proxy and MCP server while maintaining network isolation and service
-discovery.
+For MCP servers using StreamableHTTP transport, the proxy creates both a pod and
+a headless service. This allows direct HTTP communication between the proxy and
+MCP server while maintaining network isolation and service discovery.
 
 ```mermaid
 flowchart LR
@@ -180,8 +179,9 @@ When you apply an `MCPServer` resource, here's what happens:
    service to handle client connections
 4. The proxy creates the actual `MCPServer` pod containing your specified
    container image
-5. For STDIO transport, the proxy attaches directly to the pod; for SSE and StreamableHTTP
-   transport, a headless service is created for direct pod communication
+5. For STDIO transport, the proxy attaches directly to the pod; for SSE and
+   StreamableHTTP transport, a headless service is created for direct pod
+   communication
 6. Clients can now connect through the service → proxy → MCP server chain to use
    the tools and resources (note: external clients will need an ingress
    controller or similar mechanism to access the service from outside the
@@ -500,8 +500,8 @@ Common causes include:
   selectors
 - **Port configuration**: Verify the `port` field matches the MCP server's
   listening port
-- **Transport mismatch**: Ensure the `transport` field (stdio/sse/streamable-http) matches the
-  MCP server's capabilities
+- **Transport mismatch**: Ensure the `transport` field
+  (stdio/sse/streamable-http) matches the MCP server's capabilities
 - **Network policies**: Check if network policies are blocking communication
 
 </details>