A couple of updates based on review

Author: nzthiago

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](functions-target-based-scaling.md).
+Service Bus scaling decisions for the Consumption and Premium plans are made based on 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

@@ -54,11 +54,11 @@ This table summarizes the `host.json` values that are used for the _target execu
 | Event Hubs (if defined)                                        | extensions.eventHubs.targetUnprocessedEventThreshold              |       n/a     |
 | Storage Queue                                                  | extensions.queues.batchSize                                       |       16      |
 
-For Cosmos DB _target executions per instance_ is set in the function attribute:
+For Azure Cosmos DB _target executions per instance_ is set in the function attribute:
 
-| Extension   | Function trigger setting | Default Value | 
-| ------------| ------------------------ | ------------- |
-| Cosmos DB   | maxItemsPerInvocation    |  100          |
+| Extension         | Function trigger setting | Default Value | 
+| ----------------- | ------------------------ | ------------- |
+| Azure Cosmos DB   | maxItemsPerInvocation    |  100          |
 
 See [Details per extension](#details-per-extension) for example configurations of the supported extensions.