edit pass: azure-functions-triggers-and-bindings

Author: ShawnJackson

articles/azure-functions/extension-bundles.md

@@ -44,7 +44,7 @@ Keep these considerations in mind when you work with extension bundles:
 
 - When possible, you should set a `version` range value in `host.json` from the preceding table, such as `[4.0.0, 5.0.0)`, instead of defining a custom range.
 - Use the latest version range to obtain optimal app performance and access to the latest features.
-- In the unlikely event that you can't use an extension bundle, you must instead [explicitly install extensions](./functions-bindings-register.md#explicitly-install-extensions).
+- In the unlikely event that you can't use an extension bundle, you must instead [explicitly install extensions](./functions-bindings-register.md#explicitly-installing-extensions).
 
 ## Previewing extension bundles
 

articles/azure-functions/functions-bindings-expressions-patterns.md

@@ -14,7 +14,7 @@ One of the most powerful features of [triggers and bindings](./functions-trigger
 
 Most expressions are wrapped in curly braces. For example, in a queue trigger function, `{queueTrigger}` resolves to the queue message text. If the `path` property for a blob output binding is `container/{queueTrigger}` and a queue message `HelloWorld` triggers the function, a blob named `HelloWorld` is created.
 
-## App settings
+<a name = binding-expressions---app-settings></a>## App settings
 
 It's a best practice to manage secrets and connection strings by using app settings rather than configuration files. This practice limits access to these secrets and makes it safe to store files such as `function.json` in public source-control repositories.
 

articles/azure-functions/functions-bindings-register.md

@@ -31,7 +31,7 @@ In the unlikely event that you can't use an extension bundle, you must instead e
 
 ::: zone-end
 
-## Explicitly installing extensions
+<a name = "explicitly-install-extensions"></a>## Explicitly installing extensions
 ::: zone pivot="programming-language-csharp"  
 For projects that use a compiled C# class library, you install the NuGet packages for the extensions that you need as you normally would in your apps. For more information, see the [Visual Studio Code developer guide](functions-develop-vs-code.md?tabs=csharp#install-binding-extensions) or the [Visual Studio developer guide](functions-develop-vs.md#add-bindings).
 
@@ -60,7 +60,7 @@ To manually install binding extensions:
 
 1. Validate your app functionality locally and then redeploy your project, including `extensions.csproj`, to your function app in Azure.  
 
-As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#define-an-extension-bundle-reference).
+As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#defining-an-extension-bundle-reference).
 ::: zone-end
 
 ## Next steps

articles/azure-functions/functions-triggers-bindings.md

@@ -233,5 +233,5 @@ You can create custom input and output bindings. Bindings must be authored in .N
 - [Register Azure Functions binding extensions](./functions-bindings-register.md)
 - Testing:
   - [Strategies for testing your code in Azure Functions](functions-test-a-function.md)
-  - [Manually run a non HTTP-triggered function](functions-manually-run-non-http.md)
+  - [Manually run a non-HTTP-triggered function](functions-manually-run-non-http.md)
 - [Handling binding errors](./functions-bindings-errors.md)