From 9fa6e445d5dd59328399afdf476dab35845d75e7 Mon Sep 17 00:00:00 2001
From: Xuguang Mei <meixg@foxmail.com>
Date: Thu, 10 Mar 2022 10:14:59 +0800
Subject: [PATCH] doc: remove outdated timeout.unref content

resolve: https://github.com/nodejs/node/issues/42239

PR-URL: https://github.com/nodejs/node/pull/42241
Fixes: https://github.com/nodejs/node/issues/42239
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Mestery <mestery@protonmail.com>
---
 doc/api/timers.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/api/timers.md b/doc/api/timers.md
index f3612470c7569f..decb2c1561645a 100644
--- a/doc/api/timers.md
+++ b/doc/api/timers.md
@@ -140,10 +140,6 @@ to remain active. If there is no other activity keeping the event loop running,
 the process may exit before the `Timeout` object's callback is invoked. Calling
 `timeout.unref()` multiple times will have no effect.
 
-Calling `timeout.unref()` creates an internal timer that will wake the Node.js
-event loop. Creating too many of these can adversely impact performance
-of the Node.js application.
-
 ### `timeout[Symbol.toPrimitive]()`
 
 <!-- YAML