@@ -3283,9 +3283,11 @@ napi_status napi_create_async_work(napi_env env, |
3283 | 3283 | - `[in] async_resource_name`: Identifier for the kind of resource that is |
3284 | 3284 | being provided for diagnostic information exposed by the `async_hooks` API. |
3285 | 3285 | - `[in] execute`: The native function which should be called to excute |
3286 | | -the logic asynchronously. |
| 3286 | +the logic asynchronously. The given function is called from a worker pool |
| 3287 | +thread and can execute in parallel with the main event loop thread. |
3287 | 3288 | - `[in] complete`: The native function which will be called when the |
3288 | | -asynchronous logic is comple or is cancelled. |
| 3289 | +asynchronous logic is completed or is cancelled. The given function is called |
| 3290 | +from the main event loop thread. |
3289 | 3291 | - `[in] data`: User-provided data context. This will be passed back into the |
3290 | 3292 | execute and complete functions. |
3291 | 3293 | - `[out] result`: `napi_async_work*` which is the handle to the newly created |
@@ -3361,9 +3363,9 @@ callback invocation, even if it has been successfully cancelled. |
3361 | 3363 |
|
3362 | 3364 | ## Custom Asynchronous Operations |
3363 | 3365 | The simple asynchronous work APIs above may not be appropriate for every |
3364 | | -scenario, because with those the async execution still happens on the main |
3365 | | -event loop. When using any other async mechanism, the following APIs are |
3366 | | -necessary to ensure an async operation is properly tracked by the runtime. |
| 3366 | +scenario. When using any other asynchronous mechanism, the following APIs |
| 3367 | +are necessary to ensure an asynchronous operation is properly tracked by |
| 3368 | +the runtime. |
3367 | 3369 |
|
3368 | 3370 | ### napi_async_init |
3369 | 3371 | <!-- YAML |
|