Fix Note

Author: bjqian

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

@@ -47,7 +47,7 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
 
    #### ThrottleByJwtCustomClaimRule
 
-   More advanced, connections could be grouped into different groups according to custom claim. Connections with the same claim are aggregated to do the check. For example, you could add a *ThrottleByJwtCustomClaimRule* to allow 5 concurrent connections with custom claim key "freeUser".
+   More advanced, connections could be grouped into different groups according to custom claim. Connections with the same claim are aggregated to do the check. For example, you could add a **ThrottleByJwtCustomClaimRule** to allow 5 concurrent connections with custom claim name *freeUser*.
 
    > [!NOTE]
    > * 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.

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

@@ -33,13 +33,15 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
    #### ThrottleByUserIdRule
    This rule limits the concurrent connections of a user. For example, if a user opens multiple browser tabs or logs in using different devices, you can use this rule to restrict the number of concurrent connections for that user.
 
-   **Note:** The UserId must exist in the access token for this rule to work. Refer to [Configure access token](#configure-access-token).
+  > [!NOTE]
+  > * The UserId must exist in the access token for this rule to work. Refer to [Configure access token](#configure-access-token).
 
 
    #### 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 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).
+  > [!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).
 
 
 > [!WARNING]