Add limitation for websocket logging (#24358)

* Add limitation for websocket logging

PCX-13396

* Update src/content/docs/workers/observability/logs/real-time-logs.mdx

Co-authored-by: Jun Lee <[email protected]>

---------

Co-authored-by: Jun Lee <[email protected]>

Author: kodster28

src/content/docs/workers/observability/logs/real-time-logs.mdx

@@ -83,12 +83,11 @@ You can filter real-time logs in the dashboard or using [`wrangler tail`](/worke
 
 :::
 
-Note that:
-
 - Real-time logs does not store Workers Logs. To store logs, use [Workers Logs](/workers/observability/logs/workers-logs).
 - If your Worker has a high volume of traffic, the real-time logs might enter sampling mode. This will cause some of your messages to be dropped and a warning to appear in your logs.
 - Logs from any [Durable Objects](/durable-objects/) your Worker is using will show up in the dashboard.
 - A maximum of 10 clients can view a Worker's logs at one time. This can be a combination of either dashboard sessions or `wrangler tail` calls.
+- When using `wrangler tail` with [WebSocket event handlers](/workers/runtime-apis/websockets/), any `console.log` statements within those handlers are hidden until the WebSocket client closes the connection. Once the `close` is received, all messages are flushed, printing everything to the terminal at once.
 
 ## Persist logs