docs(asynchronous-work): clarify setImmediate() behavior

[raj-aayush01]

The documentation currently states that setImmediate() is equivalent to setTimeout(() => {}, 0).

This change clarifies that they are not generally equivalent because their callbacks execute in different phases of the event loop, and their execution order depends on the execution context.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-learn	Ready	Preview	Jun 26, 2026 9:22am

[cursor]

PR Summary

Low Risk
Documentation-only wording change with no runtime or API behavior impact.

Overview
Corrects the closing note on Node.js setImmediate() in Discover JavaScript Timers: it no longer claims equivalence to setTimeout(() => {}, 0).

The text now states that setImmediate() runs in the event loop check phase and that ordering versus zero-delay setTimeout depends on execution context, because the two APIs use different loop phases.

^{Reviewed by Cursor Bugbot for commit d2d3e27. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/timers

Please review the changes when you have a chance. Thank you! 🙏