Merge pull request #284434 from duongau/afdfreshness

Azure Front Door - freshness review batch 1 - 8/12

Author: denrea

articles/frontdoor/front-door-custom-domain.md

@@ -5,7 +5,7 @@ services: frontdoor
 author: duongau
 ms.service: azure-frontdoor
 ms.topic: how-to
-ms.date: 04/04/2023
+ms.date: 08/12/2024
 ms.author: duau
 #Customer intent: As a website owner, I want to add a custom domain to my Front Door configuration so that my users can use my custom domain to access my content.
 ---
@@ -40,7 +40,7 @@ A custom domain can only be associated with one Front Door profile at a time. Ho
 
 ## Map the temporary afdverify subdomain
 
-When you map an existing domain that is in production, there are things consider. While you're registering your custom domain in the Azure portal, a brief period of downtime for the domain may occur. To avoid interruption of web traffic, map your custom domain to your Front Door default frontend host with the Azure afdverify subdomain first to create a temporary CNAME mapping. Your users can access your domain without interruption when the DNS mapping occurs.
+When you map an existing domain that is in production, there are things consider. While you're registering your custom domain in the Azure portal, a brief period of downtime for the domain might occur. To avoid interruption of web traffic, map your custom domain to your Front Door default frontend host with the Azure afdverify subdomain first to create a temporary CNAME mapping. Your users can access your domain without interruption when the DNS mapping occurs.
 
 If you're using your custom domain for the first time with no production traffic, you can directly map your custom domain to your Front Door. You can skip ahead to [Map the permanent custom domain](#map-the-permanent-custom-domain).
 
@@ -50,7 +50,7 @@ To create a CNAME record with the afdverify subdomain:
 
 2. Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name server management**. 
 
-3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names may vary):
+3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names might vary):
 
     | Source                    | Type  | Destination                     |
     |---------------------------|-------|---------------------------------|
@@ -78,7 +78,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
 
     - Type: Leave *CNAME* selected.
 
-    - Host: Enter the subdomain of your custom domain to use, including the afdverify subdomain name. For example, afdverify.www.
+    - Host: Enter the subdomain of your custom domain for use, including the afdverify subdomain name. For example, afdverify.www.
 
     - Points to: Enter the host name of your default Front Door frontend host, including the afdverify subdomain name. For example, afdverify.contoso-frontend.azurefd.net. 
 
@@ -91,7 +91,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
 
 ## Associate the custom domain with your Front Door
 
-After you've registered your custom domain, you can then add it to your Front Door.
+After you register your custom domain, you can then add it to your Front Door.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) and browse to the Front Door containing the frontend host that you want to map to a custom domain.
 
@@ -112,22 +112,22 @@ After you've registered your custom domain, you can then add it to your Front Do
 
 ## Verify the custom domain
 
-After you've completed the registration of your custom domain, verify that the custom domain references your default Front Door frontend host.
+After you complete the registration of your custom domain, verify that the custom domain references your default Front Door frontend host.
 
 In your browser, navigate to the address of the file by using the custom domain. For example, if your custom domain is robotics.contoso.com, the URL to the cached file should be similar to the following URL: http:\//robotics.contoso.com/my-public-container/my-file.jpg. Verify that the result is that same as when you access the Front Door directly at *<Front Door host>*.azurefd.net.
 
 
 ## Map the permanent custom domain
 
-If you've verified that the afdverify subdomain has been successfully mapped to your Front Door, you can then map the custom domain directly to your default Front Door frontend host.
+To proceed with mapping the custom domain directly to your default Front Door frontend host, you need to ensure that the afdverify subdomain was successfully mapped to your Front Door. Once verified, you can proceed with mapping the custom domain.
 
 To create a CNAME record for your custom domain:
 
 1. Sign in to the web site of the domain provider for your custom domain.
 
 2. Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name Server Management**. 
 
-3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names may vary):
+3. Create a CNAME record entry for your custom domain and complete the fields as shown in the following table (field names might vary):
 
     | Source          | Type  | Destination           |
     |-----------------|-------|-----------------------|
@@ -141,7 +141,7 @@ To create a CNAME record for your custom domain:
 
 4. Save your changes.
 
-5. If you're previously created a temporary afdverify subdomain CNAME record, delete it. 
+5. If you previously created a temporary afdverify subdomain CNAME record, delete it. 
 
 6. If you're using this custom domain in production for the first time, follow the steps for [Associate the custom domain with your Front Door](#associate-the-custom-domain-with-your-front-door) and [Verify the custom domain](#verify-the-custom-domain).
 
@@ -177,7 +177,7 @@ For example, the procedure for the GoDaddy domain registrar is as follows:
 
 In the preceding steps, you added a custom domain to a Front Door. If you no longer want to associate your Front Door with a custom domain, you can remove the custom domain by doing these steps:
 
-1. Go to your DNS provider, delete the CNAME record for the custom domain or update the CNAME record for the custom domain to a non Front Door endpoint.
+1. Go to your DNS provider, delete the CNAME record for the custom domain, or update the CNAME record for the custom domain to a non Front Door endpoint.
 
     > [!Important]
     > To prevent dangling DNS entries and the security risks they create, starting from April 9th 2021, Azure Front Door requires removal of the CNAME records to Front Door endpoints before the resources can be deleted. Resources include Front Door custom domains, Front Door endpoints or Azure resource groups that has Front Door custom domain(s) enabled.

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