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

liliankasem · mattchenderson · web-flow · commit 09717c37798a · 2025-02-26T13:36:04.000-08:00
Co-authored-by: Matthew Henderson &lt;mattchenderson@users.noreply.github.com&gt;
diff --git a/articles/azure-functions/dotnet-isolated-process-guide.md b/articles/azure-functions/dotnet-isolated-process-guide.md
@@ -567,7 +567,7 @@ and those could vary depending on the trigger type being used. Some common reaso
 
 For the isolated worker model, the host we will send the invocation through to the worker _even_ if the cancellation token was cancelled _before_ the host is able to send the invocation request to the worker.
 
-If you do not want pre-cancelled invocations to be sent to the worker, you can add the following property to your host.json file to disable this behaviour.
+If you do not want pre-cancelled invocations to be sent to the worker, you can add the `SendCanceledInvocationsToWorker` property to your `host.json` file to disable this behaviour. The following example shows a `host.json` file that uses this property:
 
 ```json
 {

Original file line number	Diff line number	Diff line change
`@@ -567,7 +567,7 @@ and those could vary depending on the trigger type being used. Some common reaso`
`567`	`567`
`568`	`568`	`For the isolated worker model, the host we will send the invocation through to the worker _even_ if the cancellation token was cancelled _before_ the host is able to send the invocation request to the worker.`
`569`	`569`
`570`		`-If you do not want pre-cancelled invocations to be sent to the worker, you can add the following property to your host.json file to disable this behaviour.`
	`570`	+If you do not want pre-cancelled invocations to be sent to the worker, you can add the `SendCanceledInvocationsToWorker` property to your `host.json` file to disable this behaviour. The following example shows a `host.json` file that uses this property:
`571`	`571`
`572`	`572`	```json
`573`	`573`	`{`