docs: update explanation of setImmediate vs setTimeout (#8623)

* docs: update explanation of setImmediate vs setTimeout

Clarifies the execution order of setTimeout and setImmediate when called from the main module and inside an I/O callback.

Signed-off-by: Sébastien Dan <sebastien.dan@ikmail.com>

* fix: use bold and lowercase format for event loop phases

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Sébastien Dan <sdan@polygon.technology>

---------

Signed-off-by: Sébastien Dan <sebastien.dan@ikmail.com>
Signed-off-by: Sébastien Dan <sdan@polygon.technology>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: sebastiendan

apps/site/pages/en/learn/asynchronous-work/understanding-setimmediate.md

@@ -20,7 +20,7 @@ How is `setImmediate()` different from `setTimeout(() => {}, 0)` (passing a 0ms
 
 A function passed to `process.nextTick()` is going to be executed on the current iteration of the event loop, after the current operation ends. This means it will always execute before `setTimeout` and `setImmediate`.
 
-A `setTimeout()` callback with a 0ms delay is very similar to `setImmediate()`. The execution order will depend on various factors, but they will be both run in the next iteration of the event loop.
+A `setTimeout()` callback with a 0ms delay is very similar to `setImmediate()`. The execution order will depend on various factors, but they will be both run in the next iteration (the first one) of the event loop when called from the main module. When scheduled inside an I/O callback, setImmediate is guaranteed to run in the current iteration's **check** phase, while setTimeout must wait for the **timers** phase of the subsequent iteration.
 
 A `process.nextTick` callback is added to `process.nextTick queue`. A `Promise.then()` callback is added to `promises microtask queue`. A `setTimeout`, `setImmediate` callback is added to `macrotask queue`.