@@ -10,7 +10,7 @@ period of time. Timers do not need to be imported via `require()`, since
1010all the methods are available globally to emulate the browser JavaScript API.
1111To fully understand when timer functions will be executed, it's a good idea to
1212read up on the the Node.js
13- [ Event Loop] ( ../topics/ event-loop-timers-and-nexttick.md ) .
13+ [ Event Loop] ( /en/docs/guides/ event-loop-timers-and-nexttick/ ) .
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.
9797The second is that ` process.nextTick() ` is non-clearable, meaning once
9898code 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.md #processnexttick)
99+ cannot be stopped, just like with a normal function. Refer to [ this guide] ( /en/docs/guides/ event-loop-timers-and-nexttick/ #processnexttick)
100100to better understand the operation of ` process.nextTick() ` .
101101
102102### "Infinite Loop" Execution ~ * ` setInterval() ` *
@@ -189,4 +189,4 @@ There's much more to the Event Loop and Timers than this guide
189189has covered. To learn more about the internals of the Node.js
190190Event Loop and how Timers operate during execution, check out
191191this Node.js guide: [ The Node.js Event Loop, Timers, and
192- process.nextTick()] ( ../topics/ event-loop-timers-and-nexttick.md ) .
192+ process.nextTick()] ( /en/docs/guides/ event-loop-timers-and-nexttick/ ) .
0 commit comments