From 2f9b77a980c19ba2c3e61d12dffbcac1b60310ec Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Thu, 22 Mar 2018 08:10:25 -0700 Subject: [PATCH] 16.4 -> 16.x --- content/blog/2018-03-20-react-v-16-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2018-03-20-react-v-16-3.md b/content/blog/2018-03-20-react-v-16-3.md index 3c71e7ed..13fb76b5 100644 --- a/content/blog/2018-03-20-react-v-16-3.md +++ b/content/blog/2018-03-20-react-v-16-3.md @@ -68,7 +68,7 @@ We recognize that this change will impact many existing components. (At Facebook > **Note:** > -> Deprecation warnings will be enabled in version 16.4, **but the legacy lifecycles will continue to work until version 17**. +> Deprecation warnings will be enabled with a future 16.x release, **but the legacy lifecycles will continue to work until version 17**. > > Even in version 17, it will still be possible to use them, but they will be aliased with an "UNSAFE_" prefix to indicate that they might cause issues. We have also prepared an [automated script to rename them](https://github.com/reactjs/react-codemod#rename-unsafe-lifecycles) in existing code.