Fix blocking issues

ggailey777 · ggailey777 · commit f06efa09cedd · 2024-07-18T02:01:42.000-07:00
diff --git a/articles/azure-functions/function-keys-how-to.md b/articles/azure-functions/function-keys-how-to.md
@@ -3,7 +3,7 @@ title: Work with access keys in Azure Functions
 description: Learn about access keys in Azure Functions, including how to get and renew keys and how to use access keys when calling function endpoints.
 ms.service: azure-functions
 ms.topic: how-to 
-ms.date: 07/07/2024
+ms.date: 07/18/2024
 
 #CustomerIntent: As an Azure Functions developer, I want learn how to work with access keys so that I can properly harden both my function endpoints and my overall function app running in Azure.
 ---
@@ -41,14 +41,14 @@ The following table compares the uses for various kinds of access keys:
 | Execute a function                            | Specific function        | Function           | 
 | Execute a function                            | Any function             | Function or host   | 
 | Call an `admin` endpoint                      | Function app             | Master-only        | 
-| Call Durable Task extension APIs              | Function app<sup>*</sup> | System<sup>2</sup> | 
-| Call an extension-specific Webhook (internal) | Function app<sup>*</sup> | system<sup>2</sup> | 
+| Call Durable Task extension APIs              | Function app<sup>*</sup> | System | 
+| Call an extension-specific Webhook (internal) | Function app<sup>*</sup> | system | 
 
 <sup>*</sup>Scope determined by the extension.  
 
 ## Key requirements
 
-In Functions, access keys are randomly-generated 32-byte arrays that are encoded as URL-safe base-64 strings. While you can generate your own access keys and use them with Functions, we strongly recommend that you instead allow Functions to generate all of your access keys for you. 
+In Functions, access keys are randomly generated 32-byte arrays that are encoded as URL-safe base-64 strings. While you can generate your own access keys and use them with Functions, we strongly recommend that you instead allow Functions to generate all of your access keys for you. 
 
 Functions-generated access keys include special signature and checksum values that indicate the type of access key and that it was generated by Azure Functions. Having these extra components in the key itself makes it much easier to determine the source of these kinds of secrets located during security scanning and other automated processes. 
 
diff --git a/articles/azure-functions/functions-app-settings.md b/articles/azure-functions/functions-app-settings.md
@@ -283,7 +283,7 @@ Specifies the connection string for an Azure Storage account that the Functions
 |---|------------|
 |AzureWebJobsStorage|`DefaultEndpointsProtocol=https;AccountName=...`|
 
