From 58205b3dfd6d463bd02cb8259c8f3942f36c5408 Mon Sep 17 00:00:00 2001
From: Peter Roche <46547072+paroche@users.noreply.github.com>
Date: Wed, 29 Jan 2020 00:07:49 -0700
Subject: [PATCH] Update article.md

"continues to closest" -> "continues to next closest". Consistent w/ usage in rest of explanation.
---
 1-js/11-async/04-promise-error-handling/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/11-async/04-promise-error-handling/article.md b/1-js/11-async/04-promise-error-handling/article.md
index 4b4db9b6..7c6af6a3 100644
--- a/1-js/11-async/04-promise-error-handling/article.md
+++ b/1-js/11-async/04-promise-error-handling/article.md
@@ -100,7 +100,7 @@ As we already noticed, `.catch` at the end of the chain is similar to `try..catc
 
 In a regular `try..catch` we can analyze the error and maybe rethrow it if it can't be handled. The same thing is possible for promises.
 
-If we `throw` inside `.catch`, then the control goes to the next closest error handler. And if we handle the error and finish normally, then it continues to the closest successful `.then` handler.
+If we `throw` inside `.catch`, then the control goes to the next closest error handler. And if we handle the error and finish normally, then it continues to the next closest successful `.then` handler.
 
 In the example below the `.catch` successfully handles the error: