Fix typo

Author: bjqian

articles/azure-signalr/signalr-howto-config-application-firewall.md

@@ -1,6 +1,6 @@
 ---
 title: SignalR Application Firewall (Preview)
-description: An introduction about why and how to setup Application Firewall for Azure SignalR service
+description: An introduction about why and how to set up Application Firewall for Azure SignalR service
 author: biqian
 ms.service: signalr
 ms.custom: devx-track-azurecli
@@ -42,12 +42,12 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
    #### ThrottleByJwtSignatureRule
    This rule limits the concurrent connections of the same token to prevent malicious users from reusing tokens to establish infinite connections, which can exhaust connection quota.
 
-   **Note:** It's not guaranteed by default that tokens generated by the SDK are different each time. Though each token contaisn a timestamp, this timestamp might be the same if vast tokens are generated within seconds. To avoid identical tokens, insert a random claim into the token claims.  Refer to [Configure access token](#configure-access-token).
+   **Note:** It's not guaranteed by default that tokens generated by the SDK are different each time. Though each token contains a timestamp, this timestamp might be the same if vast tokens are generated within seconds. To avoid identical tokens, insert a random claim into the token claims.  Refer to [Configure access token](#configure-access-token).
 
 
    #### ThrottleByJwtCustomClaimRule
 
-   More advancedly, connections could be grouped into different groups according to custom claim. Connections with the same claim will be aggregated to do the check.  For example, you could add a *ThrottleByJwtCustomClaimRule* to allow 5 concurrent connections for those with custom claim key "freeUser".
+   More advanced, connections could be grouped into different groups according to custom claim. Connections with the same claim will be aggregated to do the check.  For example, you could add a *ThrottleByJwtCustomClaimRule* to allow 5 concurrent connections for those with custom claim key "freeUser".
 
    **Key point**: The rule applies to all claims with a certain claim name. The connection count aggregation is on the same claim (including claim name and claim value). The *ThrottleByUserIdRule* is a special case of this rule, applying to all connections with the userIdentity claim.
 
@@ -56,11 +56,11 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
  ### Best Practice
   #### Avoid using too aggressive maxCount
 
-  Client connections may close without completing the tcp handshake. SignalR service can't detect those "half-closed" connections immediately. The connection is taken as active until the heartbeart failure. Therefore, aggressive throttling strategies might unexpectedly throttle clients. A smoother approach is to **leave some buffer** for the connection count, for example: double the *maxCount*.
+  Client connections may close without completing the tcp handshake. SignalR service can't detect those "half-closed" connections immediately. The connection is taken as active until the heartbeat failure. Therefore, aggressive throttling strategies might unexpectedly throttle clients. A smoother approach is to **leave some buffer** for the connection count, for example: double the *maxCount*.
 
 
 
-## Setup Application Firewall 
+## Set up Application Firewall 
 
 # [Portal](#tab/Portal)
 To use Application Firewall, navigate to the SignalR **Application Firewall** blade on the Azure portal and click **Add** to add a rule. 

articles/azure-web-pubsub/howto-config-application-firewall.md

@@ -1,6 +1,6 @@
 ---
 title: Web PubSub Application Firewall (Preview)
-description: An introduction about why and how to setup Application Firewall for Azure Web PubSub service
+description: An introduction about why and how to set up Application Firewall for Azure Web PubSub service
 author: biqian
 ms.service: azure-web-pubsub
 ms.custom: devx-track-azurecli
@@ -41,17 +41,17 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
    #### ThrottleByJwtSignatureRule
    This rule limits the concurrent connections of the same token to prevent malicious users from reusing tokens to establish infinite connections, which can exhaust connection quota.
 
-   **Note:** It's not guaranteed by default that tokens generated by the SDK are different each time. Though each token contaisn a timestamp, this timestamp might be the same if vast tokens are generated within seconds. To avoid identical tokens, insert a random claim into the token claims.  Refer to [Configure access token](#configure-access-token).
+   **Note:** It's not guaranteed by default that tokens generated by the SDK are different each time. Though each token contains a timestamp, this timestamp might be the same if vast tokens are generated within seconds. To avoid identical tokens, insert a random claim into the token claims.  Refer to [Configure access token](#configure-access-token).
 
 
  ### Best Practice
   #### Avoid using too aggressive maxCount
 
-  Client connections may close without completing the tcp handshake. Web PubSub service can't detect those "half-closed" connections immediately. The connection is taken as active until the heartbeart failure. Therefore, aggressive throttling strategies might unexpectedly throttle clients. A smoother approach is to **leave some buffer** for the connection count, for example: double the *maxCount*.
+  Client connections may close without completing the tcp handshake. Web PubSub service can't detect those "half-closed" connections immediately. The connection is taken as active until the heartbeat failure. Therefore, aggressive throttling strategies might unexpectedly throttle clients. A smoother approach is to **leave some buffer** for the connection count, for example: double the *maxCount*.
 
 
 
-## Setup Application Firewall 
+## Set up Application Firewall 
 
 # [Portal](#tab/Portal)
 To use Application Firewall, navigate to the Web PubSub **Application Firewall** blade on the Azure portal and click **Add** to add a rule.