Fix blocking issues

Author: ggailey777

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

@@ -374,7 +374,7 @@ For Python v2 functions defined using a decorator, the following properties on t
 |-------------|-----------------------------|
 |`arg_name` | The variable name used in function code that represents the list of documents with changes. |
 |`database_name`  | The name of the Azure Cosmos DB database with the collection being monitored. |
-|`collection_name`  | The name of the Azure CosmosDB collection being monitored. |
+|`collection_name`  | The name of the Azure Cosmos DB collection being monitored. |
 |`connection` | The connection string of the Azure Cosmos DB being monitored. |
 
 For Python functions defined by using *function.json*, see the [Configuration](#configuration) section.

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

@@ -17,7 +17,7 @@ Target-based scaling provides a fast and intuitive scaling model for customers a
 
 Target-based scaling  replaces the previous Azure Functions incremental scaling model as the default for these extension types. Incremental scaling added or removed a maximum of one worker at [each new instance rate](event-driven-scaling.md#understanding-scaling-behaviors), with complex decisions for when to scale. In contrast, target-based scaling allows scale up of four instances at a time, and the scaling decision is based on a simple target-based equation:
 
-![Desired instances = event source length / target executions per instance](./media/functions-target-based-scaling/targetbasedscalingformula.png)
+![Illustration of the equation: desired instances = event source length / target executions per instance.](./media/functions-target-based-scaling/target-based-scaling-formula.png)
 
 The default _target executions per instance_ values come from the SDKs used by the Azure Functions extensions. You don't need to make any changes for target-based scaling to work.