Skip to content

Commit 5ed4b89

Browse files
devsnekjasnell
authored andcommitted
doc: fix confusing language about microtask queue
PR-URL: #23197 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
1 parent 0adca98 commit 5ed4b89

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/api/globals.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,8 @@ The `queueMicrotask()` method queues a microtask to invoke `callback`. If
123123
be emitted.
124124

125125
In general, `queueMicrotask` is the idiomatic choice over `process.nextTick()`.
126-
`process.nextTick()` will always run before microtasks, and so unexpected
127-
execution order may be observed.
126+
`process.nextTick()` will always run before the microtask queue, and so
127+
unexpected execution order may be observed.
128128

129129
```js
130130
// Here, `queueMicrotask()` is used to ensure the 'load' event is always

0 commit comments

Comments
 (0)