update tutorial

Author: halkazwini

articles/application-gateway/create-url-route-portal.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: tutorial
-ms.date: 09/03/2024
+ms.date: 02/05/2025
 ms.author: greglin
 #Customer intent: As an IT administrator, I want to use the Azure portal to set up an application gateway so I can route my app traffic based on path-based routing rules.
 ---
@@ -25,15 +25,12 @@ In this article, you learn how to:
 
 :::image type="content" source="./media/application-gateway-create-url-route-portal/scenario.png" alt-text="Diagram of application gateway URL routing example." lightbox="./media/application-gateway-create-url-route-portal/scenario.png":::
 
-[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
-
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
 ## Prerequisites
 
 - An Azure subscription
 
-
 ## Create virtual machines
 
 In this example, you create three virtual machines to be used as backend servers for the application gateway. You also install IIS on the virtual machines to verify that the application gateway works as expected.
@@ -159,18 +156,19 @@ On the **Configuration** tab, you'll connect the frontend and backend pool you c
 
 4. On the **Backend targets** tab, select **myBackendPool** for the **Backend target**.
 
-5. For the **HTTP setting**, select **Add new** to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. 
+5. For the **Backend settings**, select **Add new** to create a new HTTP setting. The HTTP setting will determine the behavior of the routing rule. 
 
-6. In the **Add an HTTP setting** window that opens, enter *myHTTPSetting* for the **HTTP setting name**. Accept the default values for the other settings in the **Add an HTTP setting** window, then select **Add** to return to the **Add a routing rule** window.
+6. In the **Add Backend setting** window that opens, enter *myHTTPSetting* for the **Backend settings name**. Accept the default values for the other settings in the **Add Backend setting** window, then select **Add** to return to the **Add a routing rule** window.
 7. Under **Path-based routing**, select **Add multiple targets to create a path-based rule**.
-8. For **Path**, type */images/*\*.
-9. For **Target name**, type *Images*.
-10. For **HTTP setting**, select **myHTTPSetting**
-11. For **Backend target**, select **Images**.
-12. Select **Add** to save the path rule and return to the **Add a routing rule** tab.
-13. Repeat to add another rule for Video.
-14. Select **Add** to add the routing rule and return to the **Configuration** tab.
-15. Select **Next: Tags** and then **Next: Review + create**.
+1. Under **Path based rules**, select **Add multiple targets to create a path-based rule**.
+1. For **Path**, type */images/*\*.
+1. For **Target name**, type *Images*.
+1. For **Backend settings**, select **myHTTPSetting**
+1. For **Backend target**, select **myBackendPool**.
+1. Select **Add** to save the path rule and return to the **Add a routing rule** tab.
+1. Repeat to add another rule for Video.
+1. Select **Add** to add the routing rule and return to the **Configuration** tab.
+1. Select **Next: Tags** and then **Next: Review + create**.
 
 > [!NOTE]
 > You do not need to add a custom */** path rule to handle default cases. This is automatically handled by the default backend pool.