Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: fix typos in event loop doc to aid readability #6916

Closed
wants to merge 2 commits into from
Closed

doc: fix typos in event loop doc to aid readability #6916

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
183ba32
doc: fix typos in event loop doc to aid readability
May 21, 2016
83a6f22
doc: remove possessive language from `setImmediate` vs `setTimeout`
May 23, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
doc: remove possessive language from setImmediate vs setTimeout 
Use 'the process' instead of 'your process'.
  • Loading branch information
Kevin Donahue committed May 23, 2016
commit 83a6f226b6a768793cac7a9e8eccd49cc8e8a847
18 changes: 9 additions & 9 deletions doc/topics/the-event-loop-timers-and-nexttick.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 executed varies depending on the context in
which they are called. If both are called in the main module, then you
are bound by 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 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):
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 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
Expand Down