Fix scores

vicancy · vicancy · commit f06aabe14b91 · 2023-04-11T13:55:10.000+08:00
diff --git a/articles/azure-web-pubsub/quickstarts-event-notifications-from-clients.md b/articles/azure-web-pubsub/quickstarts-event-notifications-from-clients.md
@@ -5,18 +5,18 @@ author: vicancy
 ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.topic: quickstart
-ms.date: 03/13/2023
+ms.date: 04/12/2023
 ---
 
 # Event notifications from clients
 
 ## Intro
 
 In the first three articles of "quickstarts", we learned two useful communication patterns using Web PubSub for real-time messaging at scale ***(million+)***.
-- **Pub/Sub** among clients which frees your application server from the complexity of managing persistent connections
+- **Pub/Sub** among clients that free your application server from the complexity of managing persistent connections
 - **Push messages** to clients from your application server as soon as new data is available
 
-In this quickstart guide, we will learn about the event system of Web PubSub so that your application server can react to events like when 
+In this quickstart guide, we learn about the event system of Web PubSub so that your application server can react to events like when 
 > [!div class="checklist"]
 > * a client is `connected`
 > * a client sends a `message`, which requires further processing 
@@ -34,7 +34,7 @@ In this quickstart guide, we will learn about the event system of Web PubSub so
 ---
 
 ## Create the application
-Web PubSub is a standalone service to your application server. While your application retains its role as a traditional HTTP server, Web PubSub takes care of the real-time message passing between your application server and the clients. We will first create the client program and then the server program.
+Web PubSub is a standalone service to your application server. While your application retains its role as a traditional HTTP server, Web PubSub takes care of the real-time message passing between your application server and the clients. We first create the client program and then the server program.
 
 ### Create the client
 # [JavaScript](#tab/javascript)
@@ -126,12 +126,12 @@ app.use(handler.getMiddleware());
 app.listen(8080, () => console.log('Server started, listening on port 8080'));
 ```
 
-As configured in the code above, when a client connects with your Web PubSub resource, Web PubSub invokes the Webhook served by your application server at the path `/eventhandler`. Here, we simply print out the `userId` to the console when a user is connected.
+As configured in the code above, when a client connects with your Web PubSub resource, Web PubSub invokes the Webhook served by your application server at the path `/eventhandler`. Here, we simply print the `userId` to the console when a user is connected.
 
 ---
 
 ## Expose localhost
-If your run the program on your computer, it is running on `localhost` at port `8080`. For our purposes, it means your local express app cannot be reached on the internet. Consequently, Web PubSub can not invoke the Webhook served at the path `/eventhandler`.
+If your run the program on your computer, it's running on `localhost` at port `8080`. For our purposes, it means your local express app can't be reached on the internet. So, Web PubSub can't invoke the Webhook served at the path `/eventhandler`.
 
 What we need is to expose localhost to be accessible on the internet. There are several tools available for this. 
 > [!div class="checklist"]
@@ -148,18 +148,18 @@ You can download ngrok from https://ngrok.com/download
 ngrok http 8080
 ```
 #### 3. Make note of the generated URL 
-"ngrok" will output a URL like this `https://<domain-name>.ngrok.io`. Now your port `8080` is accessible on the internet.
+"ngrok" outputs a URL like this `https://<domain-name>.ngrok.io`. Now your port `8080` is accessible on the internet.
 
 ---
 
 ## Set event handler on your Web PubSub resource
-Now, we need to let your Web PubSub resource know about this Webhook URL. You can set the event handlers either from Azure Portal or Azure CLI. 
+Now, we need to let your Web PubSub resource know about this Webhook URL. You can set the event handlers either from Azure portal or Azure CLI. 
 
 # [Azure portal](#tab/portal)
-1. Select **"Settings"** from the menu and click **"Add"**
+1. Select **"Settings"** from the menu and select **"Add"**
 :::image type="content" source="media/howto-develop-eventhandler/configure-event-handler_menu.png" alt-text="Screenshot of Azure Web PubSub Configure Event Handler - menu":::
 
-1. Enter a hub name. For our purposes, enter "**myHub1**" and click "**Add**"
+1. Enter a hub name. For our purposes, enter "**myHub1**" and select "**Add**"
 
 1. In the event handler page, configure the following fields
 :::image type="content" source="media/howto-develop-eventhandler/configure-event-handler_details.png" alt-text="Screenshot of Azure Web PubSub Configure Event Handler - details":::
