1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: fix typos in timers topic to aid readability

Browse Source 
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:
Kevin Donahue 2016-05-21 11:19:36 -04:00 committed by Robert Jefe Lindstaedt
parent 20501275d3
commit af61ebf6e2
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -218,15 +218,15 @@ ways depending on when they are called.
* `setTimeout()` schedules a script to be run * `setTimeout()` schedules a script to be run
after a minimum threshold in ms has elapsed. after a minimum threshold in ms has elapsed.
The order in which they are execute varies depending on the context in The order in which the timers are executed will vary depending on the
which they are called. If both are called in the main module then you context in which they are called. If both are called from within the
are bound to how fast your process go, which is impacted by other main module, then timing will be bound by the performance of the process
programs running on your machine. (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 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 functions are cycle (i.e. the main module), the order in which the two timers are
executed is non-deterministic as it is based upon how fast your process executed is non-deterministic, as it is bound by the performance of the
goes (which is impacted by other programs running on your machine): process:
```js ```js