Small fix

bjqian · web-flow · commit 1326401c4988 · 2024-07-17T14:38:41.000+08:00
diff --git a/articles/azure-signalr/signalr-howto-configure-application-firewall.md b/articles/azure-signalr/signalr-howto-configure-application-firewall.md
@@ -51,7 +51,7 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
    
 
 > [!WARNING]
-> * **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 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*.
+> * **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 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*.
 
 
 
diff --git a/articles/azure-web-pubsub/howto-configure-application-firewall.md b/articles/azure-web-pubsub/howto-configure-application-firewall.md
@@ -43,7 +43,7 @@ Client Connection Count Rules restrict concurrent client connections. When a cli
 
 
 > [!WARNING]
-> * **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 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*.
+> * **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 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*.
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -51,7 +51,7 @@ Client Connection Count Rules restrict concurrent client connections. When a cli`
`51`	`51`
`52`	`52`
`53`	`53`	`> [!WARNING]`
`54`		`-> * 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 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.`
	`54`	`+> * 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 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.`
`55`	`55`
`56`	`56`
`57`	`57`
Original file line number	Diff line number	Diff line change
`@@ -43,7 +43,7 @@ Client Connection Count Rules restrict concurrent client connections. When a cli`
`43`	`43`
`44`	`44`
`45`	`45`	`> [!WARNING]`
`46`		`-> * 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 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.`
	`46`	`+> * 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 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.`
`47`	`47`
`48`	`48`
`49`	`49`