From f285d002c536683beff4dfa69906a17e3343a368 Mon Sep 17 00:00:00 2001 From: Dan Abramov Date: Sun, 10 Jun 2018 21:51:08 +0100 Subject: [PATCH] Reduce visual noise in the list It's obvious enough that this is the same method. I don't think repeating its name in the list brings any value, and it puts too much visual emphasis on something we're trying to deemphasize. --- content/docs/reference-react-component.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/reference-react-component.md b/content/docs/reference-react-component.md index 53fce429..0cf5ec06 100644 --- a/content/docs/reference-react-component.md +++ b/content/docs/reference-react-component.md @@ -74,7 +74,7 @@ These methods are called in the following order when an instance of a component > >These methods are considered legacy and you should [avoid them](/blog/2018/03/27/update-on-async-rendering.html) in new code: > ->- [`componentWillMount()` / `UNSAFE_componentWillMount()`](#unsafe_componentwillmount) +>- [`UNSAFE_componentWillMount()`](#unsafe_componentwillmount) #### Updating @@ -90,8 +90,8 @@ An update can be caused by changes to props or state. These methods are called i > >These methods are considered legacy and you should [avoid them](/blog/2018/03/27/update-on-async-rendering.html) in new code: > ->- [`componentWillUpdate()` / `UNSAFE_componentWillUpdate()`](#unsafe_componentwillupdate) ->- [`componentWillReceiveProps()` / `UNSAFE_componentWillReceiveProps()`](#unsafe_componentwillreceiveprops) +>- [`UNSAFE_componentWillUpdate()`](#unsafe_componentwillupdate) +>- [`UNSAFE_componentWillReceiveProps()`](#unsafe_componentwillreceiveprops) #### Unmounting