Acrolinx suggestions

Author: castrodd

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

@@ -12,15 +12,15 @@ zone_pivot_groups: programming-languages-set-functions
 
 # Azure Functions warmup trigger
 
-This article explains how to work with the warmup trigger in Azure Functions. A warmup trigger is invoked when an instance is added to scale a running function app. The warmup trigger lets you define a function that's run when a new instance of your function app is started. You can use a warmup trigger to pre-load custom dependencies during the pre-warming process so your functions are ready to start processing requests immediately. Some actions for a warmup trigger might include opening connections, loading dependencies, or running any other custom logic before your app begins receiving traffic.
+This article explains how to work with the warmup trigger in Azure Functions. A warmup trigger is invoked when an instance is added to scale a running function app. The warmup trigger lets you define a function that runs when a new instance of your function app is started. You can use a warmup trigger to preload custom dependencies so your functions are ready to start processing requests immediately. Some actions for a warmup trigger might include opening connections, loading dependencies, or running any other custom logic before your app begins receiving traffic.
 
 The following considerations apply when using a warmup trigger:
 
 * The warmup trigger isn't available to apps running on the [Consumption plan](./consumption-plan.md).
 * The warmup trigger isn't supported on version 1.x of the Functions runtime.  
 * Support for the warmup trigger is provided by default in all development environments. You don't have to manually install the package or register the extension.
 * There can be only one warmup trigger function per function app, and it can't be invoked after the instance is already running.
-* The warmup trigger is only called during scale-out operations, not during restarts or other non-scale startups. Make sure your logic can load all required dependencies without relying on the warmup trigger. Lazy loading is a good pattern to achieve this goal.
+* The warmup trigger is only called during scale-out operations, not during restarts or other nonscaling startups. Make sure your logic can load all required dependencies without relying on the warmup trigger. Lazy loading is a good pattern to achieve this goal.
 * Dependencies created by warmup trigger should be shared with other functions in your app. To learn more, see [Static clients](manage-connections.md#static-clients).
 * If the [built-in authentication](../app-service/overview-authentication-authorization.md) (aka Easy Auth) is used, [HTTPS Only](../app-service/configure-ssl-bindings.md#enforce-https) should be enabled for the warmup trigger to get invoked.
 
@@ -34,13 +34,13 @@ The following considerations apply when using a warmup trigger:
 
 # [Isolated worker model](#tab/isolated-process)
 
-The following example shows a [C# function](dotnet-isolated-process-guide.md) that runs on each new instance when it's added to your app. 
+The following example shows a [C# function](dotnet-isolated-process-guide.md) that runs on each new instance when added to your app. 
 
 :::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/Warmup/Warmup.cs" range="4-18":::
 
 # [In-process model](#tab/in-process)
 
-The following example shows a [C# function](functions-dotnet-class-library.md) that runs on each new instance when it's added to your app. 
+The following example shows a [C# function](functions-dotnet-class-library.md) that runs on each new instance when added to your app. 
 
 ```cs
 using Microsoft.Azure.WebJobs;
@@ -84,7 +84,7 @@ public void warmup( @WarmupTrigger Object warmupContext, ExecutionContext contex
 
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows a warmup trigger [JavaScript function](functions-reference-node.md) that runs on each new instance when it's added to your app.
+The following example shows a warmup trigger [JavaScript function](functions-reference-node.md) that runs on each new instance when added to your app.
 
 ```javascript
 import { app } from "@azure/functions";
@@ -98,7 +98,7 @@ app.warmup('warmupTrigger1', {
 
 # [Model v3](#tab/nodejs-v3)
 
-The following example shows a warmup trigger in a *function.json* file and a [JavaScript function](functions-reference-node.md) that runs on each new instance when it's added to your app.
+The following example shows a warmup trigger in a *function.json* file and a [JavaScript function](functions-reference-node.md) that runs on each new instance when added to your app.
 
 Here's the *function.json* file:
 
@@ -128,7 +128,7 @@ module.exports = async function (warmupContext, context) {
 ::: zone pivot="programming-language-typescript"
 # [Model v4](#tab/nodejs-v4)
 
-The following example shows a warmup trigger [JavaScript function](functions-reference-node.md) that runs on each new instance when it's added to your app.
+The following example shows a warmup trigger [JavaScript function](functions-reference-node.md) that runs on each new instance when added to your app.
 
 ```TypeScript
 import { app, InvocationContext, WarmupContextOptions } from "@azure/functions";
@@ -218,15 +218,15 @@ Use the `WarmupTrigger` attribute to define the function. This attribute has no
 ::: zone pivot="programming-language-java"  
 ## Annotations
 
-Annotations aren't required by a warmup trigger. Just use a name of `warmup` (case-insensitive) for the `FunctionName` annotation.
+Warmup triggers do not require annotations. Just use a name of `warmup` (case-insensitive) for the `FunctionName` annotation.
 
 ::: zone-end  
 ::: zone pivot="programming-language-javascript,programming-language-typescript"  
 ## Configuration
 
 # [Model v4](#tab/nodejs-v4)
 
-There are no additional properties that need to be set on the `options` object passed to the `app.warmup()` method.
+There are no properties that need to be set on the `options` object passed to the `app.warmup()` method.
 
 # [Model v3](#tab/nodejs-v3)
 
@@ -281,7 +281,7 @@ Your function must be named `warmup` (case-insensitive) using the `FunctionName`
 ::: zone-end
 ::: zone pivot="programming-language-javascript,programming-language-typescript"
 # [Model v4](#tab/nodejs-v4)
-Please see the list of considerations at the top of the page for general usage advice.
+See the list of considerations at the top of the page for general usage advice.
 # [Model v3](#tab/nodejs-v3)
 The function type in _function.json_ must be set to `warmupTrigger`.
 ::: zone-end