From 724d87ea4095c336d0fc0ea6fd7144159f9bfb23 Mon Sep 17 00:00:00 2001
From: Dan Abramov <dan.abramov@gmail.com>
Date: Sat, 8 Apr 2017 04:11:46 +0100
Subject: [PATCH] Update manually

---
 docs/typechecking-with-proptypes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/typechecking-with-proptypes.html b/docs/typechecking-with-proptypes.html
index 124a4fb121..5760421413 100644
--- a/docs/typechecking-with-proptypes.html
+++ b/docs/typechecking-with-proptypes.html
@@ -80,7 +80,7 @@
 
     <blockquote>
 <p>Note:
-<code>React.PropTypes</code> is deprecated as of React v15.5. Please use <a href="https://github.com/aackerman/PropTypes">the <code>prop-types</code> library instead</a>.</p>
+<code>React.PropTypes</code> is deprecated as of React v15.5. Please use <a href="https://www.npmjs.com/package/prop-types">the <code>prop-types</code> library instead</a>.</p>
 </blockquote>
 
 <p>As your app grows, you can catch a lot of bugs with typechecking. For some applications, you can use JavaScript extensions like <a href="https://flowtype.org/">Flow</a> or <a href="https://www.typescriptlang.org/">TypeScript</a> to typecheck your whole application. But even if you don&#39;t use those, React has some built-in typechecking abilities. To run typechecking on the props for a component, you can assign the special <code>propTypes</code> property:</p>