doc: fix typos in timers topic to aid readability
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: https://github.com/nodejs/node/pull/6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
This commit is contained in:
parent
20501275d3
commit
af61ebf6e2
@ -218,15 +218,15 @@ ways depending on when they are called.
|
||||
* `setTimeout()` schedules a script to be run
|
||||
after a minimum threshold in ms has elapsed.
|
||||
|
||||
The order in which they are execute varies depending on the context in
|
||||
which they are called. If both are called in the main module then you
|
||||
are bound to how fast your process go, which is impacted by other
|
||||
programs running on your machine.
|
||||
The order in which the timers are executed will vary depending on the
|
||||
context in which they are called. If both are called from within the
|
||||
main module, then timing will be bound by the performance of the process
|
||||
(which can be impacted by other applications running on the machine).
|
||||
|
||||
For example, if we run the following script which is not within a I/O
|
||||
cycle (i.e. the main module), the order in which the two functions are
|
||||
executed is non-deterministic as it is based upon how fast your process
|
||||
goes (which is impacted by other programs running on your machine):
|
||||
For example, if we run the following script which is not within an I/O
|
||||
cycle (i.e. the main module), the order in which the two timers are
|
||||
executed is non-deterministic, as it is bound by the performance of the
|
||||
process:
|
||||
|
||||
|
||||
```js
|
||||
|
Loading…
x
Reference in New Issue
Block a user