From b82136a94c9de3b0922465aaeafeea8751392682 Mon Sep 17 00:00:00 2001 From: Peter Keller Date: Mon, 1 Oct 2018 18:25:55 -0400 Subject: [PATCH] Update sentence in Unhandled rejections --- 6-async/03-promise-chaining/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/6-async/03-promise-chaining/article.md b/6-async/03-promise-chaining/article.md index 3df3b0da..d1a5cb92 100644 --- a/6-async/03-promise-chaining/article.md +++ b/6-async/03-promise-chaining/article.md @@ -635,7 +635,7 @@ new Promise(function() { In case of an error, the promise state becomes "rejected", and the execution should jump to the closest rejection handler. But there is no such handler in the examples above. So the error gets "stuck". -In practice, that's usually because of the bad code. Indeed, how come that there's no error handling? +In practice, that's usually because of the bad code. Indeed, how come there's no error handling? Most JavaScript engines track such situations and generate a global error in that case. We can see it in the console.