Fix links

Author: craigshoemaker

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

@@ -7,8 +7,6 @@ ms.date: 02/24/2020
 ms.author: cshoe
 ---
 
-## Input
-
 The Azure Cosmos DB input binding uses the SQL API to retrieve one or more Azure Cosmos DB documents and passes them to the input parameter of the function. The document ID or query parameters can be determined based on the trigger that invokes the function.
 
 For information on setup and configuration details, see the [overview](./functions-bindings-cosmosdb-v2.md).
@@ -1393,7 +1391,7 @@ public class DocsFromRouteSqlQuery {
 
  ---
 
-## Input - attributes and annotations
+## Attributes and annotations
 
 # [C#](#tab/csharp)
 
@@ -1419,7 +1417,7 @@ From the [Java functions runtime library](https://docs.microsoft.com/java/api/ov
 
 ---
 
-## Input - configuration
+## Configuration
 
 The following table explains the binding configuration properties that you set in the *function.json* file and the `CosmosDB` attribute.
 
@@ -1437,7 +1435,7 @@ The following table explains the binding configuration properties that you set i
 
 [!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
 
-## Input - usage
+## Usage
 
 # [C#](#tab/csharp)
 

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

@@ -516,7 +516,7 @@ In the [Java functions runtime library](/java/api/overview/azure/functions/runti
 
 ---
 
-## Output - attributes and annotations
+## Attributes and annotations
 
 # [C#](#tab/csharp)
 
@@ -552,7 +552,7 @@ The `CosmosDBOutput` annotation is available to write data to Cosmos DB. You can
 
 ---
 
-## Output - configuration
+## Configuration
 
 The following table explains the binding configuration properties that you set in the *function.json* file and the `CosmosDB` attribute.
 
@@ -570,7 +570,7 @@ The following table explains the binding configuration properties that you set i
 
 [!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
 
-## Output - usage
+## Usage
 
 By default, when you write to the output parameter in your function, a document is created in your database. This document has an automatically generated GUID as the document ID. You can specify the document ID of the output document by specifying the `id` property in the JSON object passed to the output parameter.
 

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

@@ -187,7 +187,7 @@ The attribute's constructor takes the database name and collection name. For inf
     }
 ```
 
-For a complete example, see [Trigger](#trigger).
+For a complete example, see [Trigger](#example).
 
 # [C# Script](#tab/csharp-script)
 

articles/cosmos-db/how-to-configure-cosmos-db-trigger-connection-policy.md

@@ -18,7 +18,7 @@ There are two connection modes - Direct mode and Gateway mode. To learn more abo
 
 ## Changing the connection mode and protocol
 
-There are two key configuration settings available to configure the client connection policy – the **connection mode** and the **connection protocol**. You can change the default connection mode and protocol used by the Azure Functions trigger for Cosmos DB and all the [Azure Cosmos DB bindings](../azure-functions/functions-bindings-cosmosdb-v2-output.md)). To change the default settings, you need to locate the `host.json` file in your Azure Functions project or Azure Functions App and add the following [extra setting](../azure-functions/functions-bindings-cosmosdb-v2.md#hostjson-settings):
+There are two key configuration settings available to configure the client connection policy – the **connection mode** and the **connection protocol**. You can change the default connection mode and protocol used by the Azure Functions trigger for Cosmos DB and all the [Azure Cosmos DB bindings](../azure-functions/functions-bindings-cosmosdb-v2-output.md)). To change the default settings, you need to locate the `host.json` file in your Azure Functions project or Azure Functions App and add the following [extra setting](../azure-functions/functions-bindings-cosmosdb-v2-output.md#hostjson-settings):
 
 ```js
 {

articles/cosmos-db/how-to-create-multiple-cosmos-db-triggers.md

@@ -33,7 +33,7 @@ The goal of this article is to guide you to accomplish the second option.
 
 ## Configuring a shared leases container
 
-To configure the shared leases container, the only extra configuration you need to make on your triggers is to add the `LeaseCollectionPrefix` [attribute](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#attributes-and-annotations) if you are using C# or `leaseCollectionPrefix` [attribute](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger) if you are using JavaScript. The value of the attribute should be a logical descriptor of what that particular trigger.
+To configure the shared leases container, the only extra configuration you need to make on your triggers is to add the `LeaseCollectionPrefix` [attribute](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#attributes-and-annotations) if you are using C# or `leaseCollectionPrefix` [attribute](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md) if you are using JavaScript. The value of the attribute should be a logical descriptor of what that particular trigger.
 
 For example, if you have three Triggers: one that sends emails, one that does an aggregation to create a materialized view, and one that sends the changes to another storage, for later analysis, you could assign the `LeaseCollectionPrefix` of "emails" to the first one, "materialized" to the second one, and "analytics" to the third one.