Reword further
Dan Abramov committed
Jul 27, 2017 at 10:48 UTC
bc0d241be1dd73799840536fdf4937b53ef18ab5
1 file changed
+1
-1
docs/_posts/2017-07-26-error-handling-in-react-16.md
+1
-1
@@ -15,7 +15,7 @@ In the past, JavaScript errors inside components used to corrupt React’s inter
15
16
A JavaScript error in a part of the UI shouldn’t break the whole app. To solve this problem for React users, React 16 introduces a new concept of an “error boundary”.
17
18
-Error boundaries are React components that **catch JavaScript errors in their descendants, log those errors, and display a fallback UI** instead of the component tree that crashed. Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them.
18
+Error boundaries are React components that **catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI** instead of the component tree that crashed. Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them.
19
20
A class component becomes an error boundary if it defines a new lifecycle method called `componentDidCatch(error, info)`:
21