Merge pull request #224954 from cebundy/wps-refs

[Web PubSub] review input from previous PR 223135

Author: prmerger-automator[bot]

articles/azure-web-pubsub/includes/reference-json-requests.md

@@ -3,7 +3,7 @@ author: vicancy
 ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.topic: include 
-ms.date: 08/06/2021
+ms.date: 01/24/2023
 ---
 
 ### Join groups

articles/azure-web-pubsub/includes/reference-permission.md

@@ -3,7 +3,7 @@ author: vicancy
 ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.topic: include 
-ms.date: 08/06/2021
+ms.date: 01/24/2023
 ---
 
 ## Permissions

articles/azure-web-pubsub/includes/reference-protobuf-requests.md

@@ -1,3 +1,11 @@
+---
+author: vicancy
+ms.author: lianwei
+ms.service: azure-web-pubsub
+ms.topic: include 
+ms.date: 01/24/2023
+---
+
 ### Join groups
 
 Format:
@@ -18,7 +26,7 @@ Set `leave_group_message.group` to the group name.
 
 Format:
 
-* `ackId`:  The unique identity of each request. The service sends a [ack response message](#ack-response) to notify the process result of the request. More details can be found at [AckId and Ack Response](../concept-client-protocols.md#ackid-and-ack-response)
+* `ackId`: The unique identity of each request. The service sends an [ack response message](#ack-response) to notify the process result of the request. More details can be found at [AckId and Ack Response](../concept-client-protocols.md#ackid-and-ack-response)
 
 * `dataType`:  The data format, which can be `protobuf`, `text`, or `binary` depending on the `data` in `MessageData`. The receiving clients can use `dataType` to correctly process the content.
 
@@ -129,7 +137,7 @@ There's an implicit `dataType`, which can be `protobuf`, `text`, or `binary`, de
 
 * `text`: When you set `event_message.data.text_data`, the implicit `dataType` is `text`. The `text_data` value should be a string. The event handler receives a UTF-8-encoded string.
 
-* `binary`: When you set `event_message.data.binary_data`, the implicit `dataType` is `binary`. The `binary_data` value should be a byte array. The event handler receives the simple WebSocket binary frame.
+* `binary`: When you set `event_message.data.binary_data`, the implicit `dataType` is `binary`. The `binary_data` value should be a byte array. The event handler receives the raw binary frame.
 
 #### Case 1: Send an event with text data
 

articles/azure-web-pubsub/reference-json-reliable-webpubsub-subprotocol.md

@@ -10,9 +10,9 @@ ms.date: 01/09/2023
 
 # Azure Web PubSub Reliable JSON WebSocket subprotocol
 
-The JSON WebSocket subprotocol, `json.reliable.webpubsub.azure.v1`, enables the highly reliable exchange of publish/subscribe messages directly between clients even during network issues.
+The JSON WebSocket subprotocol, `json.reliable.webpubsub.azure.v1`, enables the highly reliable exchange of publish/subscribe messages directly between clients through the service without a round trip to the upstream server.
 
-This document describes the subprotocol json.reliable.webpubsub.azure.v1.
+This document describes the subprotocol `json.reliable.webpubsub.azure.v1`.
 
 > [!NOTE]
 > Reliable protocols are still in preview. Some changes are expected in the future.
@@ -23,9 +23,10 @@ To overcome intermittent network issues and maintain reliable message delivery,
 
 A *Reliable PubSub WebSocket client* can:
 
-* reconnect a dropped connection.
+* recover a connection from intermittent network issues.
 * recover from message loss.
 * join a group using [join requests](#join-groups).
+* leave a group using [leave requests](#leave-groups).
 * publish messages directly to a group using [publish requests](#publish-messages).
 * route messages directly to upstream event handlers using [event requests](#send-custom-events).
 

articles/azure-web-pubsub/reference-json-webpubsub-subprotocol.md

@@ -10,18 +10,18 @@ ms.date: 01/09/2023
 
 # Azure Web PubSub supported JSON WebSocket subprotocol
 
-The JSON WebSocket subprotocol, `json.webpubsub.azure.v1`, enables the exchange of publish/subscribe messages directly between clients.  A WebSocket connection using the `json.webpubsub.azure.v1` subprotocol is called a *PubSub WebSocket client*.
+The JSON WebSocket subprotocol, `json.webpubsub.azure.v1`, enables the exchange of publish/subscribe messages between clients through the service without a round trip to the upstream server.  A WebSocket connection using the `json.webpubsub.azure.v1` subprotocol is called a *PubSub WebSocket client*.
 
 
 ## Overview
 
-In a simple WebSocket client, a *server* role is required to handle events from clients. A simple WebSocket connection triggers a `message` event when it sends messages and relies on the server-side to process messages and do other operations. 
+A simple WebSocket connection triggers a `message` event when it sends messages and relies on the server-side to process messages and do other operations. 
 
 With the `json.webpubsub.azure.v1` subprotocol, you can create *PubSub WebSocket clients* that can:
 
 * join a group using [join requests](#join-groups).
 * publish messages directly to a group using [publish requests](#publish-messages).
-* route messages directly to upstream event handlers using [event requests](#send-custom-events).
+* route messages to different upstream event handlers using [event requests](#send-custom-events).
 
 For example, you can create a *PubSub WebSocket client* with the following JavaScript code:
 
@@ -44,7 +44,7 @@ Message types received by the client can be:
 
 * ack - The response to a request containing an `ackId`.
 * message - Messages from the group or server.
-* system - Responses from the Web PubSub service to system related client requests.
+* system - Messages from the Web PubSub service.
 
 ### Ack response
 
@@ -142,11 +142,11 @@ If the REST API is sending a string `Hello World` using `application/json` conte
 
 ### System response
 
-The Web PubSub service sends system related responses to client requests. 
+The Web PubSub service sends system-related messages to clients. 
 
 #### Connected
 
-The response to the client connect request:
+The message sent to the client when the client successfully connects:
 
 ```json
 {
@@ -159,7 +159,7 @@ The response to the client connect request:
 
 #### Disconnected
 
-The response when the server closes the connection, or when the service declines the client.
+The message sent to the client when the server closes the connection, or when the service declines the client.
 
 ```json
 {