From 345ee273654b95595fb254b177a98171aa101b2f Mon Sep 17 00:00:00 2001
From: Ahmet ULKU <96921013+ahhmettulku@users.noreply.github.com>
Date: Sun, 1 Feb 2026 00:05:06 +0300
Subject: [PATCH] Update description of process.nextTick() behavior
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Clarify the explanation of process.nextTick() in relation to the event loop:
The phrase “before moving to the next phase” may be misleading, as it can imply that process.nextTick() waits for the current event-loop phase to complete. In reality, process.nextTick() callbacks run immediately after the current call stack empties, it doesn't wait for the current phase to end.

Signed-off-by: Ahmet ULKU <96921013+ahhmettulku@users.noreply.github.com>
---
 .../en/learn/asynchronous-work/understanding-processnexttick.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md b/apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md
index 2b71a57b2eb2e..9b1926b57cdfd 100644
--- a/apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md
+++ b/apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md
@@ -9,7 +9,7 @@ authors: flaviocopes, MylesBorins, LaRuaNa, ahmadawais, ovflowd, marksist300
 As you try to understand the Node.js event loop, one important part of it is `process.nextTick()`.
 Every time the runtime calls back into JavaScript for an event, we call it a tick.
 
-When we pass a function to `process.nextTick()`, we instruct the engine to invoke this function immediately after the current operation completes, before moving to the next phase in the event loop:
+When we pass a function to `process.nextTick()`, we schedule it to run immediately after the current call stack completes, before the event loop continues and before any other queued tasks or phases are processed:
 
 ```js
 process.nextTick(() => {