Skip to content

Commit 5535387

Browse files
Update articles/azure-functions/dotnet-isolated-process-guide.md
Co-authored-by: Matthew Henderson <[email protected]>
1 parent 013dbe2 commit 5535387

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/dotnet-isolated-process-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -560,8 +560,8 @@ public async Task HandleCancellationCleanup(
560560
The cancellation token is signaled when the function invocation is canceled. Several reasons could lead to a cancellation,
561561
and those could vary depending on the trigger type being used. Some common reasons are:
562562

563-
1. Client Disconnect: the client that is invoking your function disconnected. This is most likely for HttpTrigger functions.
564-
2. Function App Restart: if you, or the platform, restart (or stop) the Function App around the same time an invocation is requested.
563+
1. Client disconnect: the client that is invoking your function disconnected. This is most likely for HttpTrigger functions.
564+
2. Function app restart: if you, or the platform, restart (or stop) the Function App around the same time an invocation is requested.
565565
A restart can occur due to worker instance movements, worker instance updates, or scaling.
566566
- Invocations in-flight during a restart event may be retried depending on how they were triggered. Please refer to the [retry documentation](./functions-bindings-error-pages.md#retries) for further information.
567567

0 commit comments

Comments
 (0)