From 234142cdf7aacf441145be534b84957db0f73af5 Mon Sep 17 00:00:00 2001
From: sunnylqm <sunnylqm@qq.com>
Date: Tue, 12 Apr 2016 19:49:13 -0700
Subject: [PATCH] Fix broken link for shouldComponentUpdate

Summary: Closes https://github.com/facebook/react-native/pull/6856

Differential Revision: D3172431

fb-gh-sync-id: d0fcde5a2097bdca9551d1e9e9f5817865002041
fbshipit-source-id: d0fcde5a2097bdca9551d1e9e9f5817865002041
---
 docs/DirectManipulation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/DirectManipulation.md b/docs/DirectManipulation.md
index 3c6fd46ed..f705eda39 100644
--- a/docs/DirectManipulation.md
+++ b/docs/DirectManipulation.md
@@ -23,7 +23,7 @@ properties directly on a DOM node.
 > and stores state in the native layer (DOM, UIView, etc.) and not
 > within your React components, which makes your code more difficult to
 > reason about. Before you use it, try to solve your problem with `setState`
-> and [shouldComponentUpdate](react-native/docs/direct-manipulation.html#setnativeprops-shouldcomponentupdate).
+> and [shouldComponentUpdate](http://facebook.github.io/react/docs/advanced-performance.html#shouldcomponentupdate-in-action).
 
 ## setNativeProps with TouchableOpacity