Fixing links

Author: nzthiago

articles/azure-functions/functions-bindings-cosmosdb-v2-trigger.md

@@ -14,7 +14,7 @@ The Azure Cosmos DB Trigger uses the [Azure Cosmos DB change feed](../cosmos-db/
 
 For information on setup and configuration details, see the [overview](./functions-bindings-cosmosdb-v2.md).
 
-Cosmos DB scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](../articles/azure-functions/functions-target-based-scaling.md).
+Cosmos DB scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](functions-target-based-scaling.md).
 
 ::: zone pivot="programming-language-python"
 Azure Functions supports two programming models for Python. The way that you define your bindings depends on your chosen programming model.

articles/azure-functions/functions-bindings-service-bus-trigger.md

@@ -16,7 +16,7 @@ Starting with extension version 3.1.0, you can trigger on a session-enabled queu
 
 For information on setup and configuration details, see the [overview](functions-bindings-service-bus.md).
 
-Service Bus scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](../articles/azure-functions/functions-target-based-scaling.md).
+Service Bus scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](functions-target-based-scaling.md).
 
 ::: zone pivot="programming-language-python"
 Azure Functions supports two programming models for Python. The way that you define your bindings depends on your chosen programming model.

articles/azure-functions/functions-bindings-storage-queue-trigger.md

@@ -12,7 +12,7 @@ zone_pivot_groups: programming-languages-set-functions-lang-workers
 
 The queue storage trigger runs a function as messages are added to Azure Queue storage.
 
-Azure Queue storage scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](../articles/azure-functions/functions-target-based-scaling.md).
+Azure Queue storage scaling decisions for the Consumption and Premium plans are done via Target Based Scaling. For more information, see [Target Based Scaling](functions-target-based-scaling.md).
 
 ::: zone pivot="programming-language-python"  
 Azure Functions supports two programming models for Python. The way that you define your bindings depends on your chosen programming model.

articles/azure-functions/functions-target-based-scaling.md

@@ -253,7 +253,7 @@ Sample `bindings` section of a `function.json` with `MaxItemsPerInvocation` defi
 }
 ```
 > [!NOTE]
-> Since Cosmos DB is a partitioned workload, the target instance count for Cosmos DB is capped by the number of physical partitions in your Cosmos DB. For further documentation on Cosmos DB scaling, please see notes on [physical partitions](../cosmos-db/nosql/change-feed-processor.md?tabs=dotnet#dynamic-scaling:~:text=We%20see%20that,a%20lease%20document) and [lease ownership](../cosmos-db/nosql/change-feed-processor.md?tabs=dotnet#dynamic-scaling:~:text=One%20lease%20can%20only%20be%20owned%20by%20one%20instance%20at%20a%20given%20time%2C%20so%20the%20number%20of%20instances%20should%20not%20be%20greater%20than%20the%20number%20of%20leases.).
+> Since Cosmos DB is a partitioned workload, the target instance count for Cosmos DB is capped by the number of physical partitions in your Cosmos DB. For further documentation on Cosmos DB scaling, please see notes on [physical partitions](../cosmos-db/nosql/change-feed-processor.md#dynamic-scaling) and [lease ownership](../cosmos-db/nosql/change-feed-processor.md#dynamic-scaling).
 
 ## Opting Out
 Target Based Scaling is an opt-out feature except for function apps on the the Premium plan with Runtime Scale Monitoring enabled. This means it is on by default for the Functions Consumption plan, and Premium plans without Runtime Scale Monitoring. If you wish to disable Target Based Scaling and revert to incremental scaling, add the following app setting to your function app:

includes/functions-bindings-event-hubs-trigger.md

@@ -509,7 +509,7 @@ The following table explains the trigger configuration properties that you set i
 
 ## Usage
 
-To learn more about how Event Hubs trigger and IoT Hub trigger scales, see [Event Hubs trigger](../articles/azure-functions/event-driven-scaling.md#event-hubs-triggers).
+To learn more about how Event Hubs trigger and IoT Hub trigger scales, see [Consuming Events with Azure Functions](/azure/architecture/serverless/event-hubs-functions/event-hubs-functions#consuming-events-with-azure-functions).
 
 ::: zone pivot="programming-language-csharp"  
 The parameter type supported by the Event Hubs output binding depends on the Functions runtime version, the extension package version, and the C# modality used.