From 18377566bf726729f6eea876e060a2c40bed0e92 Mon Sep 17 00:00:00 2001
From: Travis CI <travis@Traviss-Mac-228.local>
Date: Mon, 16 Nov 2015 19:44:33 +0000
Subject: [PATCH] update website

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

diff --git a/docs/panresponder.html b/docs/panresponder.html
index 4deef93ee1a..a5ababa84a2 100644
--- a/docs/panresponder.html
+++ b/docs/panresponder.html
@@ -50,7 +50,7 @@ normal event.</p><p>A <code>gestureState</code> object has the following:</p><ul
 that provide not only the typical <code>ResponderSyntheticEvent</code>, but also the
 <code>PanResponder</code> gesture state.  Simply replace the word <code>Responder</code> with
 <code>PanResponder</code> in each of the typical <code>onResponder*</code> callbacks. For
-example, the <code>config</code> object would look like:</p><ul><li><code>onMoveShouldSetPanResponder: (e, gestureState) =&gt; {...}</code></li><li><code>onMoveShouldSetPanResponderCapture: (e, gestureState) =&gt; {...}</code></li><li><code>onStartShouldSetPanResponder: (e, gestureState) =&gt; {...}</code></li><li><code>onStartShouldSetPanResponderCapture: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderReject: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderGrant: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderStart: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderEnd: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderRelease: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderMove: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderTerminate: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderTerminationRequest: (e, gestureState) =&gt; {...}</code></li><li><p>&#x27;onShouldBlockNativeResponder: (e, gestureState) =&gt; {...}&#x27;</p><p>In general, for events that have capture equivalents, we update the
+example, the <code>config</code> object would look like:</p><ul><li><code>onMoveShouldSetPanResponder: (e, gestureState) =&gt; {...}</code></li><li><code>onMoveShouldSetPanResponderCapture: (e, gestureState) =&gt; {...}</code></li><li><code>onStartShouldSetPanResponder: (e, gestureState) =&gt; {...}</code></li><li><code>onStartShouldSetPanResponderCapture: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderReject: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderGrant: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderStart: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderEnd: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderRelease: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderMove: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderTerminate: (e, gestureState) =&gt; {...}</code></li><li><code>onPanResponderTerminationRequest: (e, gestureState) =&gt; {...}</code></li><li><p><code>onShouldBlockNativeResponder: (e, gestureState) =&gt; {...}</code></p><p>In general, for events that have capture equivalents, we update the
 gestureState once in the capture phase and can use it in the bubble phase
 as well.</p><p>Be careful with onStartShould* callbacks. They only reflect updated
 <code>gestureState</code> for start/end events that bubble/capture to the Node.