Additional edits.

Author: TimShererWithAquent

articles/azure-functions/functions-dotnet-class-library.md

@@ -90,12 +90,12 @@ Version 4.x of the Functions runtime provides equivalent functionality for .NET
 
 In Visual Studio, the **Azure Functions** project template creates a C# class library project that contains the following files:
 
-* [host.json](functions-host-json.md) - stores configuration settings that affect all functions in the project when running locally or in Azure.
-* [local.settings.json](functions-develop-local.md#local-settings-file) - stores app settings and connection strings that are used when running locally. This file contains secrets and isn't published to your function app in Azure. Instead, [add app settings to your function app](functions-develop-vs.md#function-app-settings).
+- [host.json](functions-host-json.md) - stores configuration settings that affect all functions in the project when running locally or in Azure.
+- [local.settings.json](functions-develop-local.md#local-settings-file) - stores app settings and connection strings that are used when running locally. This file contains secrets and isn't published to your function app in Azure. Instead, [add app settings to your function app](functions-develop-vs.md#function-app-settings).
 
 When you build the project, a folder structure that looks like the following example is generated in the build output directory:
 
-```
+```text
 <framework.version>
  | - bin
  | - MyFirstFunction
@@ -110,7 +110,6 @@ This directory is what gets deployed to your function app in Azure. The binding
 > [!IMPORTANT]
 > The build process creates a *function.json* file for each function. This *function.json* file isn't meant to be edited directly. You can't change binding configuration or disable the function by editing this file. To learn how to disable a function, see [How to disable functions](disable-function.md).
 
-
 ## Methods recognized as functions
 
 In a class library, a function is a method with a `FunctionName` and a trigger attribute, as shown in the following example:
@@ -136,16 +135,16 @@ The trigger attribute specifies the trigger type and binds input data to a metho
 
 The method signature might contain parameters other than the one used with the trigger attribute. Here are some of the other parameters that you can include:
 
-* [Input and output bindings](functions-triggers-bindings.md) marked as such by decorating them with attributes.  
-* An `ILogger` or `TraceWriter` ([version 1.x-only](functions-versions.md#creating-1x-apps)) parameter for [logging](#logging).
-* A `CancellationToken` parameter for [graceful shutdown](#cancellation-tokens).
-* [Binding expressions](./functions-bindings-expressions-patterns.md) parameters to get trigger metadata.
+- [Input and output bindings](functions-triggers-bindings.md) marked as such by decorating them with attributes.  
+- An `ILogger` or `TraceWriter` ([version 1.x-only](functions-versions.md#creating-1x-apps)) parameter for [logging](#logging).
+- A `CancellationToken` parameter for [graceful shutdown](#cancellation-tokens).
+- [Binding expressions](./functions-bindings-expressions-patterns.md) parameters to get trigger metadata.
 
 The order of parameters in the function signature doesn't matter. For example, you can put trigger parameters before or after other bindings, and you can put the logger parameter before or after trigger or binding parameters.
 
 ### Output bindings
 
-A function can have zero or multiple output bindings defined by using output parameters. 
+A function can have zero or multiple output bindings defined by using output parameters.
 
 The following example modifies the preceding one by adding an output queue binding named `myQueueItemCopy`. The function writes the contents of the message that triggers the function to a new message in a different queue.
 
@@ -189,7 +188,7 @@ public static class BindingExpressionsExample
 
 ## Autogenerated function.json
 
-The build process creates a *function.json* file in a function folder in the build folder. As noted earlier, this file isn't meant to be edited directly. You can't change binding configuration or disable the function by editing this file. 
+The build process creates a *function.json* file in a function folder in the build folder. As noted earlier, this file isn't meant to be edited directly. You can't change binding configuration or disable the function by editing this file.
 
 The purpose of this file is to provide information to the scale controller to use for [scaling decisions on the Consumption plan](event-driven-scaling.md). For this reason, the file only has trigger info, not input/output bindings.
 
@@ -214,7 +213,7 @@ The generated *function.json* file includes a `configurationSource` property tha
 
 ## Microsoft.NET.Sdk.Functions
 
-The *function.json* file generation is performed by the NuGet package [Microsoft\.NET\.Sdk\.Functions](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions). 
+The *function.json* file generation is performed by the NuGet package [Microsoft\.NET\.Sdk\.Functions](https://www.nuget.org/packages/Microsoft.NET.Sdk.Functions).
 
 The following example shows the relevant parts of the `.csproj` files that have different target frameworks of the same `Sdk` package:
 
@@ -245,7 +244,6 @@ The following example shows the relevant parts of the `.csproj` files that have
 ```
 ---
 
-
 Among the `Sdk` package dependencies are triggers and bindings. A 1.x project refers to 1.x triggers and bindings because those triggers and bindings target the .NET Framework, while 4.x triggers and bindings target .NET Core.
 
 The `Sdk` package also depends on [Newtonsoft.Json](https://www.nuget.org/packages/Newtonsoft.Json), and indirectly on [WindowsAzure.Storage](https://www.nuget.org/packages/WindowsAzure.Storage). These dependencies make sure that your project uses the versions of those packages that work with the Functions runtime version that the project targets. For example, `Newtonsoft.Json` has version 11 for .NET Framework 4.6.1, but the Functions runtime that targets .NET Framework 4.6.1 is only compatible with `Newtonsoft.Json` 9.0.1. So your function code in that project also has to use `Newtonsoft.Json` 9.0.1.
@@ -292,7 +290,7 @@ Each binding has its own supported types; for instance, a blob trigger attribute
 
 ## Binding to method return value
 
-You can use a method return value for an output binding, by applying the attribute to the method return value. For examples, see [Triggers and bindings](./functions-triggers-bindings.md). 
+You can use a method return value for an output binding, by applying the attribute to the method return value. For examples, see [Triggers and bindings](./functions-triggers-bindings.md).
 
 Use the return value only if a successful function execution always results in a return value to pass to the output binding. Otherwise, use `ICollector` or `IAsyncCollector`, as shown in the following section.
 
@@ -452,7 +450,7 @@ Install-Package Microsoft.Azure.WebJobs.Logging.ApplicationInsights -Version <VE
 
 ---
 
-In this command, replace `<VERSION>` with a version of this package that supports your installed version of [Microsoft.Azure.WebJobs](https://www.nuget.org/packages/Microsoft.Azure.WebJobs/). 
+In this command, replace `<VERSION>` with a version of this package that supports your installed version of [Microsoft.Azure.WebJobs](https://www.nuget.org/packages/Microsoft.Azure.WebJobs/).
 
 The following C# examples uses the [custom telemetry API](/azure/azure-monitor/app/api-custom-events-metrics). The example is for a .NET class library, but the Application Insights code is the same for C# script.
 
@@ -530,7 +528,6 @@ In this example, the custom metric data gets aggregated by the host before being
 
 When running locally, you must add the `APPINSIGHTS_INSTRUMENTATIONKEY` setting, with the Application Insights key, to the [local.settings.json](functions-develop-local.md#local-settings-file) file.
 
-
 # [v1.x](#tab/v1)
 
 ```cs
@@ -621,9 +618,9 @@ Don't set `telemetryClient.Context.Operation.Id`. This global setting causes inc
 
 The following articles show how to run an in-process C# class library function locally for testing purposes:
 
-+ [Visual Studio](functions-develop-vs.md#testing-functions)
-+ [Visual Studio Code](functions-develop-vs-code.md?tabs=csharp#debugging-functions-locally)
-+ [Command line](functions-run-local.md?tabs=v4%2Ccsharp%2Cazurecli%2Cbash#start)
+- [Visual Studio](functions-develop-vs.md#testing-functions)
+- [Visual Studio Code](functions-develop-vs-code.md?tabs=csharp#debugging-functions-locally)
+- [Command line](functions-run-local.md?tabs=v4%2Ccsharp%2Cazurecli%2Cbash#start)
 
 ## Environment variables
 
@@ -695,15 +692,11 @@ public static class IBinderExample
 }
 ```
 
-[BlobAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Extensions.Storage/Blobs/BlobAttribute.cs)
-defines the [Storage blob](functions-bindings-storage-blob.md) input or output binding, and
-[TextWriter](/dotnet/api/system.io.textwriter) is a supported output binding type.
+[BlobAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Extensions.Storage/Blobs/BlobAttribute.cs) defines the [Storage blob](functions-bindings-storage-blob.md) input or output binding, and [TextWriter](/dotnet/api/system.io.textwriter) is a supported output binding type.
 
 ### Multiple attributes example
 
-The preceding example gets the app setting for the function app's main Storage account connection string (which is `AzureWebJobsStorage`). You can specify a custom app setting to use for the Storage account by adding the
-[StorageAccountAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs/StorageAccountAttribute.cs)
-and passing the attribute array into `BindAsync<T>()`. Use a `Binder` parameter, not `IBinder`. For example:
+The preceding example gets the app setting for the function app's main Storage account connection string (which is `AzureWebJobsStorage`). You can specify a custom app setting to use for the Storage account by adding the [StorageAccountAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs/StorageAccountAttribute.cs) and passing the attribute array into `BindAsync<T>()`. Use a `Binder` parameter, not `IBinder`. For example:
 
 ```cs
 public static class IBinderExampleMultipleAttributes
@@ -728,7 +721,7 @@ public static class IBinderExampleMultipleAttributes
 }
 ```
 
-## Triggers and bindings 
+## Triggers and bindings
 
 [!INCLUDE [Supported triggers and bindings](../../includes/functions-bindings.md)]