fix docs re: setImmediate in node. Closes #1079

1 files changed, 1 insertions, 4 deletions

diff --git a/README.md b/README.md
index ae181c3..e331362 100644
--- a/README.md
+++ b/README.md
@@ -1727,10 +1727,7 @@ three
 
 ### nextTick(callback, [args...]), setImmediate(callback, [args...])
 
-Calls `callback` on a later loop around the event loop. In Node.js this just
-calls `process.nextTick`; in the browser it falls back to `setImmediate(callback)`
-if available, otherwise `setTimeout(callback, 0)`, which means other higher priority
-events may precede the execution of `callback`.
+Calls `callback` on a later loop around the event loop. In Node.js this just calls `setImmediate`.  In the browser it will use `setImmediate` if available, otherwise `setTimeout(callback, 0)`, which means other higher priority events may precede the execution of `callback`.
 
 This is used internally for browser-compatibility purposes.