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	Jun 26, 2026 5:57pm

[cursor]

PR Summary

Low Risk
Documentation-only change to asynchronous-work guide text with no code or runtime impact.

Overview
Updates one sentence in Understanding process.nextTick() so setTimeout(() => {}, 0) is described as scheduling the callback for a future event loop iteration instead of running at the end of next tick, and names process.nextTick() explicitly as running before the event loop continues.

This is wording-only; it does not change runtime behavior.

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