{"version":"2.1.285","anchor":"monitor-websocket-compliance-denial-message-reworded","canonical_anchor":"monitor-websocket-compliance-denial-message-reworded","heading":"Monitor's blocked-connection message has new punctuation","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/monitor-websocket-compliance-denial-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Monitor's blocked-connection message has new punctuation\n\nThe message when Monitor is blocked from opening a live connection for compliance reasons now uses a full stop instead of a colon\n\n**What**\n\nWhen Monitor is blocked for compliance reasons from opening a WebSocket, which is a type of live network connection, it now shows \"Monitor cannot open a WebSocket.\" followed by the details. The colon has become a full stop, and there is no full stop after the details anymore.\n\n**Why**\n\nOnly the wording changed. Nothing changes in how the message behaves.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}