From 9a4fe338fd002e3bcc3280d62884e9fcaea29635 Mon Sep 17 00:00:00 2001 From: Enrico Palmieri <25690552+rezyx@users.noreply.github.com> Date: Tue, 23 Jul 2019 21:29:26 +0200 Subject: [PATCH] minor fixes --- 1-js/11-async/07-microtask-queue/article.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/1-js/11-async/07-microtask-queue/article.md b/1-js/11-async/07-microtask-queue/article.md index de49fd6a..807ba14f 100644 --- a/1-js/11-async/07-microtask-queue/article.md +++ b/1-js/11-async/07-microtask-queue/article.md @@ -10,12 +10,12 @@ Here's the demo: ```js run let promise = Promise.resolve(); -promise.then(() => alert("promise done")); +promise.then(() => alert("promise done!")); alert("code finished"); // this alert shows first ``` -If you run it, you see `code finished` first, and then `promise done`. +If you run it, you see `code finished` first, and then `promise done!`. That's strange, because the promise is definitely done from the beginning. @@ -54,7 +54,7 @@ Now the order is as intended. ## Unhandled rejection -Remember "unhandled rejection" event from the chapter ? +Remember `unhandledrejection` event from the chapter ? Now we can see exactly how JavaScript finds out that there was an unhandled rejection