Merge pull request #247823 from duongau/afdfreshness1

Front Door - Freshness 1 (August 2023)

Author: prmerger-automator[bot]

articles/frontdoor/classic-overview.md

@@ -1,12 +1,12 @@
 ---
-title: Azure Front Door (classic)
-description: This article provides an overview of Azure Front Door (classic).
+title: Azure Front Door (classic) overview
+description: This article provides an overview of the Azure Front Door (classic) service.
 services: frontdoor
 author: duongau
 ms.service: frontdoor
 ms.topic: overview
 ms.workload: infrastructure-services
-ms.date: 06/15/2022
+ms.date: 08/09/2023
 ms.author: duau
 # customer intent: As an IT admin, I want to learn about Front Door and what I can use it for. 
 ---
@@ -17,7 +17,7 @@ Azure Front Door (classic) is a global, scalable entry-point that uses the Micro
 
 :::image type="content" source="./media/front-door-overview/front-door-visual-diagram.png" alt-text="Diagram of Azure Front Door (classic) routing user traffic to endpoints.":::
 
-Front Door (classic) works at Layer 7 (HTTP/HTTPS layer) using anycast protocol with split TCP and Microsoft's global network to improve global connectivity. Based on your routing method you can ensure that Front Door (classic) will route your client requests to the fastest and most available application backend. An application backend is any Internet-facing service hosted inside or outside of Azure. Front Door (classic) provides a range of [traffic-routing methods](front-door-routing-methods.md) and [backend health monitoring options](front-door-health-probes.md) to suit different application needs and automatic failover scenarios. Similar to [Traffic Manager](../traffic-manager/traffic-manager-overview.md), Front Door (classic) is resilient to failures, including failures to an entire Azure region.
+Front Door (classic) works at Layer 7 (HTTP/HTTPS layer) using anycast protocol with split TCP and Microsoft's global network to improve global connectivity. Based on your routing method you can, ensure that Front Door (classic) routes your client requests to the fastest and most available application backend. An application backend is any Internet-facing service hosted inside or outside of Azure. Front Door (classic) provides a range of [traffic-routing methods](front-door-routing-methods.md) and [backend health monitoring options](front-door-health-probes.md) to suit different application needs and automatic failover scenarios. Similar to [Traffic Manager](../traffic-manager/traffic-manager-overview.md), Front Door (classic) is resilient to failures, including failures to an entire Azure region.
 
 >[!NOTE]
 > Azure provides a suite of fully managed load-balancing solutions for your scenarios. 
@@ -64,5 +64,6 @@ For pricing information, see [Front Door Pricing](https://azure.microsoft.com/pr
 Subscribe to the RSS feed and view the latest Azure Front Door feature updates on the [Azure Updates](https://azure.microsoft.com/updates/?category=networking&query=Azure%20Front%20Door) page.
 
 ## Next steps
+
 - Learn how to [create a Front Door (classic)](quickstart-create-front-door.md).
-- Learn [how Front Door (classic) works](front-door-routing-architecture.md?pivots=front-door-classic).
+- Learn about [how Front Door (classic) works](front-door-routing-architecture.md?pivots=front-door-classic).

articles/frontdoor/endpoint.md

@@ -1,18 +1,19 @@
 ---
-title: 'Endpoints in Azure Front Door'
+title: Endpoints in Azure Front Door
+TitleSuffix: Azure Front Door
 description: Learn about endpoints when using Azure Front Door.
 services: frontdoor
-author: johndowns
+author: duongau
 ms.service: frontdoor
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 06/22/2022
-ms.author: jodowns
+ms.date: 08/09/2023
+ms.author: duau
 ---
 
 # Endpoints in Azure Front Door
 
-In Azure Front Door Standard/Premium, an *endpoint* is a logical grouping of one or more routes that are associated with domain names. Each endpoint is [assigned a domain name](#endpoint-domain-names) by Front Door, and you can associate your own custom domains by using routes.
+In Azure Front Door, an *endpoint* is a logical grouping of one or more routes that are associated with domain names. Each endpoint is [assigned a domain name](#endpoint-domain-names) by Front Door, and you can associate your own custom domains by using routes.
 
 ## How many endpoints should I create?
 
@@ -29,8 +30,8 @@ When you're planning the endpoints to create, consider the following factors:
 Endpoint domain names are automatically generated when you create a new endpoint. Front Door generates a unique domain name based on several components, including:
 
 - The endpoint's name.
-- A pseudorandom hash value, which is determined by Front Door. By using hash values as part of the domain name, Front Door helps to protect against [subdomain takeover](../security/fundamentals/subdomain-takeover.md) attacks.
-- The base domain name for your Front Door environment. This is generally `z01.azurefd.net`.
+- A pseudorandom hash value, which gets determined by Front Door. By using hash values as part of the domain name, Front Door helps to protect against [subdomain takeover](../security/fundamentals/subdomain-takeover.md) attacks.
+- The base domain name for your Front Door environment. Generally is `z01.azurefd.net`.
 
 For example, suppose you have created an endpoint named `myendpoint`. The endpoint domain name might be `myendpoint-mdjf2jfgjf82mnzx.z01.azurefd.net`.
 
@@ -50,8 +51,8 @@ The following table lists the allowable values for the endpoint's domain reuse b
 |--|--|
 | `TenantReuse` | This is the default value. Endpoints with the same name in the same Azure Active Directory tenant receive the same domain label. |
 | `SubscriptionReuse` | Endpoints with the same name in the same Azure subscription receive the same domain label. |
-| `ResourceGroupReuse` | Endpoints with the same name in the same resource group will receive the same domain label. |
-| `NoReuse` | Endpoints will always receive a new domain label. |
+| `ResourceGroupReuse` | Endpoints with the same name in the same resource group receives the same domain label. |
+| `NoReuse` | Endpoints always receive a new domain label. |
 
 > [!NOTE]
 > You can't modify the reuse behavior of an existing Front Door endpoint. The reuse behavior only applies to newly created endpoints.