Potential fix for pull request finding

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

Author: MiguelsPizza

packages/webmcp-local-relay/reference.mdx

@@ -173,7 +173,7 @@ The embed also monkey-patches `navigator.modelContext.elicitInput` so that elici
 
 The widget reconnects automatically using exponential backoff (1.5x multiplier) from `500ms` up to `3000ms`, stopping after 100 attempts.
 
-**Port range discovery and browser discovery:** The server tries ports `9333–9348` instead of failing on a single port. The chosen port is persisted to `~/.webmcp/relay-port.json` for stable restarts. The widget probes the port range sequentially with a state machine (`connected → retry-same-endpoint → rediscover`) and caches discovered endpoints in `sessionStorage`.
+**Port range discovery and browser probing:** The server tries ports `9333–9348` instead of failing on a single port. The chosen port is persisted to `~/.webmcp/relay-port.json` for stable restarts. The widget probes the port range sequentially with a state machine (`connected → retry-same-endpoint → rediscover`) and caches discovered endpoints in `sessionStorage`.
 
 **Subprotocol handshake:** WebSocket connections use `webmcp.v1` / `webmcp-discovery.v1` subprotocols. The server sends a `server-hello` message with relay identity (`instanceId`, `label`, `workspace`, `relayId`) on connect.