@@ -238,7 +238,7 @@ let handler = new WebPubSubEventHandler(HUB_NAME, {
 You should see both the  `userId` and the `Received message: sending custom event!` printed to the console.
 
 ## Summary
-This tutorial provides you with a basic idea of how the event system works in Web PubSub. In real-world applications, the event system can help you implement additional logic to process system and user generated events. 
+This tutorial provides you with a basic idea of how the event system works in Web PubSub. In real-world applications, the event system can help you implement more logic to process system and user generated events. 
 
 ## Next steps
 > [!div class="nextstepaction"]
diff --git a/articles/azure-web-pubsub/quickstarts-pubsub-among-clients.md b/articles/azure-web-pubsub/quickstarts-pubsub-among-clients.md
@@ -1,11 +1,11 @@
 ---
 title: PubSub among clients
-description: A quickstarts guide that shows to how to subsribe to messages in a group and send messages to a group without the involvement of a typical application server
+description: A quickstarts guide that shows to how to subscribe to messages in a group and send messages to a group without the involvement of a typical application server
 author: kevinguo-ed
 ms.author: kevinguo
 ms.service: azure-web-pubsub
 ms.topic: quickstart
-ms.date: 03/13/2023
+ms.date: 04/12/2023
 ms.custom: mode-api, devx-track-azurecli 
 ms.devlang: azurecli
 ---
@@ -136,7 +136,7 @@ await client.JoinGroupAsync("group1");
 ---
 
 ## Publish a message to a group
-In the previous step, we've set up everything needed to receive messages from `group1`, now we will send messages to that group. 
+In the previous step, we've set up everything needed to receive messages from `group1`, now we send messages to that group. 
 
 # [JavaScript](#tab/javascript)
 
@@ -164,6 +164,6 @@ By using the client SDK, you now know how to
 > * **subscribe** to group messages
 > * **publish** messages to groups
 
-Next, you will learn how to **push messages in real-time** from an application server to your clients.
+Next, you learn how to **push messages in real-time** from an application server to your clients.
 > [!div class="nextstepaction"]
 > [Push message from application server](quickstarts-push-messages-from-server.md)
diff --git a/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md b/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md
@@ -5,7 +5,7 @@ author: vicancy
 ms.author: lianwei
 ms.service: azure-web-pubsub
 ms.topic: quickstart
-ms.date: 03/14/2023
+ms.date: 04/12/2023
 ---
 
 # Push messages from server
@@ -68,7 +68,7 @@ This URL follows a pattern of `wss://<service_name>.webpubsub.azure.com/client/h
 
 ![The diagram shows how to get client access url.](./media/quickstart-live-demo/push_messages_from_server.png)
 
-As shown in the diagram above, the client will join the hub named `myHub1`.
+As shown in the diagram above, the client joins the hub named `myHub1`.
 
 In the `subscriber` project folder, create a file named `subscribe.js` with the following code
 
@@ -93,7 +93,7 @@ await client.start();
 ```bash
 node subscribe.js
 ```
-Now this client establishes a connection with your Web PubSub resource and and is ready to receive messages pushed from your application server.
+Now this client establishes a connection with your Web PubSub resource and is ready to receive messages pushed from your application server.
 
 
 # [C#](#tab/csharp)
@@ -132,7 +132,7 @@ await client.StartAsync();
 ```bash
 dotnet run "myHub1"
 ```
-Now this client establishes a connection with your Web PubSub resource and and is ready to receive messages pushed from your application server.
+Now this client establishes a connection with your Web PubSub resource and is ready to receive messages pushed from your application server.
 
 # [Python](#tab/python)
 
@@ -346,13 +346,13 @@ let server = new WebPubSubServiceClient(process.env.WebPubSubConnectionString, h
 server.sendToAll(process.argv[2], { contentType: "text/plain" });
 ```
 
-Note that the `server.sendToAll()` call sends a message to all connected clients in a hub.
+The `server.sendToAll()` call sends a message to all connected clients in a hub.
 
 #### Get the connection string 
 > [!Important]
 > A connection string includes authorization information required for your application to access Web PubSub service. The access key inside the connection string is similar to a root password for your service. 
 
-For this quickstart guide, we will get it from Azure portal as shown below.
+For this quickstart guide, we'll get it from Azure portal as shown below.
 ![A diagram shows how to get client access url.](./media/quickstart-live-demo/get_connection_string.png)
 
 #### Run the server program
@@ -369,12 +369,12 @@ node publish.js "Hello World"
 
 :::image type="content" source="media/quickstart-live-demo/push_messages_from_server.gif" alt-text="GIF of demonstrating an app server pushing data to connected client":::
 
-Try running the same "subscribe" program in multiple command shells to simluate more than clients. As soon as the "publish" program is run, you should see messages being delivered in real-time to all these clients.   
+Try running the same "subscribe" program in multiple command shells to stimulate more than clients. As soon as the "publish" program is run, you should see messages being delivered in real-time to all these clients.   
 
 
 # [C#](#tab/csharp)
 
-#### Ceate a project directory named `publisher` and install required dependencies:
+#### Create a project directory named `publisher` and install required dependencies:
 
 ```bash
 mkdir publisher
@@ -548,17 +548,17 @@ Message received: Hello World
 ---
 
 ## Summary
-This quickstart demonstrates how easy it is to push messages from an application server to all connected clients in a hub. Additionally, Web PubSub allows you to push messages to 
+This quickstart demonstrates how easy it's to push messages from an application server to all connected clients in a hub. Additionally, Web PubSub allows you to push messages to 
 
 > [!div class="checklist"]
 > * a subset of the clients in a **hub**
 > * a particular group in a **hub**
 > * a subset of clients in a **group**
 
-These APIs enable a wealth of use cases, allowing developers to focus on unique business logic while be assured that Web PubSub offers **low latency (<100ms)**, **high availability** and **massive scale (million+ simultanenous connections)**.  
+These APIs enable a wealth of use cases, allowing developers to focus on unique business logic while be assured that Web PubSub offers **low latency (<100ms)**, **high availability** and **massive scale (million+ simultaneous connections)**.  
 
 ## Next steps
-In the next step, we will explore how to work with the event system of Web PubSub, necessary to build complete web applications.
+In the next step, we'll explore how to work with the event system of Web PubSub, necessary to build complete web applications.
 
 > [!div class="nextstepaction"]
 > [Event notifications from clients](./quickstarts-event-notifications-from-clients.md)
