fix typo

nonopolarity · web-flow · commit e3a2051c0eb9 · 2019-12-27T05:25:15.000-08:00
diff --git a/1-js/11-async/07-microtask-queue/article.md b/1-js/11-async/07-microtask-queue/article.md
@@ -109,4 +109,4 @@ So, `.then/catch/finally` handlers are always called after the current code is f
 
 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.
 
-In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with "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>.
+In most JavaScript engines, including browsers and Node.js, the concept of microtasks is closely tied with "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>.

Original file line number	Diff line number	Diff line change
@@ -109,4 +109,4 @@ So, `.then/catch/finally` handlers are always called after the current code is f
`109`	`109`
`110`	`110`	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.
`111`	`111`
`112`		`-In most Javascript engines, including browsers and Node.js, the concept of microtasks is closely tied with "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 "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>.`