Verified the article, reviewed the content, and fixed all minor editorial issues. Updated ms.date w.r.t freshness pass.

Author: Akhilesh-microsoft

articles/azure-signalr/signalr-concept-messages-and-connections.md

@@ -4,7 +4,7 @@ description: An overview of key concepts about messages and connections in Azure
 author: vicancy
 ms.service: azure-signalr-service
 ms.topic: conceptual
-ms.date: 03/23/2023
+ms.date: 09/03/2024
 ms.author: lianwei
 ---
 # Messages and connections in Azure SignalR Service
@@ -38,7 +38,7 @@ Large messages do negatively affect messaging performance. Use smaller messages
 
 ## How messages are counted for billing
 
-Messages sent into the service are inbound messages and messages sent out of the service are outbound messages.  Only outbound messages from Azure SignalR Service are counted for billing. Ping messages between clients and servers are ignored.
+Messages sent into the service are inbound messages and messages sent out of the service are outbound messages. Only outbound messages from Azure SignalR Service are counted for billing. Ping messages between clients and servers are ignored.
 
 Messages larger than 2 KB are counted as multiple messages of 2 KB each. The message count chart in the Azure portal is updated every 100 messages per hub.
 
@@ -48,7 +48,7 @@ For example, imagine you have one application server, and three clients:
 
 * When *client A* sends a 1 KB inbound message to *client B*, without going through app server, the message is a free inbound message. The message routed from service to *client B* is billed as an outbound message.
 
-* If you have three clients and one application server, when one client sends a 4-KB message for the server broadcast to all clients, the billed message count is eight: 
+* When one client sends a 4-KB message for the server broadcast to all clients, and there are three clients and one application server, the billed message count is eight: 
 
   * One message from the service to the application server.
   * Three messages from the service to the clients. Each message is counted as two 2-KB messages.
@@ -70,7 +70,7 @@ A live trace connection isn't counted as a client connection or as a server conn
 
 ASP.NET SignalR calculates server connections in a different way. It includes one default hub in addition to hubs that you define. By default, each application server needs five more initial server connections. The initial connection count for the default hub stays consistent with other hubs.
 
-The service and the application server keep syncing connection status and making adjustments to server connections to get better performance and service stability.  So you may see changes in the number of server connections in your running service.
+The service and the application server keep syncing connection status and making adjustments to server connections to get better performance and service stability. So you might see changes in the number of server connections in your running service.
 
 ## Related resources