rewrite steps and freshness

Author: duongau

articles/frontdoor/quickstart-create-front-door.md

@@ -1,6 +1,6 @@
 ---
-title: 'Quickstart: Set up high availability with Azure Front Door Service - Azure portal'
-description: This quickstart shows how to use Azure Front Door Service for your highly available and high-performance global web application by using the Azure portal.
+title: 'Quickstart: How to use Azure Front Door Service to enable high availability - Azure portal'
+description: In this quickstart, you learn how to use the Azure portal to set up Azure Front Door Service for your web application that requires high availability and high performance across the globe.
 services: front-door
 author: duongau
 ms.author: duau
@@ -10,12 +10,12 @@ ms.topic: quickstart
 ms.service: frontdoor
 ms.workload: infrastructure-services
 ms.custom: template-tutorial, mode-ui, engagement-fy23
-#Customer intent: As an IT admin, I want to direct user traffic to ensure high availability of web applications.
+#Customer intent: As an IT admin, I want to manage user traffic to ensure high availability of web applications.
 ---
 
 # Quickstart: Create a Front Door for a highly available global web application
 
-This quickstart shows you how to use the Azure portal to set up high availability for a web application with Azure Front Door. You create a Front Door configuration that distributes traffic across two instances of a web application running in different Azure regions. The configuration uses equal weighted and same priority backends, which means that Azure Front Door directs traffic to the closest available site that hosts the application. Azure Front Door also monitors the health of the web application and perform automatic failover to the next nearest site if the closest site is down.
+This quickstart shows you how to use the Azure portal to set up high availability for a web application with Azure Front Door. You create a Front Door configuration that distributes traffic across two instances of a web application running in different Azure regions. The configuration uses equal weighted and same priority backends, which means that Azure Front Door directs traffic to the closest available site that hosts the application. Azure Front Door also monitors the health of the web application and performs automatic failover to the next nearest site if the closest site is down.
 
 :::image type="content" source="media/quickstart-create-front-door/environment-diagram.png" alt-text="Diagram of Front Door deployment environment using the Azure portal." border="false":::
 
@@ -49,11 +49,11 @@ To follow this quickstart, you need two web apps that run in different Azure reg
     | **Windows Plan** | Select **Create new** and type *myAppServicePlanCentralUS* in the text box. |
     | **Sku and size** | Select **Standard S1 100 total ACU, 1.75 GB memory**. |
 
-1. Select **Review + create** and verify the summary details. Then, select **Create** to initiate the deployment process. Note that the deployment may take several minutes to complete.
+1. Select **Review + create** and verify the summary details. Then, select **Create** to initiate the deployment process. The deployment may take several minutes to complete.
 
     :::image type="content" source="media/quickstart-create-front-door/create-web-app.png" alt-text="Screenshot showing Create Web App page." lightbox="./media/quickstart-create-front-door/create-web-app.png":::
 
-Once you have successfully deployed your first web app, proceed to create another one. Follow the same steps and enter the same values as before, except for the ones listed below:
+Once you have successfully deployed your first web app, proceed to create another one. Follow the same steps and enter the same values as before, except for the ones listed:
 
 | Setting | Value |
 |--|--|
@@ -92,100 +92,101 @@ Next, set up a backend pool that includes your two web apps.
 
     :::image type="content" source="media/quickstart-create-front-door/front-door-add-backend-pool.png" alt-text="Add a backend pool." lightbox="./media/quickstart-create-front-door/front-door-add-backend-pool.png":::
 
-1. In the **Add a backend** pane, select the following information and select **Add**.
+1. Provide or select the following information in the *Add a backend* pane and select **Add**.
 
     | Setting | Value |
     | --- | --- |
     | **Backend host type** | Select **App service**. |   
     | **Subscription** | Select your subscription. |    
-    | **Backend host name** | Select the first web app you created. In this example, the web app was *WebAppContoso-1*. |
+    | **Backend host name** | Select the first web app you created. For example, *WebAppContoso-1*. |
 
-    **Leave all other fields default.**
+    **Keep all other fields default.**
 
     :::image type="content" source="media/quickstart-create-front-door/front-door-add-a-backend.png" alt-text="Add a backend host to your Front Door." lightbox="./media/quickstart-create-front-door/front-door-add-a-backend.png":::
 
-1. Select **Add a backend** again. select the following information and select **Add**.
+1. “Select **Add a backend** again. Provide or select the following information and select **Add**.
 
     | Setting | Value |
     | --- | --- |
     | **Backend host type** | Select **App service**. |   
     | **Subscription** | Select your subscription. |    
-    | **Backend host name** | Select the second web app you created. In this example, the web app was *WebAppContoso-2*. |
+    | **Backend host name** | Select the second web app you created. For example, *WebAppContoso-2*. |
 
-    **Leave all other fields default.**
+    **Keep all other fields default.**
 
-1. Select **Add** on the **Add a backend pool** pane to complete the configuration of the backend pool.
+1. Select **Add** on the *Add a backend pool* page to finish the configuration of the backend pool.
 
     :::image type="content" source="media/quickstart-create-front-door/front-door-add-backend-pool-complete.png" alt-text="Add a backend pool for Azure Front Door." lightbox="./media/quickstart-create-front-door/front-door-add-backend-pool-complete.png":::
 
-Finally, add a routing rule. A routing rule maps your frontend host to the backend pool. The rule forwards a request for `contoso-frontend.azurefd.net` to **myBackendPool**.
+Lastly, create a routing rule. A routing rule links your frontend host to the backend pool. The rule routes a request for `contoso-frontend.azurefd.net` to **myBackendPool**.
 
