From 62478eb3d97243e2c7f71b64c23b4ac0a0dfb012 Mon Sep 17 00:00:00 2001 From: timathon Date: Wed, 9 Nov 2016 12:07:49 +0800 Subject: [PATCH] doc: fix link to Event Loop page PR-URL: https://github.com/nodejs/node/pull/9527 Reviewed-By: Roman Reiss Reviewed-By: Colin Ihrig --- doc/guides/timers-in-node.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/timers-in-node.md b/doc/guides/timers-in-node.md index 6cdbd35b21ffa7..818cc793437cad 100644 --- a/doc/guides/timers-in-node.md +++ b/doc/guides/timers-in-node.md @@ -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 @@ -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()`*