fix: remove misleading note section

locale/en/docs/guides/event-loop-timers-and-nexttick.md

@@ -412,8 +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()`?
 

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()`?

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()`?