Fix links

Author: craigshoemaker

articles/app-service/webjobs-sdk-how-to.md

@@ -392,7 +392,7 @@ static async Task Main()
 }
 ```
 
-For more details, see the [Azure CosmosDB binding](../azure-functions/functions-bindings-cosmosdb-v2.md#hostjson-settings) article.
+For more details, see the [Azure CosmosDB binding](../azure-functions/functions-bindings-cosmosdb-v2-output.md#hostjson-settings) article.
 
 ### Event Hubs trigger configuration (version 3.*x*)
 

articles/azure-functions/functions-host-json.md

@@ -203,7 +203,7 @@ For more information on snapshots, see [Debug snapshots on exceptions in .NET ap
 
 ## cosmosDb
 
-Configuration setting can be found in [Cosmos DB triggers and bindings](functions-bindings-cosmosdb-v2.md#host-json).
+Configuration setting can be found in [Cosmos DB triggers and bindings](functions-bindings-cosmosdb-v2-output.md#host-json).
 
 ## durableTask
 

articles/cosmos-db/change-feed-functions.md

@@ -15,7 +15,7 @@ Azure Functions provides the simplest way to connect to the [change feed](change
 
 ![Serverless event-based Functions working with the Azure Functions trigger for Cosmos DB](./media/change-feed-functions/functions.png)
 
-With the [Azure Functions trigger for Cosmos DB](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger), you can leverage the [Change Feed Processor](./change-feed-processor.md)'s scaling and reliable event detection functionality without the need to maintain any [worker infrastructure](./change-feed-processor.md). Just focus on your Azure Function's logic without worrying about the rest of the event-sourcing pipeline. You can even mix the Trigger with any other [Azure Functions bindings](../azure-functions/functions-triggers-bindings.md#supported-bindings).
+With the [Azure Functions trigger for Cosmos DB](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md), you can leverage the [Change Feed Processor](./change-feed-processor.md)'s scaling and reliable event detection functionality without the need to maintain any [worker infrastructure](./change-feed-processor.md). Just focus on your Azure Function's logic without worrying about the rest of the event-sourcing pipeline. You can even mix the Trigger with any other [Azure Functions bindings](../azure-functions/functions-triggers-bindings.md#supported-bindings).
 
 > [!NOTE]
 > Currently, the Azure Functions trigger for Cosmos DB is supported for use with the Core (SQL) API only.
@@ -25,7 +25,7 @@ With the [Azure Functions trigger for Cosmos DB](../azure-functions/functions-bi
 To implement a serverless event-based flow, you need:
 
 * **The monitored container**: The monitored container is the Azure Cosmos container being monitored, and it stores the data from which the change feed is generated. Any inserts, updates to the monitored container are reflected in the change feed of the container.
-* **The lease container**: The lease container maintains state across multiple and dynamic serverless Azure Function instances and enables dynamic scaling. This lease container can be manually or automatically created by the Azure Functions trigger for Cosmos DB. To automatically create the lease container, set the *CreateLeaseCollectionIfNotExists* flag in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration). Partitioned lease containers are required to have a `/id` partition key definition.
+* **The lease container**: The lease container maintains state across multiple and dynamic serverless Azure Function instances and enables dynamic scaling. This lease container can be manually or automatically created by the Azure Functions trigger for Cosmos DB. To automatically create the lease container, set the *CreateLeaseCollectionIfNotExists* flag in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration). Partitioned lease containers are required to have a `/id` partition key definition.
 
 ## Create your Azure Functions trigger for Cosmos DB
 

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.md#output)). 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.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.md#trigger---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.md#trigger) 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.
 
@@ -103,6 +103,6 @@ And for JavaScript, you can apply the configuration on the `function.json` file,
 
 ## Next steps
 
-* See the full configuration for the [Azure Functions trigger for Cosmos DB](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration)
-* Check the extended [list of samples](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger) for all the languages.
+* See the full configuration for the [Azure Functions trigger for Cosmos DB](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration)
+* Check the extended [list of samples](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md) for all the languages.
 * Visit the Serverless recipes with Azure Cosmos DB and Azure Functions [GitHub repository](https://github.com/ealsur/serverless-recipes/tree/master/cosmosdbtriggerscenarios) for more samples.

articles/cosmos-db/troubleshoot-changefeed-functions.md

@@ -61,7 +61,7 @@ This scenario can have multiple causes and all of them should be checked:
 
 1. Is your Azure Function deployed in the same region as your Azure Cosmos account? For optimal network latency, both the Azure Function and your Azure Cosmos account should be colocated in the same Azure region.
 2. Are the changes happening in your Azure Cosmos container continuous or sporadic?
-If it's the latter, there could be some delay between the changes being stored and the Azure Function picking them up. This is because internally, when the trigger checks for changes in your Azure Cosmos container and finds none pending to be read, it will sleep for a configurable amount of time (5 seconds, by default) before checking for new changes (to avoid high RU consumption). You can configure this sleep time through the `FeedPollDelay/feedPollDelay` setting in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration) of your trigger (the value is expected to be in milliseconds).
+If it's the latter, there could be some delay between the changes being stored and the Azure Function picking them up. This is because internally, when the trigger checks for changes in your Azure Cosmos container and finds none pending to be read, it will sleep for a configurable amount of time (5 seconds, by default) before checking for new changes (to avoid high RU consumption). You can configure this sleep time through the `FeedPollDelay/feedPollDelay` setting in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration) of your trigger (the value is expected to be in milliseconds).
 3. Your Azure Cosmos container might be [rate-limited](./request-units.md).
 4. You can use the `PreferredLocations` attribute in your trigger to specify a comma-separated list of Azure regions to define a custom preferred connection order.
 
@@ -88,10 +88,10 @@ One easy way to workaround this situation, is to apply a `LeaseCollectionPrefix/
 To re-process all the items in a container from the beginning:
 1. Stop your Azure function if it is currently running. 
 1. Delete the documents in the lease collection (or delete and re-create the lease collection so it is empty)
-1. Set the [StartFromBeginning](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration) CosmosDBTrigger attribute in your function to true. 
+1. Set the [StartFromBeginning](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration) CosmosDBTrigger attribute in your function to true. 
 1. Restart the Azure function. It will now read and process all changes from the beginning. 
 
-Setting [StartFromBeginning](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration) to true will tell the Azure function to start reading changes from the beginning of the history of the collection instead of the current time. This only works when there are no already created leases (i.e. documents in the leases collection). Setting this property to true when there are leases already created has no effect; in this scenario, when a function is stopped and restarted, it will begin reading from the last checkpoint, as defined in the leases collection. To re-process from the beginning, follow the above steps 1-4.  
+Setting [StartFromBeginning](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration) to true will tell the Azure function to start reading changes from the beginning of the history of the collection instead of the current time. This only works when there are no already created leases (i.e. documents in the leases collection). Setting this property to true when there are leases already created has no effect; in this scenario, when a function is stopped and restarted, it will begin reading from the last checkpoint, as defined in the leases collection. To re-process from the beginning, follow the above steps 1-4.  
 
 ### Binding can only be done with IReadOnlyList\<Document> or JArray
 
@@ -101,7 +101,7 @@ To workaround this situation, remove the manual NuGet reference that was added a
 
 ### Changing Azure Function's polling interval for the detecting changes
 
-As explained earlier for [My changes take too long to be received](./troubleshoot-changefeed-functions.md#my-changes-take-too-long-to-be-received), Azure function will sleep for a configurable amount of time (5 seconds, by default) before checking for new changes (to avoid high RU consumption). You can configure this sleep time through the `FeedPollDelay/feedPollDelay` setting in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2.md#trigger---configuration) of your trigger (the value is expected to be in milliseconds).
+As explained earlier for [My changes take too long to be received](./troubleshoot-changefeed-functions.md#my-changes-take-too-long-to-be-received), Azure function will sleep for a configurable amount of time (5 seconds, by default) before checking for new changes (to avoid high RU consumption). You can configure this sleep time through the `FeedPollDelay/feedPollDelay` setting in the [configuration](../azure-functions/functions-bindings-cosmosdb-v2-trigger.md#configuration) of your trigger (the value is expected to be in milliseconds).
 
 ## Next steps