Skip to content

Commit

Permalink
doc: fix link to Event Loop page
Browse files Browse the repository at this point in the history
PR-URL: #9527
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
  • Loading branch information
timathon authored and MylesBorins committed Dec 21, 2016
1 parent a39a409 commit 2bf61e4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/guides/timers-in-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ period of time. Timers do not need to be imported via `require()`, since
all the methods are available globally to emulate the browser JavaScript API.
To fully understand when timer functions will be executed, it's a good idea to
read up on the the Node.js
[Event Loop](../topics/event-loop-timers-and-nexttick).
[Event Loop](../topics/event-loop-timers-and-nexttick.md).

## Controlling the Time Continuum with Node.js

Expand Down Expand Up @@ -96,7 +96,7 @@ some major ways they differ. The first is that `process.nextTick()` will run
*before* any `Immediate`s that are set as well as before any scheduled I/O.
The second is that `process.nextTick()` is non-clearable, meaning once
code has been scheduled to execute with `process.nextTick()`, the execution
cannot be stopped, just like with a normal function. Refer to [this guide](../topics/event-loop-timers-and-nexttick#processnexttick)
cannot be stopped, just like with a normal function. Refer to [this guide](../topics/event-loop-timers-and-nexttick.md#processnexttick)
to better understand the operation of `process.nextTick()`.

### "Infinite Loop" Execution ~ *`setInterval()`*
Expand Down

0 comments on commit 2bf61e4

Please sign in to comment.