From 74d974449cb9a33178b42106bd52f15d93be784d Mon Sep 17 00:00:00 2001
From: Szymon Nowicki <sznowicki@users.noreply.github.com>
Date: Sat, 16 Dec 2017 12:25:31 +0100
Subject: [PATCH] Update `React.PureComponent` reference.

Rewording the `React.PureComponent` reference to make it more clear, that `React.Component` doesn't implement `.shouldComponentUpdate` at all.
---
 content/docs/reference-react.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/docs/reference-react.md b/content/docs/reference-react.md
index 6320a34c..1c9eadf9 100644
--- a/content/docs/reference-react.md
+++ b/content/docs/reference-react.md
@@ -70,8 +70,7 @@ See the [React.Component API Reference](/docs/react-component.html) for a list o
 * * *
 
 ### `React.PureComponent`
-
-`React.PureComponent` is exactly like [`React.Component`](#reactcomponent), but implements [`shouldComponentUpdate()`](/docs/react-component.html#shouldcomponentupdate) with a shallow prop and state comparison, which [`React.Component`](#reactcomponent) is missing completely. 
+`React.PureComponent` is similar to [`React.Component`](#reactcomponent). The difference between them is that [`React.Component`](#reactcomponent) doesn't implement [`shouldComponentUpdate()`](/docs/react-component.html#shouldcomponentupdate), but `React.PureComponent` implements it with a shallow prop and state comparison. 
 
 If your React component's `render()` function renders the same result given the same props and state, you can use `React.PureComponent` for a performance boost in some cases.