fix: Correct name, not event queue but message queue. (nodejs#128)

flaviocopes · ZYSzys · commit e4608c8db8a3 · 2019-02-28T09:51:37.000+08:00
diff --git a/src/documentation/0029-node-event-loop/index.md b/src/documentation/0029-node-event-loop/index.md
@@ -144,7 +144,7 @@ When setTimeout() is called, the Browser or Node.js start the timer. Once the ti
 
 The Message Queue is also where user-initiated events like click or keyboard events, or fetch responses are queued before your code has the opportunity to react to them. Or also DOM events like `onLoad`.
 
-**The loop gives priority to the call stack, and it first processes everything it finds in the call stack, and once there's nothing in there, it goes to pick up things in the event queue.**
+**The loop gives priority to the call stack, and it first processes everything it finds in the call stack, and once there's nothing in there, it goes to pick up things in the message queue.**
 
 We don't have to wait for functions like `setTimeout`, fetch or other things to do their own work, because they are provided by the browser, and they live on their own threads. For example, if you set the `setTimeout` timeout to 2 seconds, you don't have to wait 2 seconds - the wait happens elsewhere.
 
