Merge pull request #233416 from duongau/afdredirect

Azure Front Door - URL redirect - freshness review

Author: prmerger-automator[bot]

articles/frontdoor/front-door-url-redirect.md

@@ -7,14 +7,14 @@ author: duongau
 ms.service: frontdoor
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 03/09/2022
+ms.date: 04/04/2023
 ms.author: duau
 zone_pivot_groups: front-door-tiers
 ---
 
 # URL redirect
 
-Azure Front Door can redirect traffic at each of the following levels: protocol, hostname, path, query string. These functionalities can be configured for individual microservices since the redirection is path-based. This can simplify application configuration by optimizing resource usage, and supports new redirection scenarios including global and path-based redirection.
+Azure Front Door can redirect traffic at each of the following levels: protocol, hostname, path, query string. These functionalities can be configured for individual microservices since the redirection is path-based. This setup can simplify application configuration by optimizing resource usage, and supports new redirection scenarios including global and path-based redirection.
 
 ::: zone pivot="front-door-standard-premium"
 
@@ -31,18 +31,19 @@ In Azure Front Door Standard/Premium tier, you can configure URL redirect using
 ::: zone-end
 
 ## Redirection types
+
 A redirect type sets the response status code for the clients to understand the purpose of the redirect. The following types of redirection are supported:
 
-- **301 (Moved permanently)**: Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource will use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection. 
+- **301 (Moved permanently)**: Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection. 
 - **302 (Found)**: Indicates that the target resource is temporarily under a different URI. Since the redirection can change on occasion, the client should continue to use the effective request URI for future requests.
 - **307 (Temporary redirect)**: Indicates that the target resource is temporarily under a different URI. The user agent MUST NOT change the request method if it does an automatic redirection to that URI. Since the redirection can change over time, the client ought to continue using the original effective request URI for future requests.
 - **308 (Permanent redirect)**: Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource should use one of the enclosed URIs.
 
 ## Redirection protocol
-You can set the protocol that will be used for redirection. The most common use cases of the redirect feature, is to set HTTP to HTTPS redirection.
+You can set the protocol that is used for redirection. The most common use cases of the redirect feature are to set HTTP to HTTPS redirection.
 
 - **HTTPS only**: Set the protocol to HTTPS only, if you're looking to redirect the traffic from HTTP to HTTPS. Azure Front Door recommends that you should always set the redirection to HTTPS only.
-- **HTTP only**: Redirects the incoming request to HTTP. Use this value only if you want to keep your traffic HTTP that is, non-encrypted.
+- **HTTP only**: Redirects the incoming request to HTTP. Use this value only if you want to keep your traffic HTTP that is, nonencrypted.
 - **Match request**: This option keeps the protocol used by the incoming request. So, an HTTP request remains HTTP and an HTTPS request remains HTTPS post redirection.
 
 ## Destination host