Skip to content

Commit 9a4fe33

Browse files
committed
minor fixes
1 parent 7c340a1 commit 9a4fe33

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎1-js/11-async/07-microtask-queue/article.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ Here's the demo:
1010
```js run
1111
let promise = Promise.resolve();
1212

13-
promise.then(() => alert("promise done"));
13+
promise.then(() => alert("promise done!"));
1414

1515
alert("code finished"); // this alert shows first
1616
```
1717

18-
If you run it, you see `code finished` first, and then `promise done`.
18+
If you run it, you see `code finished` first, and then `promise done!`.
1919

2020
That's strange, because the promise is definitely done from the beginning.
2121

@@ -54,7 +54,7 @@ Now the order is as intended.
5454

5555
## Unhandled rejection
5656

57-
Remember "unhandled rejection" event from the chapter <info:promise-error-handling>?
57+
Remember `unhandledrejection` event from the chapter <info:promise-error-handling>?
5858

5959
Now we can see exactly how JavaScript finds out that there was an unhandled rejection
6060

0 commit comments

Comments
 (0)