Skip to content

Commit e0dd476

Browse files
Kevin DonahueMyles Borins
Kevin Donahue
authored and
Myles Borins
committed
doc: fix typos in timers topic to aid readability
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Robert Jefe Lindstaedt <[email protected]>
1 parent a8391bc commit e0dd476

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

doc/topics/the-event-loop-timers-and-nexttick.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -218,15 +218,15 @@ ways depending on when they are called.
218218
* `setTimeout()` schedules a script to be run
219219
after a minimum threshold in ms has elapsed.
220220

221-
The order in which they are execute varies depending on the context in
222-
which they are called. If both are called in the main module then you
223-
are bound to how fast your process go, which is impacted by other
224-
programs running on your machine.
225-
226-
For example, if we run the following script which is not within a I/O
227-
cycle (i.e. the main module), the order in which the two functions are
228-
executed is non-deterministic as it is based upon how fast your process
229-
goes (which is impacted by other programs running on your machine):
221+
The order in which the timers are executed will vary depending on the
222+
context in which they are called. If both are called from within the
223+
main module, then timing will be bound by the performance of the process
224+
(which can be impacted by other applications running on the machine).
225+
226+
For example, if we run the following script which is not within an I/O
227+
cycle (i.e. the main module), the order in which the two timers are
228+
executed is non-deterministic, as it is bound by the performance of the
229+
process:
230230

231231

232232
```js

0 commit comments

Comments
 (0)