From d966ad8fa7bef9524d340545dc90fcf65c59ac6b Mon Sep 17 00:00:00 2001
From: Akanksha <160621596+Akankshaaaa-01@users.noreply.github.com>
Date: Fri, 26 Jun 2026 09:42:06 +0530
Subject: [PATCH 1/2] =?UTF-8?q?fix:=20typo=20"Contibute"=20=E2=86=92=20"Co?=
 =?UTF-8?q?ntribute"=20in=20navigation?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Akanksha <160621596+Akankshaaaa-01@users.noreply.github.com>
---
 site.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site.json b/site.json
index 8d8de72..c8f249d 100644
--- a/site.json
+++ b/site.json
@@ -22,7 +22,7 @@
     },
     {
       "link": "https://github.com/nodejs/node/blob/main/CONTRIBUTING.md",
-      "text": "Contibute",
+      "text": "Contribute",
       "target": "_blank"
     },
     {

From 501a592893dde6e92eae8241d11d660be85845cc Mon Sep 17 00:00:00 2001
From: Akanksha <160621596+Akankshaaaa-01@users.noreply.github.com>
Date: Fri, 26 Jun 2026 23:21:27 +0530
Subject: [PATCH 2/2] docs(asynchronous-work): clarify setTimeout() wording

Clarify the wording describing the scheduling of setTimeout(() => {}, 0) relative to process.nextTick().

Signed-off-by: Akanksha <160621596+Akankshaaaa-01@users.noreply.github.com>
---
 pages/asynchronous-work/understanding-processnexttick.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/asynchronous-work/understanding-processnexttick.md b/pages/asynchronous-work/understanding-processnexttick.md
index 634b6dd..290daec 100644
--- a/pages/asynchronous-work/understanding-processnexttick.md
+++ b/pages/asynchronous-work/understanding-processnexttick.md
@@ -19,7 +19,7 @@ The event loop is busy processing the current function code. When this operation
 
 It's the way we can tell the JS engine to process a function asynchronously (after the current function), but as soon as possible, not queue it.
 
-Calling `setTimeout(() => {}, 0)` will execute the function at the end of next tick, much later than when using `nextTick()` which prioritizes the call and executes it just before the beginning of the next tick.
+Calling `setTimeout(() => {}, 0)` schedules the callback for a future event loop iteration, much later than when using `process.nextTick()`, which executes before the event loop continues.
 
 Use `nextTick()` when you want to make sure that in the next event loop iteration that code is already executed.