Skip to content

Commit ffb7031

Browse files
authored
Merge pull request #46020 from andresnava/patch-3
"Scale-up" -> "Scale-out"
2 parents 2dfd60e + cc402ac commit ffb7031

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ The [Microsoft.Azure.WebJobs.Extensions](https://www.nuget.org/packages/Microsof
2626

2727
## Trigger
2828

29-
The warmup trigger lets you define a function that will be run on an instance when it is added to your running app. You can use a warmup function to open connections, load dependencies, or run any other custom logic before your app will begin receiving traffic.
29+
The warmup trigger lets you define a function that will be run on a new instance when it is added to your running app. You can use a warmup function to open connections, load dependencies, or run any other custom logic before your app will begin receiving traffic.
3030

3131
The warmup trigger is intended to create shared dependencies that will be used by the other functions in your app. [See examples of shared dependencies here](./manage-connections.md#client-code-examples).
3232

33-
Note that the warmup trigger is only called during scale-up operations, not during restarts or other non-scale startups. You must ensure your logic can load all necessary dependencies without using the warmup trigger. Lazy loading is a good pattern to achieve this.
33+
Note that the warmup trigger is only called during scale-out operations, not during restarts or other non-scale startups. You must ensure your logic can load all necessary dependencies without using the warmup trigger. Lazy loading is a good pattern to achieve this.
3434

3535
## Trigger - example
3636

0 commit comments

Comments
 (0)