docs(asynchronous-work): clarify setTimeout() scheduling in process.nextTick guide

[Akankshaaaa-01]

Summary

This change clarifies the wording describing setTimeout(() => {}, 0) in the Understanding process.nextTick() guide.

The previous wording referred to the callback executing "at the end of next tick", which may be interpreted as a specific event loop timing. The updated wording instead describes it as being scheduled for a future event loop iteration while preserving the beginner-friendly explanation.

No behavioral changes are introduced.

[github-actions]

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/timers @nodejs/nodejs-website

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
nodejs-learn	Ready	Preview	Jul 3, 2026 3:30am

[cursor]

PR Summary

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

Overview
Updates a single comparison sentence in Understanding process.nextTick() so setTimeout(() => {}, 0) is described as scheduling work for a future event loop iteration, instead of running “at the end of next tick.”

The revised text still contrasts that delay with process.nextTick(), which runs before the event loop continues, without changing the rest of the guide.

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

[Akankshaaaa-01]

@avivkeller Could you take a look at this PR when you have a chance? Happy to adjust the wording if needed, or close the PR if you think this change isn't necessary.