Skip to content

Commit ab32b7e

Browse files
minor tweaks
1 parent 0c7f0fe commit ab32b7e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

nservicebus/handlers/async-handlers_apm_core_[,9).partial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ snippet: HandlerWhichIntegratesWithAPM
66

77
### Asynchronous RPC calls
88

9-
The APM approach described above can be used to integrate with remote procedure calls as shown in this snippet:
9+
The APM approach described above can be used to integrate with remote procedure calls, as shown in this snippet:
1010

1111
snippet: HandlerWhichIntegratesWithRemotingWithAPM
1212

@@ -15,4 +15,4 @@ or use [`Task.Run`](https://msdn.microsoft.com/en-us/library/system.threading.ta
1515
snippet: HandlerWhichIntegratesWithRemotingWithTask
1616

1717
> [!NOTE]
18-
> [`Task.Run`](https://msdn.microsoft.com/en-us/library/system.threading.tasks.task.run.aspx) can have significantly less overhead than using a delegate with `BeginInvoke`/`EndInvoke`. By default, both APIs will use the worker thread pool as the underlying scheduling engine. Analyze and measure for the business scenarios involved.
18+
> [`Task.Run`](https://msdn.microsoft.com/en-us/library/system.threading.tasks.task.run.aspx) can have significantly less overhead than using a delegate with `BeginInvoke`/`EndInvoke`. Both APIs will use the worker thread pool as the underlying scheduling engine by default. Analyze and measure the business scenarios involved.

0 commit comments

Comments
 (0)