Update links

Author: Sohamdg081992

articles/azure-monitor/containers/prometheus-metrics-scrape-configuration.md

@@ -498,7 +498,7 @@ Scraping targets using basic auth is currently not supported using pod/service m
 ---
 
 If you are using both basic auth and tls auth, please refer to the [section](#create-secret-using-yaml-for-both-basic-and-tls-auth) below.
-For more details, refer to the [note section](#note-section).
+For more details, refer to the [note section](#note-for-both-basic-and-tls-authentication) below.
 
 
 ### TLS based scraping
@@ -521,8 +521,6 @@ Please follow the below steps.
      <certfile>: base64_cert_content    
      <keyfile>: base64_key_content 
    ```
-   
----
 
    The **ama-metrics-mtls-secret** secret is mounted on to the ama-metrics containers at path - **/etc/prometheus/certs/**  and is made available to the process that is scraping prometheus metrics. The key( ex - certfile) in the above example will be the file name and the value is base64 decoded and added to the contents of the file within the container and    the prometheus scraper uses the contents of this file to get the value that is used as the password used to scrape the endpoint.
 
@@ -569,7 +567,6 @@ Please follow the below steps.
    If you want to use both basic and Tls authentication settings in your configmap/CRD, just make sure that the secret **ama-metrics-mtls-secret** includes all the files(keys) under the data section with their corresponding base 64 encoded values, as shown below.
 
    ```yaml
-
    apiVersion: v1
    kind: Secret
    metadata:
@@ -581,10 +578,9 @@ Please follow the below steps.
      keyfile: base64_key_content      # used for Tls
      password1: base64-encoded-string # used for basic auth
      password2: base64-encoded-string # used for basic auth
+   ```
 
-   ```yaml
-
-<a name="note-section"></a>
+### Note for both Basic and TLS authentication
 > [!NOTE]
 > 
 > The **/etc/prometheus/certs/** path is mandatory, but *password1* can be any string and needs to match the key for the data in the secret created above. This is because the secret **ama-metrics-mtls-secret** is mounted in the path **/etc/prometheus/certs/** within the container.