Make it more specific
Dan Abramov committed
Jul 27, 2017 at 23:44 UTC
c7e9044c51fe8cc82aaa8e24424afa42e7370348
1 file changed
+1
-1
docs/_posts/2017-07-26-error-handling-in-react-16.md
+1
-1
@@ -77,7 +77,7 @@ We also encourage you to use JS error reporting services (or build your own) so
77
78
## Component Stack Traces
79
80
-React 16 prints all errors to the console in development, even if the application accidentally swallows them. In addition to the error message and the JavaScript stack, it also provides component stack traces. Now you can see where exactly in the component tree the failure has happened:
80
+React 16 prints all errors that occurred during rendering to the console in development, even if the application accidentally swallows them. In addition to the error message and the JavaScript stack, it also provides component stack traces. Now you can see where exactly in the component tree the failure has happened:
81
82
<img src="/react/img/blog/error-boundaries-stack-trace.png" alt="Component stack traces in error message" style="width: 100%;">
83