From a3cb7c52352272c34c4e54cd78c0732edb041c6f Mon Sep 17 00:00:00 2001 From: Arshita Kakkar Date: Thu, 29 Aug 2019 18:08:36 +0530 Subject: [PATCH] Removed hyperlink from 'a' (#2296) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The sentence in line114 - "For this change, we’ve provided a [codemod](https://github.com/reactjs/react-codemod#error-boundaries) to automatically migrate your code" had hyperlink added to [a codemod] instead of only to [codemod]. Updated this. --- content/blog/2017-07-26-error-handling-in-react-16.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2017-07-26-error-handling-in-react-16.md b/content/blog/2017-07-26-error-handling-in-react-16.md index 7625de7b4..455fd001a 100644 --- a/content/blog/2017-07-26-error-handling-in-react-16.md +++ b/content/blog/2017-07-26-error-handling-in-react-16.md @@ -111,4 +111,4 @@ Error boundaries preserve the declarative nature of React, and behave as you wou React 15 included a very limited support for error boundaries under a different method name: `unstable_handleError`. This method no longer works, and you will need to change it to `componentDidCatch` in your code starting from the first 16 beta release. -For this change, we’ve provided [a codemod](https://github.com/reactjs/react-codemod#error-boundaries) to automatically migrate your code. +For this change, we’ve provided a [codemod](https://github.com/reactjs/react-codemod#error-boundaries) to automatically migrate your code.