Remove duplicate dogstatsd link and renumber references

Consolidated duplicate [1] and [2] link references that both pointed
to /developers/dogstatsd, and renumbered all subsequent link references
to maintain sequential ordering.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: lucaspimentel

content/en/serverless/azure_app_service/windows_code.md

@@ -21,7 +21,7 @@ further_reading:
 
 ## Overview
 
-The Datadog extension for Azure App Service provides monitoring capabilities in addition to the [Datadog-Azure integration][6], which provides metrics and logs.
+The Datadog extension for Azure App Service provides monitoring capabilities in addition to the [Datadog-Azure integration][5], which provides metrics and logs.
 
 - Full distributed APM tracing using automatic instrumentation.
 - Customized APM service and trace views showing relevant Azure App Service metrics and metadata.
@@ -65,15 +65,15 @@ There are no billing implications for tracing Java Web Apps during this period.
 ## Installation
 Datadog recommends doing regular updates to the latest version of the extension to ensure optimal performance, stability, and availability of features. Note that both the initial install and subsequent updates require your web app to be fully stopped in order to install/update successfully.
 
-If you haven't already, set up the [Datadog-Azure integration][4]. You can verify that your Azure integration is configured correctly by ensuring that you see the `azure.app_services.count` or `azure.functions.count` metrics in Datadog.
+If you haven't already, set up the [Datadog-Azure integration][3]. You can verify that your Azure integration is configured correctly by ensuring that you see the `azure.app_services.count` or `azure.functions.count` metrics in Datadog.
 
 <div class="alert alert-info">This step is critical for metric/trace correlation and functional trace panel views and improves the overall experience of using Datadog with Azure App Services.
 </div>
 
 {{< tabs >}}
 {{% tab "Terraform" %}}
 
-The [Datadog Terraform module for Windows Web Apps][4] wraps the [azurerm_windows_web_app][5] resource and automatically configures your Web App for Datadog Serverless Monitoring by adding required environment variables and the Windows Web App extension for your runtime.
+The [Datadog Terraform module for Windows Web Apps][3] wraps the [azurerm_windows_web_app][4] resource and automatically configures your Web App for Datadog Serverless Monitoring by adding required environment variables and the Windows Web App extension for your runtime.
 
 If you don't already have Terraform set up, [install Terraform][1], create a new directory, and make a file called `main.tf`.
 
@@ -126,7 +126,7 @@ module "my_web_app" {
 
 Finally, run `terraform apply`, and follow any prompts.
 
-The [Datadog Windows Web App module][2] only deploys the Web App resource and extension, so you need to [deploy your code][3] separately.
+The [Datadog Windows Web App module][2] only deploys the Web App resource and extension, so you need to [deploy your code][2] separately.
 
 [1]: https://developer.hashicorp.com/terraform/install
 [2]: https://registry.terraform.io/modules/DataDog/web-app-datadog/azurerm/latest/submodules/windows
@@ -149,11 +149,11 @@ The [Datadog Windows Web App module][2] only deploys the Web App resource and ex
 
    `DD_SITE`
    : **Value**: Your Datadog site<br>
-   Your [Datadog site][3]. Defaults to `datadoghq.com`.<br>
+   Your [Datadog site][2]. Defaults to `datadoghq.com`.<br>
 
    **Unified Service Tagging**
 
-   Datadog recommends tagging your application with the `env`, `service`, and `version` tags for [unified service tagging][4].
+   Datadog recommends tagging your application with the `env`, `service`, and `version` tags for [unified service tagging][3].
 
    `DD_SERVICE`
    : **Value**: Your application's service name.<br>
@@ -204,9 +204,9 @@ The [Datadog Windows Web App module][2] only deploys the Web App resource and ex
 
 ## Custom metrics
 
-The Azure App Service extension includes an instance of [DogStatsD][2], Datadog's metrics aggregation service. This enables you to submit custom metrics, service checks, and events directly to Datadog from Azure Web Apps and Functions with the extension.
+The Azure App Service extension includes an instance of [DogStatsD][1], Datadog's metrics aggregation service. This enables you to submit custom metrics, service checks, and events directly to Datadog from Azure Web Apps and Functions with the extension.
 
-Writing custom metrics and checks in Azure App Service is similar to the process for doing so with an application on a host running the Datadog Agent. **Unlike** the [standard DogStatsD config process][2], there is no need to set ports or a server name when initializing the DogStatsD configuration. There are ambient environment variables in Azure App Service that determine how the metrics are sent (requires v6.0.0+ of the DogStatsD client).
+Writing custom metrics and checks in Azure App Service is similar to the process for doing so with an application on a host running the Datadog Agent. **Unlike** the [standard DogStatsD config process][1], there is no need to set ports or a server name when initializing the DogStatsD configuration. There are ambient environment variables in Azure App Service that determine how the metrics are sent (requires v6.0.0+ of the DogStatsD client).
 
 To submit custom metrics to Datadog from Azure App Service using the extension:
 
@@ -282,7 +282,7 @@ tracer.dogstatsd.decrement('example_metric.decrement', 1, { environment: 'dev' }
   - Set `DD_TRACE_ENABLED` to `false`.
   - Set `DD_AAS_ENABLE_CUSTOM_METRICS` to `true`.
 
-Learn more about [custom metrics][3].
+Learn more about [custom metrics][2].
 
 ## Logging
 
@@ -537,7 +537,7 @@ It is likely that you do not have the Azure integration configured to monitor yo
 
 1. Go to the Azure integration tile.
 
-2. Ensure you have installed the [Azure integration][4] for the Azure subscription where your application is running.
+2. Ensure you have installed the [Azure integration][3] for the Azure subscription where your application is running.
 
 3. Ensure that any App Service plan filtering rules you have applied include the App Service plan where the app is running. If an App Service plan is not included, all apps and functions hosted on it are also not included. Tags on the app itself are not used for filtering by Datadog.
 
@@ -551,15 +551,14 @@ It is likely that you do not have the Azure integration configured to monitor yo
 
 **Note**: To expedite the process of investigating application errors with the support team, set `DD_TRACE_DEBUG:true` and add the content of the Datadog logs directory (`%AzureAppServiceHomeDirectory%\LogFiles\datadog`) to your email.
 
-Still need help? Contact [Datadog support][5].
+Still need help? Contact [Datadog support][4].
 
 ### Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /developers/dogstatsd
-[2]: /developers/dogstatsd
-[3]: /metrics/
-[4]: /integrations/azure/
-[5]: /help
-[6]: https://app.datadoghq.com/integrations/azure
+[2]: /metrics/
+[3]: /integrations/azure/
+[4]: /help
+[5]: https://app.datadoghq.com/integrations/azure