freshness review - 8/12

Author: duongau

articles/frontdoor/front-door-routing-architecture.md

@@ -6,7 +6,7 @@ services: front-door
 author: duongau
 ms.service: azure-frontdoor
 ms.topic: conceptual
-ms.date: 04/04/2023
+ms.date: 08/12/2024
 ms.author: duau
 zone_pivot_groups: front-door-tiers
 ---
@@ -55,23 +55,23 @@ When Front Door receives an HTTP request, it uses the request's `Host` header to
 
 ::: zone-end
 
-The client and server perform a TLS handshake using the TLS certificate you've configured for your custom domain name, or by using the Front Door certificate when the `Host` header ends with `*.azurefd.net`.
+The client and server perform a TLS handshake using the TLS certificate you configured for your custom domain name, or by using the Front Door certificate when the `Host` header ends with `*.azurefd.net`.
 
 ## Evaluate WAF rules
 
 ::: zone pivot="front-door-standard-premium"
 
-If your domain has enabled the Web Application Firewall, WAF rules are evaluated.
+If your domain has Web Application Firewall enabled, WAF rules are evaluated.
 
 ::: zone-end
 
 ::: zone pivot="front-door-classic"
 
-If your frontend has enabled the Web Application Firewall, WAF rules are evaluated.
+If your frontend has Web Application Firewall enabled, WAF rules are evaluated.
 
 ::: zone-end
 
-If a rule has been violated, Front Door returns an error to the client and the request processing stops.
+If a rule gets violated, Front Door returns an error to the client and the request processing stops.
 
 ::: zone pivot="front-door-standard-premium"
 
@@ -97,15 +97,15 @@ The route specifies the [backend pool](front-door-backend-pool.md) that the requ
 
 ## Evaluate rule sets
 
-If you have defined [rule sets](front-door-rules-engine.md) for the route, they're executed in the order they're configured. [Rule sets can override the origin group](front-door-rules-engine-actions.md#RouteConfigurationOverride) specified in a route. Rule sets can also trigger a redirection response to the request instead of forwarding it to an origin.
+If you define [rule sets](front-door-rules-engine.md) for the route, they get process in the order configured. [Rule sets can override the origin group](front-door-rules-engine-actions.md#RouteConfigurationOverride) specified in a route. Rule sets can also trigger a redirection response to the request instead of forwarding it to an origin.
 
 ::: zone-end
 
 ::: zone pivot="front-door-classic"
 
 ## Evaluate rules engines
 
-If you have defined [rules engines](front-door-rules-engine.md) for the route, they're executed in the order they're configured. [Rules engines can override the backend pool](front-door-rules-engine-actions.md#route-configuration-overrides) specified in a routing rule. Rules engines can also trigger a redirection response to the request instead of forwarding it to a backend.
+If you define [rules engines](front-door-rules-engine.md) for the route, they get process in the order configured. [Rules engines can override the backend pool](front-door-rules-engine-actions.md#route-configuration-overrides) specified in a routing rule. Rules engines can also trigger a redirection response to the request instead of forwarding it to a backend.
 
 ::: zone-end
 
@@ -133,11 +133,11 @@ If caching is disabled or no response is available, the request is forwarded to
 
 Front Door selects an origin to use within the origin group. Origin selection is based on several factors, including:
 
-- The health of each origin, which Front Door monitors by using [health probes](front-door-health-probes.md).
-- The [routing method](front-door-routing-methods.md) for your origin group.
-- Whether you have enabled [session affinity](front-door-routing-methods.md#affinity)
+- Health of each origin, which Front Door monitors by using [health probes](front-door-health-probes.md).
+- [Routing method](front-door-routing-methods.md) for your origin group.
+- If you enable [session affinity](front-door-routing-methods.md#affinity)
 
-## Forward request to origin
+## Forward the request to the origin
 
 Finally, the request is forwarded to the origin.
 
@@ -149,11 +149,11 @@ Finally, the request is forwarded to the origin.
 
 Front Door selects a backend to use within the backend pool. Backend selection is based on several factors, including:
 
-- The health of each backend, which Front Door monitors by using [health probes](front-door-health-probes.md).
-- The [routing method](front-door-routing-methods.md) for your backend pool.
-- Whether you have enabled [session affinity](front-door-routing-methods.md#affinity)
+- Health of each backend, which Front Door monitors by using [health probes](front-door-health-probes.md).
+- [Routing method](front-door-routing-methods.md) for your backend pool.
+- If you have enable [session affinity](front-door-routing-methods.md#affinity)
 
-## Forward request to backend
+## Forward the request to the backend
 
 Finally, the request is forwarded to the backend.
 
@@ -163,12 +163,12 @@ Finally, the request is forwarded to the backend.
 
 ::: zone pivot="front-door-standard-premium"
 
-- Learn how to [create a Front Door profile](standard-premium/create-front-door-portal.md).
+- Learn how to [create an Azure Front Door profile](standard-premium/create-front-door-portal.md).
 
 ::: zone-end
 
 ::: zone pivot="front-door-classic"
 
-- Learn how to [create a Front Door profile](quickstart-create-front-door.md).
+- Learn how to [create an Azure Front Door (classic) profile](quickstart-create-front-door.md).
 
 ::: zone-end