Merge pull request #1436 from paroche/patch-60

Update article.md
2019-10-10 10:52:05 +03:00 · 2019-10-10 10:52:05 +03:00 · 933861dec6
commit 933861dec6
parent 3008f26a41 91b17f3bf0
1 changed files with 1 additions and 1 deletions
--- a/1-js/10-error-handling/1-try-catch/article.md
+++ b/1-js/10-error-handling/1-try-catch/article.md
@ -668,4 +668,4 @@ We can also generate our own errors using the `throw` operator. Technically, the
 *Rethrowing* is a very important pattern of error handling: a `catch` block usually expects and knows how to handle the particular error type, so it should rethrow errors it doesn't know.
-Even if we don't have `try..catch`, most environments allow to setup a "global" error handler to catch errors that "fall out". In-browser that's `window.onerror`.
+Even if we don't have `try..catch`, most environments allow us to setup a "global" error handler to catch errors that "fall out". In-browser, that's `window.onerror`.
@ -668,4 +668,4 @@ We can also generate our own errors using the `throw` operator. Technically, the

	Rethrowing is a very important pattern of error handling: a `catch` block usually expects and knows how to handle the particular error type, so it should rethrow errors it doesn't know.	Rethrowing is a very important pattern of error handling: a `catch` block usually expects and knows how to handle the particular error type, so it should rethrow errors it doesn't know.

	Even if we don't have `try..catch`, most environments allow to setup a "global" error handler to catch errors that "fall out". In-browser that's `window.onerror`.	Even if we don't have `try..catch`, most environments allow us to setup a "global" error handler to catch errors that "fall out". In-browser, that's `window.onerror`.