Minor Application Gateway WAF updates

Author: johndowns

articles/web-application-firewall/ag/application-gateway-crs-rulegroups-rules.md

@@ -16,7 +16,7 @@ Application Gateway web application firewall (WAF) protects web applications fro
 
 ## Core rule sets
 
-The Application Gateway WAF comes pre-configured with CRS 3.1 by default, but you can choose to use any other supported CRS version.
+The Application Gateway WAF comes pre-configured with CRS 3.2 by default, but you can choose to use any other supported CRS version.
 
 CRS 3.2 offers a new engine and new rule sets defending against Java infections, an initial set of file upload checks, and fewer false positives compared with earlier versions of CRS. You can also [customize rules to suit your needs](application-gateway-customize-waf-rules-portal.md). Learn more about the new [Azure WAF engine](waf-engine.md).
 

articles/web-application-firewall/ag/application-gateway-waf-request-size-limits.md

@@ -34,7 +34,7 @@ For CRS 3.2 (on the WAF_v2 SKU) and newer, these limits are as follows when usin
    - 2 MB request body size limit
    - 4 GB file upload limit 
 
-Only requests with Content-Type of *multipart/form-data* are considered file uploads. The file part of the body content is evaluated against the file upload limit. For all other content types, the request body size limit applies.
+Only requests with Content-Type of *multipart/form-data* are considered for file uploads. For content to be considered as a file upload, it has to be a part of a multipart form with a *filename* header. For all other content types, the request body size limit applies.
 
 To set request size limits in the Azure portal, configure **Global parameters** in the WAF policy resource's **Policy settings** page: