Skip to content

Commit

Permalink
doc: fix some links in guides (#1363)
Browse files Browse the repository at this point in the history
  • Loading branch information
vsemozhetbyt authored and fhemberger committed Sep 18, 2017
1 parent babfc66 commit 98c1cb3
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion locale/en/docs/guides/backpressuring-in-streams.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion locale/en/docs/guides/timers-in-node.md
Original file line number Diff line number Diff line change
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](/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()`*
Expand Down
4 changes: 2 additions & 2 deletions locale/ko/docs/guides/timers-in-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -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()`.
-->

Expand All @@ -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)
참고하세요.

<!--
Expand Down

0 comments on commit 98c1cb3

Please sign in to comment.