From c7737f84b39f911705d6dd91b44a9e5e96327532 Mon Sep 17 00:00:00 2001 From: Vse Mozhet Byt Date: Mon, 18 Sep 2017 00:02:03 +0300 Subject: [PATCH] doc: fix some links in guides --- locale/en/docs/guides/backpressuring-in-streams.md | 2 +- locale/en/docs/guides/timers-in-node.md | 2 +- locale/ko/docs/guides/timers-in-node.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/locale/en/docs/guides/backpressuring-in-streams.md b/locale/en/docs/guides/backpressuring-in-streams.md index 38c351d1b9beb..04b02365f463a 100644 --- a/locale/en/docs/guides/backpressuring-in-streams.md +++ b/locale/en/docs/guides/backpressuring-in-streams.md @@ -548,7 +548,7 @@ Node.js. [`Transform`]: https://nodejs.org/api/stream.html#stream_duplex_and_transform_streams [`zlib`]: https://nodejs.org/api/zlib.html [`.drain()`]: https://nodejs.org/api/stream.html#stream_event_drain -[`.data` event]: https://nodejs.org/api/stream.html#event-data +[`.data` event]: https://nodejs.org/api/stream.html#stream_event_data [`.read()`]: https://nodejs.org/docs/latest/api/stream.html#stream_readable_read_size [`.write()`]: https://nodejs.org/api/stream.html#stream_writable_write_chunk_encoding_callback [`._read()`]: https://nodejs.org/docs/latest/api/stream.html#stream_readable_read_size_1 diff --git a/locale/en/docs/guides/timers-in-node.md b/locale/en/docs/guides/timers-in-node.md index 923cc8349bc7e..0f0cd2881ede8 100644 --- a/locale/en/docs/guides/timers-in-node.md +++ b/locale/en/docs/guides/timers-in-node.md @@ -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](/en/docs/guides/event-loop-timers-and-nexttick/#processnexttick) +cannot be stopped, just like with a normal function. Refer to [this guide](/en/docs/guides/event-loop-timers-and-nexttick/#process-nexttick) to better understand the operation of `process.nextTick()`. ### "Infinite Loop" Execution ~ *`setInterval()`* diff --git a/locale/ko/docs/guides/timers-in-node.md b/locale/ko/docs/guides/timers-in-node.md index d2c96e59c66c8..e83829e58d518 100644 --- a/locale/ko/docs/guides/timers-in-node.md +++ b/locale/ko/docs/guides/timers-in-node.md @@ -171,7 +171,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](/en/docs/guides/event-loop-timers-and-nexttick/#processnexttick) +cannot be stopped, just like with a normal function. Refer to [this guide](/en/docs/guides/event-loop-timers-and-nexttick/#process-nexttick) to better understand the operation of `process.nextTick()`. --> @@ -191,7 +191,7 @@ Note: `setImmediate()`를 `process.nextTick()`와 혼동하지 마세요. 서로 `Immediate` *이전에* 실행될 것입니다. 두 번째로 `process.nextTick()`은 취소할 수 없으므로 일단 `process.nextTick()`으로 코드를 실행하도록 스케줄링하면 일반 함수처럼 실행을 멈출 수 없습니다. `process.nextTick()`의 동작을 더 이해하려면 -[이 가이드 문서](/en/docs/guides/event-loop-timers-and-nexttick/#processnexttick)를 +[이 가이드 문서](/en/docs/guides/event-loop-timers-and-nexttick/#process-nexttick)를 참고하세요.