Update custom-error.md

Author: jaesoni

articles/application-gateway/custom-error.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 12/19/2023
+ms.date: 01/27/2025
 ms.author: jaysoni 
 ms.custom: devx-track-azurepowershell
 ---
@@ -23,17 +23,17 @@ The custom error pages are supported for the following response codes:
 
 | Response code | Description |
 | ---------- | ---------- |
-| 400 | Bad request (In preview) |
+| 400 | Bad request |
 | 403 | Forbidden |
-| 405 | Method not allowed (In preview) |
-| 408 | Request timeout (In preview) |
-| 500 | Internal Server Error (In preview) |
+| 405 | Method not allowed |
+| 408 | Request timeout |
+| 500 | Internal Server Error |
 | 502 | Bad gateway |
-| 503 | Service unavailable (In preview) |
-| 504 | Gateway timeout (In preview) |
+| 503 | Service unavailable |
+| 504 | Gateway timeout |
 
 > [!Note]
-> - API version 2022-09-01 or later should be used to configure error pages for the new response codes (in preview).
+> - API version 2022-09-01 or later should be used to configure error pages for all available response codes.
 > - Response code 404 (Page not found) is currently unsupported.
 > - The custom error pages are displayed for response codes generated by Application Gateway. If an error originates from the backend server, it is passed along unmodified to the client.