-1. Still in **Create a Front Door**, in **Routing rules**, select **+** to configure a routing rule.
+1. Still in *Create a Front Door*, in *Routing rules*, select **+** to set up a routing rule.
 
-1. In **Add a rule**, for **Name**, enter *LocationRule*. Accept all the default values, then select **Add** to add the routing rule.
+1. In *Add a rule*, for **Name**, type LocationRule. Keep all the default values, then select Add to create the routing rule.”
 
     :::image type="content" source="media/quickstart-create-front-door/front-door-add-a-rule.png" alt-text="Screenshot showing Add a rule when creating Front Door." lightbox="./media/quickstart-create-front-door/front-door-add-a-rule.png":::
 
-   >[!WARNING]
-   > You **must** ensure that each of the frontend hosts in your Front Door has a routing rule with a default path (`/*`) associated with it. That is, across all of your routing rules there must be at least one routing rule for each of your frontend hosts defined at the default path (`/*`). Failing to do so may result in your end-user traffic not getting routed correctly.
+    > [!WARNING]
+    > It's essential that you associate each of the frontend hosts in your Azure Front Door with a routing rule that has a default path `/*`. This means that you need to have at least one routing rule for each of your frontend hosts at the default path `/*` among all of your routing rules. Otherwise, your end-user traffic may not be routed properly. 
 
-1. Select **Review + Create**, and then **Create**.
+1. Select **Review + create** and verify the details. Then, select **Create** to start the deployment.
 
     :::image type="content" source="media/quickstart-create-front-door/configuration-azure-front-door.png" alt-text="Configured Azure Front Door." lightbox="./media/quickstart-create-front-door/configuration-azure-front-door.png":::
 
 
 ## View Azure Front Door in action
 
-Once you create a Front Door, it takes a few minutes for the configuration to be deployed globally. Once complete, access the frontend host you created. In a browser, go to your frontend host address. Your request will automatically get routed to the nearest server to you from the specified servers in the backend pool.
+Once you create a Front Door, it takes a few minutes for the configuration to be deployed globally; once completed, access the frontend host you created. In the browser, go to your frontend host address. Your requests automatically get routed to your nearest server from the specified servers in the backend pool.
 
-If you created these apps in this quickstart, you'll see an information page.
+If you followed this quickstart to create these apps, you see an information page.
 
-To test instant global failover in action, try the following steps:
+To test the instant global failover feature, try the following steps:
 
-1. Open the resource group **FrontDoorQS_rg0** and select the frontend service.
+1. Navigate to the resource group **FrontDoorQS_rg0** and select the Front Door service.”
 
     :::image type="content" source="./media/quickstart-create-front-door/front-door-view-frontend-service.png" alt-text="Screenshot of frontend service." lightbox="./media/quickstart-create-front-door/front-door-view-frontend-service.png":::
 
 1. From the **Overview** page, copy the **Frontend host** address.
 
     :::image type="content" source="./media/quickstart-create-front-door/front-door-view-frontend-host-address.png" alt-text="Screenshot of frontend host address." lightbox="./media/quickstart-create-front-door/front-door-view-frontend-host-address.png":::
 
-1. Open a browser, as described above, and go to your frontend address.
+1. Open the browser, as described previously, and go to your frontend address.
 
-1. In the Azure portal, search for and select *App services*. Scroll down to find one of your web apps, **WebAppContoso-1** in this example.
+1. In the Azure portal, search for and select App services. Scroll down to find one of your web apps, for example, *WebAppContoso-1*.
 
-1. Select your web app, and then select **Stop**, and **Yes** to verify.
+1. Select your web app, and then select **Stop**, and **Yes** to confirm.
 
 1. Refresh your browser. You should see the same information page.
 
-   >[!TIP]
-   >There is a little bit of delay for these actions. You might need to refresh again.
+    > [!TIP]
+    > These actions may take some time to take effect. You may need to refresh the browser again.”
 
-1. Find the other web app, and stop it as well.
+1. Locate the other web app, and stop it as well.
 
 1. Refresh your browser. This time, you should see an error message.
 
    :::image type="content" source="media/quickstart-create-front-door/web-app-stopped-message.png" alt-text="Both instances of the web app stopped." lightbox="./media/quickstart-create-front-door/web-app-stopped-message.png":::
 
 ## Clean up resources
 
-After you're done, you can remove all the items you created. Deleting a resource group also deletes its contents. If you don't intend to use this Front Door, you should remove resources to avoid unnecessary charges.
+After you're done, you can delete all the items you created. Deleting the resource group also deletes its contents. If you don't intend to use this Front Door, you should delete the resources to avoid incurring unnecessary charges.
 
-1. In the Azure portal, search for and select **Resource groups**, or select **Resource groups** from the Azure portal menu.
+1. In the Azure portal, search for and select **Resource groups**, or choose **Resource groups** from the Azure portal menu.
 
-1. Filter or scroll down to find a resource group, such as **FrontDoorQS_rg0**.
+1. Filter or scroll down to find a resource group, for example, *FrontDoorQS_rg0*.
 
-1. Select the resource group, then select **Delete resource group**.
+1. Choose the resource group, then select **Delete** resource group.
 
-   >[!WARNING]
-   >This action is irreversible.
+    > [!WARNING]
+    > This action can't be undone.
 
-1. Type the resource group name to verify, and then select **Delete**.
+1. Enter the name of the resource group that you want to delete, and then select **Delete**.
 
-Repeat the procedure for the other two groups.
+1. Repeat these steps for the remaining two groups.
 
 ## Next steps
 
-Advance to the next article to learn how to add a custom domain to your Front Door.
+Proceed to the next article to learn how to configure a custom domain for your Front Door.
+
 > [!div class="nextstepaction"]
 > [Add a custom domain](front-door-custom-domain.md)