-Instead of a connection string, you can use an identity based connection for this storage account. For more information, see [Connecting to host storage with an identity](functions-reference.md#connecting-to-host-storage-with-an-identity).
+Instead of a connection string, you can use an identity-based connection for this storage account. For more information, see [Connecting to host storage with an identity](functions-reference.md#connecting-to-host-storage-with-an-identity).
 
 ## AzureWebJobsStorage__accountName
 
@@ -408,7 +408,8 @@ This app setting is a temporary way for Node.js apps to enable a breaking change
 
 Starting with Node.js v20, the app setting has no effect and the breaking change behavior is always enabled.
 
-For Node.js v18 or lower, the app setting can be used and the default behavior depends on if the error happens before or after a model v4 function has been registered:
+For Node.js v18 or lower, the app setting is used, and the default behavior depends on if the error happens before or after a model v4 function has been registered:
+
 - If the error is thrown before (for example if you're using model v3 or your entry point file doesn't exist), the default behavior matches `false`.
 - If the error is thrown after (for example if you try to register duplicate model v4 functions), the default behavior matches `true`.
 
@@ -553,7 +554,7 @@ The configuration is specific to Python function apps. It defines the prioritiza
 |PYTHON\_ISOLATE\_WORKER\_DEPENDENCIES|`1`| Prioritize loading the Python libraries from application's package defined in requirements.txt. This prevents your libraries from colliding with internal Python worker's libraries. |
 
 ## PYTHON_ENABLE_DEBUG_LOGGING
-Enables debug-level logging in a Python function app. A value of `1` enables debug-level logging. Without this setting or with a value of `0`, only information and higher level logs are sent from the Python worker to the Functions host. Use this setting when debugging or tracing your Python function executions.
+Enables debug-level logging in a Python function app. A value of `1` enables debug-level logging. Without this setting or with a value of `0`, only information and higher-level logs are sent from the Python worker to the Functions host. Use this setting when debugging or tracing your Python function executions.
 
 When debugging Python functions, make sure to also set a debug or trace [logging level](functions-host-json.md#logging) in the host.json file, as needed. To learn more, see [How to configure monitoring for Azure Functions](configure-monitoring.md).
 
@@ -793,7 +794,7 @@ Some configurations must be maintained at the App Service level as site settings
 
 ### alwaysOn
 
-On a function app running in a [Dedicated (App Service) plan](./dedicated-plan.md), the functions runtime goes idle after a few minutes of inactivity, a which point only requests to an HTTP triggers _wakes-up_ your functions. To make sure that your non-HTTP triggered functions run correctly, including Timer trigger, enable Always On for the function app by setting the `alwaysOn` site setting to a value of `true`. 
+On a function app running in a [Dedicated (App Service) plan](./dedicated-plan.md), the functions runtime goes idle after a few minutes of inactivity, at which point only a request to an HTTP trigger _wakes up_ your function. To make sure that your non-HTTP triggered functions run correctly, including Timer trigger, enable Always On for the function app by setting the `alwaysOn` site setting to a value of `true`. 
 
 ### linuxFxVersion 
 
@@ -884,7 +885,7 @@ In the [Flex Consumption plan](./flex-consumption-plan.md), these site propertie
 | `properties.use32BitWorkerProcess` |32-bit not supported |
 | `properties.vnetBackupRestoreEnabled` |Not used for networking in Flex Consumption|
 | `properties.vnetContentShareEnabled` |Not used for networking in Flex Consumption|
-| `properties.vnetImagePullEnabled` |Not used for networking in Flex Consumptionlid|
+| `properties.vnetImagePullEnabled` |Not used for networking in Flex Consumption|
 | `properties.vnetRouteAllEnabled` |Not used for networking in Flex Consumption|
 | `properties.windowsFxVersion` |Not valid|
 
diff --git a/articles/azure-functions/functions-bindings-http-webhook-trigger.md b/articles/azure-functions/functions-bindings-http-webhook-trigger.md
@@ -654,9 +654,9 @@ The trigger input type is declared as one of the following types:
 |-|-|
 | [HttpRequest]     | _Use of this type requires that the app is configured with [ASP.NET Core integration in .NET Isolated]._<br/>This gives you full access to the request object and overall HttpContext. |
 | [HttpRequestData] | A projection of the request object. |
-| A custom type     | When the body of the request is JSON, the runtime will try to parse it to set the object properties. |
+| A custom type     | When the body of the request is JSON, the runtime tries to parse it to set the object properties. |
 
-When the trigger parameter is an `HttpRequestData`  an `HttpRequest`, custom types can also be bound to other parameters using `Microsoft.Azure.Functions.Worker.Http.FromBodyAttribute`. Use of this attribute requires [`Microsoft.Azure.Functions.Worker.Extensions.Http` version 3.1.0 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.Http). This is a different type than the similar attribute in `Microsoft.AspNetCore.Mvc`, and when using ASP.NET Core integration, you'll need a fully qualified reference or `using` statement. The following example shows how to use the attribute to get just the body contents while still having access to the full `HttpRequest`, using the ASP.NET Core integration:
+When the trigger parameter is of type `HttpRequestData` or `HttpRequest`, custom types can also be bound to other parameters using `Microsoft.Azure.Functions.Worker.Http.FromBodyAttribute`. Use of this attribute requires [`Microsoft.Azure.Functions.Worker.Extensions.Http` version 3.1.0 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.Http). This is a different type than the similar attribute in `Microsoft.AspNetCore.Mvc`. When using ASP.NET Core integration, you need a fully-qualified reference or `using` statement. This example shows how to use the attribute to get just the body contents while still having access to the full `HttpRequest`, using ASP.NET Core integration:
 
 ```csharp
 using Microsoft.AspNetCore.Http;
diff --git a/articles/azure-functions/functions-core-tools-reference.md b/articles/azure-functions/functions-core-tools-reference.md
@@ -226,7 +226,7 @@ The following publish options apply, based on version:
 
 | Option     | Description                            |
 | ------------ | -------------------------------------- |
-| **`--access-token`** | Lets you use a specific access token when performing authenticated azure actions. |
+| **`--access-token`** | Lets you use a specific access token when performing authenticated `azure` actions. |
 | **`--access-token-stdin `** | Reads a specific access token from a standard input. Use this when reading the token directly from a previous command such as [`az account get-access-token`](/cli/azure/account#az-account-get-access-token). |
 | **`--additional-packages`** | List of packages to install when building native dependencies. For example: `python3-dev libevent-dev`. |
 | **`--build`**, **`-b`** | Performs build action when deploying to a Linux function app. Accepts: `remote` and `local`. |
@@ -278,7 +278,7 @@ The following deployment options apply:
 
 | Option     | Description                            |
 | ------------ | -------------------------------------- |
-| **`--access-token`** | Lets you use a specific access token when performing authenticated azure actions. |
+| **`--access-token`** | Lets you use a specific access token when performing authenticated `azure` actions. |
 | **`--access-token-stdin `** | Reads a specific access token from a standard input. Use this when reading the token directly from a previous command such as [`az account get-access-token`](/cli/azure/account#az-account-get-access-token). |
 | **`--environment`** | The name of an existing Container Apps environment.| 
 | **`--image-build`** | When set to `true`, skips the local Docker build. |
diff --git a/articles/azure-functions/functions-deployment-technologies.md b/articles/azure-functions/functions-deployment-technologies.md
@@ -56,7 +56,7 @@ Some key concepts are critical to understanding how deployments work in Azure Fu
 
 When you change any of your triggers, the Functions infrastructure must be aware of the changes. Synchronization happens automatically for many deployment technologies. However, in some cases, you must manually sync your triggers. 
 
-You must manually sync triggers when using these deploymention options:
+You must manually sync triggers when using these deployment options:
 
 + [External package URL](#external-package-url)
 + [Local Git](#local-git)
diff --git a/articles/azure-functions/functions-infrastructure-as-code.md b/articles/azure-functions/functions-infrastructure-as-code.md
@@ -54,8 +54,8 @@ You must create or configure these resources for an Azure Functions-hosted deplo
 | Resource  | Requirement | Syntax and properties reference |
 |------|-------|----|
 | A [storage account](#create-storage-account) | Required | [Microsoft.Storage/storageAccounts](/azure/templates/microsoft.storage/storageaccounts) |
-| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>1</sup>|  
-| A [hosting plan](#create-the-hosting-plan)| Required<sup>2</sup> | [Microsoft.Web/serverfarms](/azure/templates/microsoft.web/serverfarms) |
+| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>*1*</sup>|  
+| A [hosting plan](#create-the-hosting-plan)| Required | [Microsoft.Web/serverfarms](/azure/templates/microsoft.web/serverfarms) |
 | A [function app](#create-the-function-app) | Required | [Microsoft.Web/sites](/azure/templates/microsoft.web/sites)  |
 :::zone-end    
 :::zone pivot="consumption-plan"  
@@ -64,7 +64,7 @@ You must create or configure these resources for an Azure Functions-hosted deplo
 | Resource  | Requirement | Syntax and properties reference |
 |------|-------|----|
 | A [storage account](#create-storage-account) | Required | [Microsoft.Storage/storageAccounts](/azure/templates/microsoft.storage/storageaccounts) |
-| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>1</sup>|  
+| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>*</sup>|  
 | A [function app](#create-the-function-app) | Required | [Microsoft.Web/sites](/azure/templates/microsoft.web/sites)  |
 :::zone-end  
 :::zone pivot="container-apps"  
@@ -73,7 +73,7 @@ An Azure Container Apps-hosted deployment typically consists of these resources:
 | Resource  | Requirement | Syntax and properties reference |
 |------|-------|----|
 | A [storage account](#create-storage-account) | Required | [Microsoft.Storage/storageAccounts](/azure/templates/microsoft.storage/storageaccounts) |
-| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>1</sup>|  
+| An [Application Insights](#create-application-insights) component | Recommended | [Microsoft.Insights/components](/azure/templates/microsoft.insights/components)<sup>*</sup>|  
 | A [managed environment](./functions-container-apps-hosting.md#) | Required | [Microsoft.App/managedEnvironments](/azure/templates/microsoft.app/managedenvironments) |
 | A [function app](#create-the-function-app) | Required | [Microsoft.Web/sites](/azure/templates/microsoft.web/sites)  |
 :::zone-end  
@@ -87,10 +87,7 @@ An Azure Arc-hosted deployment typically consists of these resources:
 | An [App Service Kubernetes environment](../app-service/overview-arc-integration.md#app-service-kubernetes-environment) | Required | [Microsoft.ExtendedLocation/customLocations](/azure/templates/microsoft.extendedlocation/customlocations) |
 | A [function app](#create-the-function-app) | Required | [Microsoft.Web/sites](/azure/templates/microsoft.web/sites)  |
 :::zone-end  
-:::zone pivot="premium-plan,dedicated-plan,flex-consumption-plan" 
-1. If you don't already have a Log Analytics Workspace that can be used by your Application Insights instance, you also need to create this resource.   
-2. An explicit hosting plan isn't required when you choose to host your function app in a [Consumption plan](./consumption-plan.md).
-:::zone-end  
+<sup>*</sup>If you don't already have a Log Analytics Workspace that can be used by your Application Insights instance, you also need to create this resource.   
 
 When you deploy multiple resources in a single Bicep file or ARM template, the order in which resources are created is important. This requirement is a result of dependencies between resources. For such dependencies, make sure to use the `dependsOn` element to define the dependency in the dependent resource. For more information, see either [Define the order for deploying resources in ARM templates](../azure-resource-manager/templates/resource-dependency.md) or [Resource dependencies in Bicep](../azure-resource-manager/bicep/resource-dependencies.md). 
 
@@ -325,7 +322,7 @@ This example section creates Flex Consumption plan:
 
 For more context, see the complete [function.bicep](https://github.com/Azure-Samples/azure-functions-flex-consumption-samples/blob/main/IaC/bicep/core/host/function.bicep#L21) file in the Flex Consumption plan sample repository.
 
-### [ARM Template](#tab/json)
+### [ARM template](#tab/json)
 
 :::code language="json" source="~/function-flex-consumption/IaC/armtemplate/azuredeploy.json" range="136-149" :::
 
diff --git a/articles/azure-functions/functions-run-local.md b/articles/azure-functions/functions-run-local.md
@@ -497,7 +497,7 @@ When the settings file is encrypted and decrypted, the file's `IsEncrypted` sett
 [Functions triggers and bindings](functions-triggers-bindings.md) are implemented as .NET extension (NuGet) packages. To be able to use a specific binding extension, that extension must be installed in the project.
 
 ::: zone pivot="programming-language-javascript,programming-language-csharp"
-This section doesn't apply to version 1.x of the Functions runtime. In version 1.x, supported binding were included in the core product extension.
+This section doesn't apply to version 1.x of the Functions runtime. In version 1.x, supported bindings were included in the core product extension.
 ::: zone-end
 
 ::: zone pivot="programming-language-csharp"
diff --git a/articles/azure-functions/security-concepts.md b/articles/azure-functions/security-concepts.md
