From 882860f6a345f3c3a7c2d82177a697beeef05ea9 Mon Sep 17 00:00:00 2001
From: Sergey Zhigunov <i.sergey.zhigunov@gmail.com>
Date: Fri, 20 Dec 2019 00:08:41 +0200
Subject: [PATCH 1/3] fix: remove misleading note section

Fixes: https://github.com/nodejs/node/issues/30801
---
 locale/en/docs/guides/event-loop-timers-and-nexttick.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/locale/en/docs/guides/event-loop-timers-and-nexttick.md b/locale/en/docs/guides/event-loop-timers-and-nexttick.md
index 921aaae6cd54d..3ef636ac29185 100644
--- a/locale/en/docs/guides/event-loop-timers-and-nexttick.md
+++ b/locale/en/docs/guides/event-loop-timers-and-nexttick.md
@@ -412,9 +412,7 @@ added, which means every day we wait, more potential breakages occur.
 While they are confusing, the names themselves won't change.
 
 *We recommend developers use `setImmediate()` in all cases because it's
-easier to reason about (and it leads to code that's compatible with a
-wider variety of environments, like browser JS.)*
-
+easier to reason about.*
 ## Why use `process.nextTick()`?
 
 There are two main reasons:

From a14b26fd4c2fb8629efdc2393be7b3770f5769bb Mon Sep 17 00:00:00 2001
From: Sergey Zhigunov <i.sergey.zhigunov@gmail.com>
Date: Fri, 20 Dec 2019 00:09:20 +0200
Subject: [PATCH 2/3] fix: remove misleading note section (ko, zh-cn)

---
 locale/ko/docs/guides/event-loop-timers-and-nexttick.md    | 2 +-
 locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/locale/ko/docs/guides/event-loop-timers-and-nexttick.md b/locale/ko/docs/guides/event-loop-timers-and-nexttick.md
index 9dd32c7f3eb63..cecb9f9e8fe4b 100644
--- a/locale/ko/docs/guides/event-loop-timers-and-nexttick.md
+++ b/locale/ko/docs/guides/event-loop-timers-and-nexttick.md
@@ -803,7 +803,7 @@ wider variety of environments, like browser JS.)*
 이 둘은 혼란스럽지만 이름이 바뀌진 않을 것입니다.
 
 *`setImmediate()`가 예상하기 더 쉬우므로 모든 경우에 `setImmediate()`를 사용하기를
-권장합니다.(이 방법이 브라우저 자바스크립트 등 더 넓은 범위의 환경과 호환될 것입니다.)*
+권장합니다.*
 
 <!--
 ## Why use `process.nextTick()`?
diff --git a/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md b/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md
index f8f3f5e7247d3..23f5e7e98871e 100644
--- a/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md
+++ b/locale/zh-cn/docs/guides/event-loop-timers-and-nexttick.md
@@ -275,7 +275,7 @@ server.on('listening', () => {});
 
 实质上，这两个名称应该交换，因为 `process.nextTick()` 比 `setImmediate()` 触发得更快，但这是过去遗留问题，因此不太可能改变。如果贸然进行名称交换，将破坏 npm 上的大部分软件包。每天都有更多新的模块在增加，这意味着我们要多等待每一天，则更多潜在破坏会发生。尽管这些名称使人感到困惑，但它们本身名字不会改变。
 
-*我们建议开发人员在所有情况下都使用 `setImmediate()`，因为它更容易理解（ 而且它可以让代码与各种环境兼容，比如浏览器 JS ）*
+*我们建议开发人员在所有情况下都使用 `setImmediate()`，因为它更容易理解。*
 
 ## 为什么要使用 `process.nextTick()`?
 

From 51ca2edbd305f9c0423b32f18e90b42ae6508c33 Mon Sep 17 00:00:00 2001
From: Maledong <52018749+MaledongGit@users.noreply.github.com>
Date: Mon, 23 Dec 2019 12:34:49 +0800
Subject: [PATCH 3/3] update: add a missing newline

add a missing newline
---
 locale/en/docs/guides/event-loop-timers-and-nexttick.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/locale/en/docs/guides/event-loop-timers-and-nexttick.md b/locale/en/docs/guides/event-loop-timers-and-nexttick.md
index 3ef636ac29185..26540519e2538 100644
--- a/locale/en/docs/guides/event-loop-timers-and-nexttick.md
+++ b/locale/en/docs/guides/event-loop-timers-and-nexttick.md
@@ -413,6 +413,7 @@ While they are confusing, the names themselves won't change.
 
 *We recommend developers use `setImmediate()` in all cases because it's
 easier to reason about.*
+
 ## Why use `process.nextTick()`?
 
 There are two main reasons: