Skip to content

Commit 837f7ab

Browse files
authored
Update article.md
"chapter" -> "article" 2x
1 parent 425a0af commit 837f7ab

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Now the order is as intended.
5454

5555
## Unhandled rejection
5656

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

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

@@ -109,4 +109,4 @@ So `.then/catch/finally` handlers are always called after the current code is fi
109109

110110
If we need to guarantee that a piece of code is executed after `.then/catch/finally`, we can add it into a chained `.then` call.
111111

112-
In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with the "event loop" and "macrotasks". As these have no direct relation to promises, they are covered in another part of the tutorial, in the chapter <info:event-loop>.
112+
In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with the "event loop" and "macrotasks". As these have no direct relation to promises, they are covered in another part of the tutorial, in the article <info:event-loop>.

0 commit comments

Comments
 (0)