Merge pull request #198088 from JackStromberg/patch-67

Removing storage account reference

Author: PRMerger7

articles/application-gateway/custom-error.md

@@ -33,13 +33,13 @@ To create a custom error page, you must have:
 
 - an HTTP response status code.
 - corresponding location for the error page. 
-- error page should be internet accessible.
+- error page should be internet accessible and return 200 response.
 - error page should be in \*.htm or \*.html extension type.
 - error page size must be less than 1 MB.
 
 You may reference either internal or external images/CSS for this HTML file. For externally referenced resources, use absolute URLs that are publicly accessible. Be aware of the HTML file size when using internal images (Base64-encoded inline image) or CSS. Relative links with files in the same location are currently not supported.
 
-After you specify an error page, the application gateway downloads it from the storage blob location and saves it to the local application gateway cache. Then, that HTML page is served by the application gateway, whereas the externally referenced resources are fetched directly by the client. To modify an existing custom error page, you must point to a different blob location in the application gateway configuration. The application gateway doesn't periodically check the blob location to fetch new versions.
+After you specify an error page, the application gateway downloads it from the defined location and saves it to the local application gateway cache. Then, that HTML page is served by the application gateway, whereas the externally referenced resources are fetched directly by the client. To modify an existing custom error page, you must point to a different blob location in the application gateway configuration. The application gateway doesn't periodically check the blob location to fetch new versions.
 
 ## Portal configuration