From 0f7443b5df73c6033f12ba015a10015abe85631e Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Tue, 4 Aug 2020 09:25:45 +0300 Subject: [PATCH] minor fixes --- 1-js/11-async/08-async-await/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/11-async/08-async-await/article.md b/1-js/11-async/08-async-await/article.md index dfb8a9d5..9f07a608 100644 --- a/1-js/11-async/08-async-await/article.md +++ b/1-js/11-async/08-async-await/article.md @@ -67,7 +67,7 @@ f(); The function execution "pauses" at the line `(*)` and resumes when the promise settles, with `result` becoming its result. So the code above shows "done!" in one second. -Let's emphasize: `await` literally makes JavaScript wait until the promise settles, and then go on with the result. That doesn't cost any CPU resources, because the engine can do other jobs in the meantime: execute other scripts, handle events, etc. +Let's emphasize: `await` literally suspends the function execution until the promise settles, and then go on with the result. That doesn't cost any CPU resources, because the JavaScript engine can do other jobs in the meantime: execute other scripts, handle events, etc. It's just a more elegant syntax of getting the promise result than `promise.then`, easier to read and write.