From 3bedee952d5f59c2f45a6879855156a000f9a0f6 Mon Sep 17 00:00:00 2001 From: Dorian Mullings Date: Wed, 24 Oct 2018 00:34:45 -0400 Subject: [PATCH] fixed minor typo in 16.6 blog post (#1290) * fixed typo 16.6 blog post * Update 2018-10-23-react-v-16-6.md --- content/blog/2018-10-23-react-v-16-6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2018-10-23-react-v-16-6.md b/content/blog/2018-10-23-react-v-16-6.md index f0f1710e..6c7d9428 100644 --- a/content/blog/2018-10-23-react-v-16-6.md +++ b/content/blog/2018-10-23-react-v-16-6.md @@ -76,7 +76,7 @@ React 16 introduced [Error Boundaries](/blog/2017/07/26/error-handling-in-react- Before that is fired, we render `null` in place of the tree that threw an error. This sometimes breaks parent components that don't expect their refs to be empty. It also doesn't work to recover from errors on the server since the `Did` lifecycle methods don't fire during server-side rendering. -We've adding another error method that lets you render the fallback UI before the render completes. See the docs for [`getDerivedStateFromError()`](/docs/react-component.html#static-getderivedstatefromerror). +We're adding another error method that lets you render the fallback UI before the render completes. See the docs for [`getDerivedStateFromError()`](/docs/react-component.html#static-getderivedstatefromerror). > Note: `getDerivedStateFromError()` is not yet available for server-side rendering. It is designed to work with server-side rendering in a future release. We're releasing it early so that you can start preparing to use it.