fixed broken link

Author: richagaur

articles/cosmos-db/autoscale-faq.yml

@@ -187,7 +187,7 @@ sections:
           If the overall consumed RU/s exceeds the max RU/s of the database or container, requests that exceed the max RU/s are throttled and return a 429 status code. Requests that result in over 100% normalized utilization are throttled. Normalized utilization is defined as the max of the RU/s utilization across all physical partitions. For example, suppose your max throughput is 20,000 RU/s and you have two physical partitions, P_1 and P_2, each capable of scaling to 10,000 RU/s. In a given second, if P_1 has used 6000 RUs, and P_2 8000 RUs, the normalized utilization is MAX(6000 RU / 10,000 RU, 8000 RU / 10,000 RU) = 0.8.
           
           > [!NOTE]
-          > The Azure Cosmos DB client SDKs and data import tools (Azure Data Factory, bulk executor library) automatically retry on 429's, so occasional 429's are fine. A sustained high number of 429's may indicate you need to increase the max RU/s or review your partitioning strategy for a [hot partition](#is-it-still-possible-to-see-429's--throttling-rate-limiting--when-autoscale-is-enabled).
+          > The Azure Cosmos DB client SDKs and data import tools (Azure Data Factory, bulk executor library) automatically retry on 429's, so occasional 429's are fine. A sustained high number of 429's may indicate you need to increase the max RU/s or review your partitioning strategy for a [hot partition](#is-it-still-possible-to-see-429-s--throttling-rate-limiting--when-autoscale-is-enabled).
           
       - question: Is it still possible to see 429's (throttling/rate limiting) when autoscale is enabled? 
         answer: |