From 6c2ece0860468d3883722ca1ffb96cfeb1906671 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Fri, 14 Jul 2017 09:20:09 +0300 Subject: [PATCH] Update article.md --- 6-async/05-async-await/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/6-async/05-async-await/article.md b/6-async/05-async-await/article.md index 377ffe49..f22703d4 100644 --- a/6-async/05-async-await/article.md +++ b/6-async/05-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 that: `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 meanwhile: execute other scripts, handle events etc. +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 meanwhile: 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.