Remove html and fix link.

Author: grminch

articles/azure-web-pubsub/concept-billing-model.md

@@ -26,9 +26,9 @@ The unit is an abstract concept of the capability of Azure Web PubSub service. E
 
 The units are counted based on the number of units and the usage time (seconds) of the units, and billed daily. 
 
-For example, imagine you have one Azure Web PubSub service instance with 5 units, scale up to 10 units from 10:00 AM to 16:00 PM and then scale back to 5 units after 16:00 PM. It turns out 5 units for 18 hours and 10 units for 6 hours in a specific day.
+For example, imagine you have one Azure Web PubSub service instance with five units, scale up to 10 units from 10:00 AM to 16:00 PM and then scale back to five units after 16:00 PM. Total usage for the day is 5 units for 18 hours and 10 units for 6 hours.
 
-> Usage of the units for billing = (5 units * 18 hours + 10 units * 6 hours) / 24 hours = 6.25 Unit/Day
+> Total units are used for billing = (5 units * 18 hours + 10 units * 6 hours) / 24 hours = 6.25 Unit/Day
 
 ## How outbound traffic is counted with billing model
 
@@ -38,7 +38,7 @@ The outbound traffic is the messages sent out of Azure Web PubSub service. You c
 
 - The messages broadcasted from service to receivers.
 - The messages sent from the service to the upstream webhooks.
-- The resource logs with [live trace tool](./howto-troubleshoot-resource-logs.md#capture-resource-logs-with-live-trace-tool). 
+- The resource logs with [live trace tool](./howto-troubleshoot-resource-logs.md#capture-resource-logs-by-using-the-live-trace-tool). 
 
 The inbound traffic is the messages sent to the Azure Web PubSub service. 
 
@@ -51,21 +51,21 @@ The message count for billing purpose is an abstract concept and defined as the
 
 ### How traffic is counted with billing model
 
-For billing, only the outbound traffic is counted. 
+Only the outbound traffic is counted for billing.
 
-For example, imagine you have an application with Azure Web PubSub service and Azure Functions. One user broadcast 4 KB data to 10 connections in a group. It turns out 4 KB for upstream from service to function and 40 KB from service broadcast to 10 connections.
+For example, imagine you have an application with Azure Web PubSub service and Azure Functions. One user broadcast 4 KB of data to 10 connections in a group. Total data is 4 KB for upstream from service to function and 40 KB from the service broadcast to 10 connections * 4 KB each.
 
 > Outbound traffic for billing = 4 KB (upstream traffic) + 4 KB * 10 (service broadcasting to clients traffic) = 44 KB
 
 > Equivalent message count = 44 KB / 2 KB = 22
 
-The Azure Web PubSub service also offers daily free quota of outbound traffic (message count) based on the usage of the units. The outbound traffic (message count) beyond the free quota is the additional outbound traffic (additional messages). Taking standard tier as example, the free quota is 2,000,000-KB outbound traffic (1,000,000 messages) per unit/day.
+The Azure Web PubSub service also offers a daily free quota of outbound traffic (message count) based on the usage of the units. The outbound traffic (message count) beyond the free quota is the extra outbound traffic not included in the base quota. Consider standard tier as example, the free quota is 2,000,000-KB outbound traffic (1,000,000 messages) per unit/day.
 
-Using the previous unit usage example, the application use 6.25 units per day that ensures the daily free quota as 12,500,000-KB outbound traffic (6.25 million messages). Imaging the daily outbound traffic is 30,000,000 KB (15 million messages), the additional messages will be 17,500,000-KB outbound traffic (8.75 million messages). As a result, you'll be billed with 6.25 standard units and 8.75 additional message units for the day.
+In the previous unit usage example, the application uses 6.25 units per day that ensures the daily free quota as 12,500,000-KB outbound traffic (6.25 million messages). Assuming the daily outbound traffic is 30,000,000 KB (15 million messages), the extra messages will be 17,500,000-KB outbound traffic (8.75 million messages). As a result, you'll be billed with 6.25 standard units and 8.75 additional message units for the day.
 
 ## Pricing 
 
-The Azure Web PubSub service offers multiple tiers with different pricing. Once you understand how the number of units and size of outbound traffic (message count) are counted with billing model, you could learn more pricing details from [Azure Web PubSub service pricing](https://azure.microsoft.com/pricing/details/web-pubsub).
+The Azure Web PubSub service offers multiple tiers with different pricing. For more information about Web PubSub pricing, see [Azure Web PubSub service pricing](https://azure.microsoft.com/pricing/details/web-pubsub).
 
 
 

articles/azure-web-pubsub/howto-troubleshoot-resource-logs.md

@@ -12,14 +12,14 @@ ms.date: 07/21/2022
 
 This how-to guide provides an overview of Azure Web PubSub resource logs and some tips for using the logs to troubleshoot certain problems.  Logs can be used for issue identification, connection tracking, message tracing, HTTP request tracing, and analysis.
 
-## <a id="whats-are-resource-logs">What are resource logs?</a> 
+## What are resource logs? 
 
 There are three types of resource logs: *Connectivity*, *Messaging*, and *HTTP requests*.
 - **Connectivity** logs provide detailed information for Azure Web PubSub hub connections. For example, basic information (user ID, connection ID, and so on) and event information (connect, disconnect, and so on).
 - **Messaging** logs provide tracing information for the Azure Web PubSub hub messages received and sent via Azure Web PubSub service. For example, tracing ID and message type of the message.
 - **HTTP requests** logs provide tracing information for HTTP requests to the Azure Web PubSub service. For example, HTTP method and status code. Typically the HTTP request is recorded when it arrives at or leave from service.
 
-## <a id="capture-resource-logs-with-live-trace-tool">Capture resource logs by using the live trace tool</a>
+## Capture resource logs by using the live trace tool
 
 The Azure Web PubSub service live trace tool has ability to collect resource logs in real time, which is helpful for troubleshooting problems in your development environment. The live trace tool can capture connectivity logs, messaging logs, and HTTP request logs.