Skip to content

Commit 16b5314

Browse files
timathonMylesBorins
authored andcommitted
doc: fix link to Event Loop page
PR-URL: #9527 Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
1 parent 2d581f1 commit 16b5314

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/guides/timers-in-node.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ period of time. Timers do not need to be imported via `require()`, since
1010
all the methods are available globally to emulate the browser JavaScript API.
1111
To fully understand when timer functions will be executed, it's a good idea to
1212
read up on the the Node.js
13-
[Event Loop](../topics/event-loop-timers-and-nexttick).
13+
[Event Loop](../topics/event-loop-timers-and-nexttick.md).
1414

1515
## Controlling the Time Continuum with Node.js
1616

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

102102
### "Infinite Loop" Execution ~ *`setInterval()`*

0 commit comments

Comments
 (0)