fix broken link

Author: Cephas Lin

articles/app-service/app-service-web-tutorial-custom-domain.md

@@ -121,7 +121,7 @@ For a wildcard name like `*` in `*.contoso.com`, create two records according to
 
 | Record type | Host | Value | Comments |
 | - | - | - | - |
-| CNAME | `*` | `<app-name>.azurewebsites.net` (see [note at top](./includes/regionalization-note.md#dnl-note)) | The domain mapping itself. |
+| CNAME | `*` | `<app-name>.azurewebsites.net` (see [note at top](#dnl-note)) | The domain mapping itself. |
 | TXT | `asuid` | The domain verification ID shown in the **Add custom domain** dialog. | App Service accesses the `asuid` TXT record to verify your ownership of the custom domain. |
 
 ![Screenshot that shows the navigation to an Azure app.](./media/app-service-web-tutorial-custom-domain/cname-record-wildcard.png)

articles/app-service/deploy-zip.md

@@ -39,7 +39,7 @@ This ZIP package deployment uses the same Kudu service that powers continuous in
 
 #### With zip deploy UI in Kudu
 
-In the browser, navigate to `https://<app_name>.scm.azurewebsites.net/ZipDeployUI` (see [note at top](./includes/regionalization-note.md#dnl-note)).
+In the browser, navigate to `https://<app_name>.scm.azurewebsites.net/ZipDeployUI` (see [note at top](#dnl-note)).
 
 Upload the ZIP package you created in [Create a project ZIP package](#create-a-project-zip-package) by dragging it to the file explorer area on the web page.
 
@@ -90,7 +90,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 # [ARM template](#tab/arm)
 
@@ -153,7 +153,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 For more information, see [Kudu publish API reference](#kudu-publish-api-reference)
 
@@ -218,7 +218,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 ### Deploy a library file
 
@@ -241,7 +241,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 ### Deploy a static file
 
@@ -264,7 +264,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 # [ARM template](#tab/arm)
 
@@ -313,7 +313,7 @@ curl -X POST \
 ```
 
 > [!NOTE]
-> For the actual fully qualified domain name to use in the URL, see [note at top](./includes/regionalization-note.md#dnl-note)
+> For the actual fully qualified domain name to use in the URL, see [note at top](#dnl-note)
 
 # [ARM template](#tab/arm)
 

articles/app-service/includes/regionalization-note.md

@@ -10,7 +10,7 @@ ms.date: 04/22/2024
 > [!NOTE]
 > Beginning April 22, 2024, all newly created App Service apps will have the option to create a unique default hostname with a naming convention of `<app-name>`-`<random-hash>`.`<region>`.`azurewebsites.net`. The names of existing apps will not change.
 >
->Example: myapp-ds27dh7271aah175.westus-01.azurewebsites.net 
+> Example: myapp-ds27dh7271aah175.westus-01.azurewebsites.net 
 >    
->For more information, refer to [Unique Default Hostname for App Service Resource](https://go.microsoft.com/fwlink/?linkid=2265728).
+> For more information, refer to [Unique Default Hostname for App Service Resource](https://go.microsoft.com/fwlink/?linkid=2265728).
 >

articles/app-service/includes/tutorial-set-up-app-service-authentication/after.md

@@ -154,7 +154,7 @@ When you enabled the App Service authentication/authorization module in the prev
 1. Select the app registration that was created. 
 1. In the overview, verify that **Supported account types** is set to **My organization only**.
 
-1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.  Or, start a browser in incognito or private mode and go to `https://<app-name>.azurewebsites.net` (see [note at top](../regionalization-note.md#dnl-note)).
+1. To verify that access to your app is limited to users in your organization, go to your web app **Overview** and select the **Default domain** link.  Or, start a browser in incognito or private mode and go to `https://<app-name>.azurewebsites.net` (see [note at top](#dnl-note)).
 
     :::image type="content" alt-text="Screenshot that shows verifying access." source="../../media/scenario-secure-app-authentication-app-service/verify-access.png":::
 

articles/app-service/overview-private-endpoint.md

@@ -55,7 +55,7 @@ In the Web HTTP logs of your app, you find the client source IP. This feature is
 
 ## DNS
 
-When you use private endpoint for App Service apps, the requested URL must match the name of your app. By default mywebappname.azurewebsites.net (see [note at top](./includes/regionalization-note.md#dnl-note)).
+When you use private endpoint for App Service apps, the requested URL must match the name of your app. By default mywebappname.azurewebsites.net (see [note at top](#dnl-note)).
 
 By default, without private endpoint, the public name of your web app is a canonical name to the cluster.
 For example, the name resolution is: