acrolinx and author update

Author: greg-lindsay

includes/application-gateway-limits.md

@@ -1,9 +1,9 @@
 ---
-author: vhorne
+author: greg-lindsay
 ms.service: application-gateway
 ms.topic: include
-ms.date: 07/25/2022
-ms.author: victorh
+ms.date: 10/19/2022
+ms.author: greglin
 ---
 | Resource | Limit | Note |
 | --- | --- | --- |
@@ -12,7 +12,7 @@ ms.author: victorh
 | Frontend ports |100<sup>1</sup> | |
 | Backend address pools |100 | |
 | Backend targets per pool |1,200 | |
-| HTTP listeners |200<sup>1</sup> |Limited to 100 active listeners that are routing traffic. Active listeners = total number of listeners - listeners not active.<br>If a default configuration inside a routing rule is set to route traffic (for example, it has a listener, a backend pool, and HTTP settings) then that also counts as a listener. See [Frequently asked questions about Application Gateway](../articles/application-gateway/application-gateway-faq.yml#what-is-considered-an-active-listener-versus-inactive-listener) for additional details.|
+| HTTP listeners |200<sup>1</sup> |Limited to 100 active listeners that are routing traffic. Active listeners = total number of listeners - listeners not active.<br>If a default configuration inside a routing rule is set to route traffic (for example, it has a listener, a backend pool, and HTTP settings) then that also counts as a listener. For more information, see [Frequently asked questions about Application Gateway](../articles/application-gateway/application-gateway-faq.yml#what-is-considered-an-active-listener-versus-inactive-listener).|
 | HTTP load-balancing rules |400<sup>1</sup> | |
 | Backend HTTP settings |100<sup>1</sup> | |
 | Instances per gateway |V1 SKU - 32<br>V2 SKU - 125 | |
@@ -41,11 +41,11 @@ ms.author: victorh
 | Maximum Private Link Configurations| 2 | 1 for public IP, 1 for private IP |
 | Maximum Private Link IP Configurations| 8 | |
 | Maximum WAF custom rules|100||
-|WAF IP address ranges per match condition|540<br>600 - with CRS 3.2 or newer|
+| WAF IP address ranges per match condition|540<br>600 - with CRS 3.2 or newer|
 | Maximum WAF exclusions per Application Gateway|40<br>200 - with CRS 3.2 or newer|
 
-<sup>1</sup> In case of WAF-enabled SKUs, you must limit the number of resources to 40.
+<sup>1</sup> For WAF-enabled SKUs, you must limit the number of resources to 40.
 
 <sup>2</sup> Limit is per Application Gateway instance not per Application Gateway resource.
 
-<sup>3</sup> Must define the value via WAF Policy for Application Gateway
+<sup>3</sup> Must define the value via WAF Policy for Application Gateway.