diff --git a/blog/2017/02/14/using-native-driver-for-animated.html b/blog/2017/02/14/using-native-driver-for-animated.html
index 3be5068980b..ddb440d9ffe 100644
--- a/blog/2017/02/14/using-native-driver-for-animated.html
+++ b/blog/2017/02/14/using-native-driver-for-animated.html
@@ -171,7 +171,7 @@
 </Animated.ScrollView>
 </code></pre>
 <h2><a class="anchor" aria-hidden="true" id="caveats"></a><a href="#caveats" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Caveats</h2>
-<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
+<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but Flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
 <p>Native Animated has also been part of React Native for quite a while but has never been documented because it was considered experimental. Because of that make sure you are using a recent version (0.40+) of React Native if you want to use this feature.</p>
 <h2><a class="anchor" aria-hidden="true" id="resources"></a><a href="#resources" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>
 <p>For more information about animated I recommend watching <a href="https://www.youtube.com/watch?v=xtqUJVqpKNo">this talk</a> by <a href="https://twitter.com/Vjeux">Christopher Chedeau</a>.</p>
diff --git a/blog/2017/02/14/using-native-driver-for-animated/index.html b/blog/2017/02/14/using-native-driver-for-animated/index.html
index 3be5068980b..ddb440d9ffe 100644
--- a/blog/2017/02/14/using-native-driver-for-animated/index.html
+++ b/blog/2017/02/14/using-native-driver-for-animated/index.html
@@ -171,7 +171,7 @@
 &lt;/Animated.ScrollView&gt;
 </code></pre>
 <h2><a class="anchor" aria-hidden="true" id="caveats"></a><a href="#caveats" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Caveats</h2>
-<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
+<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but Flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
 <p>Native Animated has also been part of React Native for quite a while but has never been documented because it was considered experimental. Because of that make sure you are using a recent version (0.40+) of React Native if you want to use this feature.</p>
 <h2><a class="anchor" aria-hidden="true" id="resources"></a><a href="#resources" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>
 <p>For more information about animated I recommend watching <a href="https://www.youtube.com/watch?v=xtqUJVqpKNo">this talk</a> by <a href="https://twitter.com/Vjeux">Christopher Chedeau</a>.</p>
diff --git a/blog/page3/index.html b/blog/page3/index.html
index ff4c44aec9a..8622cb726c4 100644
--- a/blog/page3/index.html
+++ b/blog/page3/index.html
@@ -578,7 +578,7 @@ $ <span class="hljs-built_in">create-react-native-app</span> <span class="hljs-s
 &lt;/Animated.ScrollView&gt;
 </code></pre>
 <h2><a class="anchor" aria-hidden="true" id="caveats"></a><a href="#caveats" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Caveats</h2>
-<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
+<p>Not everything you can do with Animated is currently supported in Native Animated. The main limitation is that you can only animate non-layout properties, things like <code>transform</code> and <code>opacity</code> will work but Flexbox and position properties won't. Another one is with <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
 <p>Native Animated has also been part of React Native for quite a while but has never been documented because it was considered experimental. Because of that make sure you are using a recent version (0.40+) of React Native if you want to use this feature.</p>
 <h2><a class="anchor" aria-hidden="true" id="resources"></a><a href="#resources" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>
 <p>For more information about animated I recommend watching <a href="https://www.youtube.com/watch?v=xtqUJVqpKNo">this talk</a> by <a href="https://twitter.com/Vjeux">Christopher Chedeau</a>.</p>
diff --git a/docs/0.10/navigatorios.html b/docs/0.10/navigatorios.html
index a7e64188b3f..3a1ea790eae 100644
--- a/docs/0.10/navigatorios.html
+++ b/docs/0.10/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.10/navigatorios/index.html b/docs/0.10/navigatorios/index.html
index a7e64188b3f..3a1ea790eae 100644
--- a/docs/0.10/navigatorios/index.html
+++ b/docs/0.10/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.10/view.html b/docs/0.10/view.html
index e70287db8de..d2a75d5a440 100644
--- a/docs/0.10/view.html
+++ b/docs/0.10/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.10/view/index.html b/docs/0.10/view/index.html
index e70287db8de..d2a75d5a440 100644
--- a/docs/0.10/view/index.html
+++ b/docs/0.10/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.10/viewpagerandroid.html b/docs/0.10/viewpagerandroid.html
index 93b82a70718..1cd5012e28c 100644
--- a/docs/0.10/viewpagerandroid.html
+++ b/docs/0.10/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.10/viewpagerandroid/index.html b/docs/0.10/viewpagerandroid/index.html
index 93b82a70718..1cd5012e28c 100644
--- a/docs/0.10/viewpagerandroid/index.html
+++ b/docs/0.10/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.11/drawerlayoutandroid.html b/docs/0.11/drawerlayoutandroid.html
index 1bba4c95808..fb32d0be0cb 100644
--- a/docs/0.11/drawerlayoutandroid.html
+++ b/docs/0.11/drawerlayoutandroid.html
@@ -189,8 +189,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.11/drawerlayoutandroid/index.html b/docs/0.11/drawerlayoutandroid/index.html
index 1bba4c95808..fb32d0be0cb 100644
--- a/docs/0.11/drawerlayoutandroid/index.html
+++ b/docs/0.11/drawerlayoutandroid/index.html
@@ -189,8 +189,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.11/navigatorios.html b/docs/0.11/navigatorios.html
index 6a2f8e42134..a3a3c218fd2 100644
--- a/docs/0.11/navigatorios.html
+++ b/docs/0.11/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.11/navigatorios/index.html b/docs/0.11/navigatorios/index.html
index 6a2f8e42134..a3a3c218fd2 100644
--- a/docs/0.11/navigatorios/index.html
+++ b/docs/0.11/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.11/view.html b/docs/0.11/view.html
index fc9e667d340..0edf4bc8c6b 100644
--- a/docs/0.11/view.html
+++ b/docs/0.11/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.11/view/index.html b/docs/0.11/view/index.html
index fc9e667d340..0edf4bc8c6b 100644
--- a/docs/0.11/view/index.html
+++ b/docs/0.11/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.11/viewpagerandroid.html b/docs/0.11/viewpagerandroid.html
index 8b708de4dc4..a69a4489390 100644
--- a/docs/0.11/viewpagerandroid.html
+++ b/docs/0.11/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.11/viewpagerandroid/index.html b/docs/0.11/viewpagerandroid/index.html
index 8b708de4dc4..a69a4489390 100644
--- a/docs/0.11/viewpagerandroid/index.html
+++ b/docs/0.11/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.12/drawerlayoutandroid.html b/docs/0.12/drawerlayoutandroid.html
index 700e2988569..57224b8cf22 100644
--- a/docs/0.12/drawerlayoutandroid.html
+++ b/docs/0.12/drawerlayoutandroid.html
@@ -189,8 +189,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.12/drawerlayoutandroid/index.html b/docs/0.12/drawerlayoutandroid/index.html
index 700e2988569..57224b8cf22 100644
--- a/docs/0.12/drawerlayoutandroid/index.html
+++ b/docs/0.12/drawerlayoutandroid/index.html
@@ -189,8 +189,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.12/navigatorios.html b/docs/0.12/navigatorios.html
index a4a9695b885..f9fc5e3b252 100644
--- a/docs/0.12/navigatorios.html
+++ b/docs/0.12/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.12/navigatorios/index.html b/docs/0.12/navigatorios/index.html
index a4a9695b885..f9fc5e3b252 100644
--- a/docs/0.12/navigatorios/index.html
+++ b/docs/0.12/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.12/view.html b/docs/0.12/view.html
index dbfeed2fce8..adb438776bc 100644
--- a/docs/0.12/view.html
+++ b/docs/0.12/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.12/view/index.html b/docs/0.12/view/index.html
index dbfeed2fce8..adb438776bc 100644
--- a/docs/0.12/view/index.html
+++ b/docs/0.12/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.12/viewpagerandroid.html b/docs/0.12/viewpagerandroid.html
index a1103f58646..908a1a60e15 100644
--- a/docs/0.12/viewpagerandroid.html
+++ b/docs/0.12/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.12/viewpagerandroid/index.html b/docs/0.12/viewpagerandroid/index.html
index a1103f58646..908a1a60e15 100644
--- a/docs/0.12/viewpagerandroid/index.html
+++ b/docs/0.12/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.13/drawerlayoutandroid.html b/docs/0.13/drawerlayoutandroid.html
index e7777b3c5a9..e2d4541c181 100644
--- a/docs/0.13/drawerlayoutandroid.html
+++ b/docs/0.13/drawerlayoutandroid.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.13/drawerlayoutandroid/index.html b/docs/0.13/drawerlayoutandroid/index.html
index e7777b3c5a9..e2d4541c181 100644
--- a/docs/0.13/drawerlayoutandroid/index.html
+++ b/docs/0.13/drawerlayoutandroid/index.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.13/navigatorios.html b/docs/0.13/navigatorios.html
index b68cad56a19..c7736b0e283 100644
--- a/docs/0.13/navigatorios.html
+++ b/docs/0.13/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.13/navigatorios/index.html b/docs/0.13/navigatorios/index.html
index b68cad56a19..c7736b0e283 100644
--- a/docs/0.13/navigatorios/index.html
+++ b/docs/0.13/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.13/view.html b/docs/0.13/view.html
index 348da642e4f..1e295bba2eb 100644
--- a/docs/0.13/view.html
+++ b/docs/0.13/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.13/view/index.html b/docs/0.13/view/index.html
index 348da642e4f..1e295bba2eb 100644
--- a/docs/0.13/view/index.html
+++ b/docs/0.13/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.14/drawerlayoutandroid.html b/docs/0.14/drawerlayoutandroid.html
index 232ee61eab2..566d5051be9 100644
--- a/docs/0.14/drawerlayoutandroid.html
+++ b/docs/0.14/drawerlayoutandroid.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.14/drawerlayoutandroid/index.html b/docs/0.14/drawerlayoutandroid/index.html
index 232ee61eab2..566d5051be9 100644
--- a/docs/0.14/drawerlayoutandroid/index.html
+++ b/docs/0.14/drawerlayoutandroid/index.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.14/navigatorios.html b/docs/0.14/navigatorios.html
index c568011d869..2d61c24acfa 100644
--- a/docs/0.14/navigatorios.html
+++ b/docs/0.14/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.14/navigatorios/index.html b/docs/0.14/navigatorios/index.html
index c568011d869..2d61c24acfa 100644
--- a/docs/0.14/navigatorios/index.html
+++ b/docs/0.14/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.14/view.html b/docs/0.14/view.html
index ab28fbad0d2..4ea00dc678d 100644
--- a/docs/0.14/view.html
+++ b/docs/0.14/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.14/view/index.html b/docs/0.14/view/index.html
index ab28fbad0d2..4ea00dc678d 100644
--- a/docs/0.14/view/index.html
+++ b/docs/0.14/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.15/drawerlayoutandroid.html b/docs/0.15/drawerlayoutandroid.html
index ab7701a97d0..a0c911b14b5 100644
--- a/docs/0.15/drawerlayoutandroid.html
+++ b/docs/0.15/drawerlayoutandroid.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.15/drawerlayoutandroid/index.html b/docs/0.15/drawerlayoutandroid/index.html
index ab7701a97d0..a0c911b14b5 100644
--- a/docs/0.15/drawerlayoutandroid/index.html
+++ b/docs/0.15/drawerlayoutandroid/index.html
@@ -193,8 +193,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.15/navigatorios.html b/docs/0.15/navigatorios.html
index 8022e276f46..29649801c4d 100644
--- a/docs/0.15/navigatorios.html
+++ b/docs/0.15/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.15/navigatorios/index.html b/docs/0.15/navigatorios/index.html
index 8022e276f46..29649801c4d 100644
--- a/docs/0.15/navigatorios/index.html
+++ b/docs/0.15/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.15/view.html b/docs/0.15/view.html
index e54d2cd9548..74e96699966 100644
--- a/docs/0.15/view.html
+++ b/docs/0.15/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.15/view/index.html b/docs/0.15/view/index.html
index e54d2cd9548..74e96699966 100644
--- a/docs/0.15/view/index.html
+++ b/docs/0.15/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.16/drawerlayoutandroid.html b/docs/0.16/drawerlayoutandroid.html
index 1624d021b0a..543daa74dc7 100644
--- a/docs/0.16/drawerlayoutandroid.html
+++ b/docs/0.16/drawerlayoutandroid.html
@@ -196,8 +196,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.16/drawerlayoutandroid/index.html b/docs/0.16/drawerlayoutandroid/index.html
index 1624d021b0a..543daa74dc7 100644
--- a/docs/0.16/drawerlayoutandroid/index.html
+++ b/docs/0.16/drawerlayoutandroid/index.html
@@ -196,8 +196,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.16/navigatorios.html b/docs/0.16/navigatorios.html
index c586b21f036..b7370568cdc 100644
--- a/docs/0.16/navigatorios.html
+++ b/docs/0.16/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.16/navigatorios/index.html b/docs/0.16/navigatorios/index.html
index c586b21f036..b7370568cdc 100644
--- a/docs/0.16/navigatorios/index.html
+++ b/docs/0.16/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.16/view.html b/docs/0.16/view.html
index f22da238bc2..a1f6efd1981 100644
--- a/docs/0.16/view.html
+++ b/docs/0.16/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.16/view/index.html b/docs/0.16/view/index.html
index f22da238bc2..a1f6efd1981 100644
--- a/docs/0.16/view/index.html
+++ b/docs/0.16/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.17/drawerlayoutandroid.html b/docs/0.17/drawerlayoutandroid.html
index de97b263884..be25e0317a1 100644
--- a/docs/0.17/drawerlayoutandroid.html
+++ b/docs/0.17/drawerlayoutandroid.html
@@ -196,8 +196,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.17/drawerlayoutandroid/index.html b/docs/0.17/drawerlayoutandroid/index.html
index de97b263884..be25e0317a1 100644
--- a/docs/0.17/drawerlayoutandroid/index.html
+++ b/docs/0.17/drawerlayoutandroid/index.html
@@ -196,8 +196,8 @@
 <p>Function called when the drawer state has changed. The drawer can be in 3 states:</p>
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
-<li>dragging, meaning there is currently an interation with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>dragging, meaning there is currently an interaction with the navigation view</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.17/navigatorios.html b/docs/0.17/navigatorios.html
index 3953b35b3d3..f63b0cc5ea1 100644
--- a/docs/0.17/navigatorios.html
+++ b/docs/0.17/navigatorios.html
@@ -87,7 +87,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.17/navigatorios/index.html b/docs/0.17/navigatorios/index.html
index 3953b35b3d3..f63b0cc5ea1 100644
--- a/docs/0.17/navigatorios/index.html
+++ b/docs/0.17/navigatorios/index.html
@@ -87,7 +87,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.17/view.html b/docs/0.17/view.html
index a585ca32ffa..ec8935612ee 100644
--- a/docs/0.17/view.html
+++ b/docs/0.17/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.17/view/index.html b/docs/0.17/view/index.html
index a585ca32ffa..ec8935612ee 100644
--- a/docs/0.17/view/index.html
+++ b/docs/0.17/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.18/drawerlayoutandroid.html b/docs/0.18/drawerlayoutandroid.html
index 453c0101dff..76d6dfc9dcb 100644
--- a/docs/0.18/drawerlayoutandroid.html
+++ b/docs/0.18/drawerlayoutandroid.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.18/drawerlayoutandroid/index.html b/docs/0.18/drawerlayoutandroid/index.html
index 453c0101dff..76d6dfc9dcb 100644
--- a/docs/0.18/drawerlayoutandroid/index.html
+++ b/docs/0.18/drawerlayoutandroid/index.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.18/view.html b/docs/0.18/view.html
index 2985c324c20..18b32b2ede4 100644
--- a/docs/0.18/view.html
+++ b/docs/0.18/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.18/view/index.html b/docs/0.18/view/index.html
index 2985c324c20..18b32b2ede4 100644
--- a/docs/0.18/view/index.html
+++ b/docs/0.18/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.19/drawerlayoutandroid.html b/docs/0.19/drawerlayoutandroid.html
index 1730ce80ff0..ad3503a18db 100644
--- a/docs/0.19/drawerlayoutandroid.html
+++ b/docs/0.19/drawerlayoutandroid.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.19/drawerlayoutandroid/index.html b/docs/0.19/drawerlayoutandroid/index.html
index 1730ce80ff0..ad3503a18db 100644
--- a/docs/0.19/drawerlayoutandroid/index.html
+++ b/docs/0.19/drawerlayoutandroid/index.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.19/view.html b/docs/0.19/view.html
index d4d72e37366..4a27eacbe99 100644
--- a/docs/0.19/view.html
+++ b/docs/0.19/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.19/view/index.html b/docs/0.19/view/index.html
index d4d72e37366..4a27eacbe99 100644
--- a/docs/0.19/view/index.html
+++ b/docs/0.19/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.20/drawerlayoutandroid.html b/docs/0.20/drawerlayoutandroid.html
index 3541bf0c5d0..c8ae1c08244 100644
--- a/docs/0.20/drawerlayoutandroid.html
+++ b/docs/0.20/drawerlayoutandroid.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.20/drawerlayoutandroid/index.html b/docs/0.20/drawerlayoutandroid/index.html
index 3541bf0c5d0..c8ae1c08244 100644
--- a/docs/0.20/drawerlayoutandroid/index.html
+++ b/docs/0.20/drawerlayoutandroid/index.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.20/view.html b/docs/0.20/view.html
index a328376033c..720fbd9aab4 100644
--- a/docs/0.20/view.html
+++ b/docs/0.20/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.20/view/index.html b/docs/0.20/view/index.html
index a328376033c..720fbd9aab4 100644
--- a/docs/0.20/view/index.html
+++ b/docs/0.20/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.20/viewpagerandroid.html b/docs/0.20/viewpagerandroid.html
index ff22a12e4c0..3afa382f326 100644
--- a/docs/0.20/viewpagerandroid.html
+++ b/docs/0.20/viewpagerandroid.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.20/viewpagerandroid/index.html b/docs/0.20/viewpagerandroid/index.html
index ff22a12e4c0..3afa382f326 100644
--- a/docs/0.20/viewpagerandroid/index.html
+++ b/docs/0.20/viewpagerandroid/index.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.21/drawerlayoutandroid.html b/docs/0.21/drawerlayoutandroid.html
index 91865d912c5..91f825373b7 100644
--- a/docs/0.21/drawerlayoutandroid.html
+++ b/docs/0.21/drawerlayoutandroid.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.21/drawerlayoutandroid/index.html b/docs/0.21/drawerlayoutandroid/index.html
index 91865d912c5..91f825373b7 100644
--- a/docs/0.21/drawerlayoutandroid/index.html
+++ b/docs/0.21/drawerlayoutandroid/index.html
@@ -197,7 +197,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.21/view.html b/docs/0.21/view.html
index e40b8ca025c..1b30ebc1681 100644
--- a/docs/0.21/view.html
+++ b/docs/0.21/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.21/view/index.html b/docs/0.21/view/index.html
index e40b8ca025c..1b30ebc1681 100644
--- a/docs/0.21/view/index.html
+++ b/docs/0.21/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.21/viewpagerandroid.html b/docs/0.21/viewpagerandroid.html
index a61e4c37fa7..75137b218d3 100644
--- a/docs/0.21/viewpagerandroid.html
+++ b/docs/0.21/viewpagerandroid.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.21/viewpagerandroid/index.html b/docs/0.21/viewpagerandroid/index.html
index a61e4c37fa7..75137b218d3 100644
--- a/docs/0.21/viewpagerandroid/index.html
+++ b/docs/0.21/viewpagerandroid/index.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.22/drawerlayoutandroid.html b/docs/0.22/drawerlayoutandroid.html
index 6dcaed172d9..22c0589196f 100644
--- a/docs/0.22/drawerlayoutandroid.html
+++ b/docs/0.22/drawerlayoutandroid.html
@@ -214,7 +214,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.22/drawerlayoutandroid/index.html b/docs/0.22/drawerlayoutandroid/index.html
index 6dcaed172d9..22c0589196f 100644
--- a/docs/0.22/drawerlayoutandroid/index.html
+++ b/docs/0.22/drawerlayoutandroid/index.html
@@ -214,7 +214,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.22/view.html b/docs/0.22/view.html
index 4a08113f973..ec586929922 100644
--- a/docs/0.22/view.html
+++ b/docs/0.22/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.22/view/index.html b/docs/0.22/view/index.html
index 4a08113f973..ec586929922 100644
--- a/docs/0.22/view/index.html
+++ b/docs/0.22/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.22/viewpagerandroid.html b/docs/0.22/viewpagerandroid.html
index a72e8df44dd..7644af0e454 100644
--- a/docs/0.22/viewpagerandroid.html
+++ b/docs/0.22/viewpagerandroid.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.22/viewpagerandroid/index.html b/docs/0.22/viewpagerandroid/index.html
index a72e8df44dd..7644af0e454 100644
--- a/docs/0.22/viewpagerandroid/index.html
+++ b/docs/0.22/viewpagerandroid/index.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.23/drawerlayoutandroid.html b/docs/0.23/drawerlayoutandroid.html
index 46135c448f7..60a79c5efcf 100644
--- a/docs/0.23/drawerlayoutandroid.html
+++ b/docs/0.23/drawerlayoutandroid.html
@@ -214,7 +214,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.23/drawerlayoutandroid/index.html b/docs/0.23/drawerlayoutandroid/index.html
index 46135c448f7..60a79c5efcf 100644
--- a/docs/0.23/drawerlayoutandroid/index.html
+++ b/docs/0.23/drawerlayoutandroid/index.html
@@ -214,7 +214,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.23/view.html b/docs/0.23/view.html
index ae9b61ec155..c30750d6810 100644
--- a/docs/0.23/view.html
+++ b/docs/0.23/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.23/view/index.html b/docs/0.23/view/index.html
index ae9b61ec155..c30750d6810 100644
--- a/docs/0.23/view/index.html
+++ b/docs/0.23/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.23/viewpagerandroid.html b/docs/0.23/viewpagerandroid.html
index 7384afde4e1..f61318412e6 100644
--- a/docs/0.23/viewpagerandroid.html
+++ b/docs/0.23/viewpagerandroid.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.23/viewpagerandroid/index.html b/docs/0.23/viewpagerandroid/index.html
index 7384afde4e1..f61318412e6 100644
--- a/docs/0.23/viewpagerandroid/index.html
+++ b/docs/0.23/viewpagerandroid/index.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.24/drawerlayoutandroid.html b/docs/0.24/drawerlayoutandroid.html
index 065739d93de..ec96a03019b 100644
--- a/docs/0.24/drawerlayoutandroid.html
+++ b/docs/0.24/drawerlayoutandroid.html
@@ -215,7 +215,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.24/drawerlayoutandroid/index.html b/docs/0.24/drawerlayoutandroid/index.html
index 065739d93de..ec96a03019b 100644
--- a/docs/0.24/drawerlayoutandroid/index.html
+++ b/docs/0.24/drawerlayoutandroid/index.html
@@ -215,7 +215,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.24/view.html b/docs/0.24/view.html
index a4413385aff..388b835aef6 100644
--- a/docs/0.24/view.html
+++ b/docs/0.24/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.24/view/index.html b/docs/0.24/view/index.html
index a4413385aff..388b835aef6 100644
--- a/docs/0.24/view/index.html
+++ b/docs/0.24/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.24/viewpagerandroid.html b/docs/0.24/viewpagerandroid.html
index e23eff84c52..faece9251e3 100644
--- a/docs/0.24/viewpagerandroid.html
+++ b/docs/0.24/viewpagerandroid.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.24/viewpagerandroid/index.html b/docs/0.24/viewpagerandroid/index.html
index e23eff84c52..faece9251e3 100644
--- a/docs/0.24/viewpagerandroid/index.html
+++ b/docs/0.24/viewpagerandroid/index.html
@@ -165,7 +165,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.25/drawerlayoutandroid.html b/docs/0.25/drawerlayoutandroid.html
index 35d3f8cdffb..844d80cc5bc 100644
--- a/docs/0.25/drawerlayoutandroid.html
+++ b/docs/0.25/drawerlayoutandroid.html
@@ -216,7 +216,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.25/drawerlayoutandroid/index.html b/docs/0.25/drawerlayoutandroid/index.html
index 35d3f8cdffb..844d80cc5bc 100644
--- a/docs/0.25/drawerlayoutandroid/index.html
+++ b/docs/0.25/drawerlayoutandroid/index.html
@@ -216,7 +216,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.25/view.html b/docs/0.25/view.html
index f5cdad5bb22..d001acc29e8 100644
--- a/docs/0.25/view.html
+++ b/docs/0.25/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.25/view/index.html b/docs/0.25/view/index.html
index f5cdad5bb22..d001acc29e8 100644
--- a/docs/0.25/view/index.html
+++ b/docs/0.25/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.25/viewpagerandroid.html b/docs/0.25/viewpagerandroid.html
index 0f6307b6c92..b61554b1b84 100644
--- a/docs/0.25/viewpagerandroid.html
+++ b/docs/0.25/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.25/viewpagerandroid/index.html b/docs/0.25/viewpagerandroid/index.html
index 0f6307b6c92..b61554b1b84 100644
--- a/docs/0.25/viewpagerandroid/index.html
+++ b/docs/0.25/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.26/drawerlayoutandroid.html b/docs/0.26/drawerlayoutandroid.html
index 12f6d8956e6..1f582fcd2c9 100644
--- a/docs/0.26/drawerlayoutandroid.html
+++ b/docs/0.26/drawerlayoutandroid.html
@@ -216,7 +216,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.26/drawerlayoutandroid/index.html b/docs/0.26/drawerlayoutandroid/index.html
index 12f6d8956e6..1f582fcd2c9 100644
--- a/docs/0.26/drawerlayoutandroid/index.html
+++ b/docs/0.26/drawerlayoutandroid/index.html
@@ -216,7 +216,7 @@
 <ul>
 <li>idle, meaning there is no interaction with the navigation view happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the navigation view</li>
-<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the navigation view, and the navigation view is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.26/view.html b/docs/0.26/view.html
index 7635e4f820d..218362245ee 100644
--- a/docs/0.26/view.html
+++ b/docs/0.26/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.26/view/index.html b/docs/0.26/view/index.html
index 7635e4f820d..218362245ee 100644
--- a/docs/0.26/view/index.html
+++ b/docs/0.26/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.27/view.html b/docs/0.27/view.html
index 83426bb3425..d8edf2ade3c 100644
--- a/docs/0.27/view.html
+++ b/docs/0.27/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.27/view/index.html b/docs/0.27/view/index.html
index 83426bb3425..d8edf2ade3c 100644
--- a/docs/0.27/view/index.html
+++ b/docs/0.27/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.28/view.html b/docs/0.28/view.html
index 3f7609a02a5..16563c45911 100644
--- a/docs/0.28/view.html
+++ b/docs/0.28/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.28/view/index.html b/docs/0.28/view/index.html
index 3f7609a02a5..16563c45911 100644
--- a/docs/0.28/view/index.html
+++ b/docs/0.28/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.29/image.html b/docs/0.29/image.html
index c9e5160f9db..8935724bfbb 100644
--- a/docs/0.29/image.html
+++ b/docs/0.29/image.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.29/image/index.html b/docs/0.29/image/index.html
index c9e5160f9db..8935724bfbb 100644
--- a/docs/0.29/image/index.html
+++ b/docs/0.29/image/index.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.29/view.html b/docs/0.29/view.html
index 4757b3cc518..9c8ce539d87 100644
--- a/docs/0.29/view.html
+++ b/docs/0.29/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.29/view/index.html b/docs/0.29/view/index.html
index 4757b3cc518..9c8ce539d87 100644
--- a/docs/0.29/view/index.html
+++ b/docs/0.29/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.30/image.html b/docs/0.30/image.html
index 0dcdf1e1989..24e7995b393 100644
--- a/docs/0.30/image.html
+++ b/docs/0.30/image.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.30/image/index.html b/docs/0.30/image/index.html
index 0dcdf1e1989..24e7995b393 100644
--- a/docs/0.30/image/index.html
+++ b/docs/0.30/image/index.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.30/view.html b/docs/0.30/view.html
index f6b2aeade01..6cb150ad310 100644
--- a/docs/0.30/view.html
+++ b/docs/0.30/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.30/view/index.html b/docs/0.30/view/index.html
index f6b2aeade01..6cb150ad310 100644
--- a/docs/0.30/view/index.html
+++ b/docs/0.30/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.30/viewpagerandroid.html b/docs/0.30/viewpagerandroid.html
index a0550ff3125..b144598d736 100644
--- a/docs/0.30/viewpagerandroid.html
+++ b/docs/0.30/viewpagerandroid.html
@@ -167,7 +167,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.30/viewpagerandroid/index.html b/docs/0.30/viewpagerandroid/index.html
index a0550ff3125..b144598d736 100644
--- a/docs/0.30/viewpagerandroid/index.html
+++ b/docs/0.30/viewpagerandroid/index.html
@@ -167,7 +167,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.31/image.html b/docs/0.31/image.html
index 6fd071275b2..2a6d97fd789 100644
--- a/docs/0.31/image.html
+++ b/docs/0.31/image.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.31/image/index.html b/docs/0.31/image/index.html
index 6fd071275b2..2a6d97fd789 100644
--- a/docs/0.31/image/index.html
+++ b/docs/0.31/image/index.html
@@ -225,7 +225,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.31/view.html b/docs/0.31/view.html
index 94c2750e53d..5f8c134a845 100644
--- a/docs/0.31/view.html
+++ b/docs/0.31/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.31/view/index.html b/docs/0.31/view/index.html
index 94c2750e53d..5f8c134a845 100644
--- a/docs/0.31/view/index.html
+++ b/docs/0.31/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.31/viewpagerandroid.html b/docs/0.31/viewpagerandroid.html
index d06b25d522c..0b11adbdaf9 100644
--- a/docs/0.31/viewpagerandroid.html
+++ b/docs/0.31/viewpagerandroid.html
@@ -167,7 +167,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.31/viewpagerandroid/index.html b/docs/0.31/viewpagerandroid/index.html
index d06b25d522c..0b11adbdaf9 100644
--- a/docs/0.31/viewpagerandroid/index.html
+++ b/docs/0.31/viewpagerandroid/index.html
@@ -167,7 +167,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.32/image.html b/docs/0.32/image.html
index 39d08ad4cba..05c8de88115 100644
--- a/docs/0.32/image.html
+++ b/docs/0.32/image.html
@@ -248,7 +248,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.32/image/index.html b/docs/0.32/image/index.html
index 39d08ad4cba..05c8de88115 100644
--- a/docs/0.32/image/index.html
+++ b/docs/0.32/image/index.html
@@ -248,7 +248,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.32/view.html b/docs/0.32/view.html
index f2145460e17..f334497183c 100644
--- a/docs/0.32/view.html
+++ b/docs/0.32/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.32/view/index.html b/docs/0.32/view/index.html
index f2145460e17..f334497183c 100644
--- a/docs/0.32/view/index.html
+++ b/docs/0.32/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.32/viewpagerandroid.html b/docs/0.32/viewpagerandroid.html
index 2809d756bef..fead89e2502 100644
--- a/docs/0.32/viewpagerandroid.html
+++ b/docs/0.32/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.32/viewpagerandroid/index.html b/docs/0.32/viewpagerandroid/index.html
index 2809d756bef..fead89e2502 100644
--- a/docs/0.32/viewpagerandroid/index.html
+++ b/docs/0.32/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.33/view.html b/docs/0.33/view.html
index 918ccba2f39..7538889dd4e 100644
--- a/docs/0.33/view.html
+++ b/docs/0.33/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.33/view/index.html b/docs/0.33/view/index.html
index 918ccba2f39..7538889dd4e 100644
--- a/docs/0.33/view/index.html
+++ b/docs/0.33/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.33/viewpagerandroid.html b/docs/0.33/viewpagerandroid.html
index 0b61d6b3a47..cbbeff4bd38 100644
--- a/docs/0.33/viewpagerandroid.html
+++ b/docs/0.33/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.33/viewpagerandroid/index.html b/docs/0.33/viewpagerandroid/index.html
index 0b61d6b3a47..cbbeff4bd38 100644
--- a/docs/0.33/viewpagerandroid/index.html
+++ b/docs/0.33/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.34/image.html b/docs/0.34/image.html
index 9d585c5e048..6893571c518 100644
--- a/docs/0.34/image.html
+++ b/docs/0.34/image.html
@@ -256,7 +256,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.34/image/index.html b/docs/0.34/image/index.html
index 9d585c5e048..6893571c518 100644
--- a/docs/0.34/image/index.html
+++ b/docs/0.34/image/index.html
@@ -256,7 +256,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.34/view.html b/docs/0.34/view.html
index a6ef1a90bee..6268516d114 100644
--- a/docs/0.34/view.html
+++ b/docs/0.34/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.34/view/index.html b/docs/0.34/view/index.html
index a6ef1a90bee..6268516d114 100644
--- a/docs/0.34/view/index.html
+++ b/docs/0.34/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.34/viewpagerandroid.html b/docs/0.34/viewpagerandroid.html
index 3c9a95fd62f..285b11a4fc3 100644
--- a/docs/0.34/viewpagerandroid.html
+++ b/docs/0.34/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.34/viewpagerandroid/index.html b/docs/0.34/viewpagerandroid/index.html
index 3c9a95fd62f..285b11a4fc3 100644
--- a/docs/0.34/viewpagerandroid/index.html
+++ b/docs/0.34/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.35/image.html b/docs/0.35/image.html
index 056cfcd8a8d..252cb5e5c90 100644
--- a/docs/0.35/image.html
+++ b/docs/0.35/image.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.35/image/index.html b/docs/0.35/image/index.html
index 056cfcd8a8d..252cb5e5c90 100644
--- a/docs/0.35/image/index.html
+++ b/docs/0.35/image/index.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.35/view.html b/docs/0.35/view.html
index b67049511ba..5eb785be630 100644
--- a/docs/0.35/view.html
+++ b/docs/0.35/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.35/view/index.html b/docs/0.35/view/index.html
index b67049511ba..5eb785be630 100644
--- a/docs/0.35/view/index.html
+++ b/docs/0.35/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.35/viewpagerandroid.html b/docs/0.35/viewpagerandroid.html
index f29927e14eb..9888af2a15e 100644
--- a/docs/0.35/viewpagerandroid.html
+++ b/docs/0.35/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.35/viewpagerandroid/index.html b/docs/0.35/viewpagerandroid/index.html
index f29927e14eb..9888af2a15e 100644
--- a/docs/0.35/viewpagerandroid/index.html
+++ b/docs/0.35/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.36/image.html b/docs/0.36/image.html
index dc8c842a073..5ca7335431c 100644
--- a/docs/0.36/image.html
+++ b/docs/0.36/image.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.36/image/index.html b/docs/0.36/image/index.html
index dc8c842a073..5ca7335431c 100644
--- a/docs/0.36/image/index.html
+++ b/docs/0.36/image/index.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.36/view.html b/docs/0.36/view.html
index 8270e5eca93..2303655ccfe 100644
--- a/docs/0.36/view.html
+++ b/docs/0.36/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.36/view/index.html b/docs/0.36/view/index.html
index 8270e5eca93..2303655ccfe 100644
--- a/docs/0.36/view/index.html
+++ b/docs/0.36/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.36/viewpagerandroid.html b/docs/0.36/viewpagerandroid.html
index 7c343960120..57125e992e7 100644
--- a/docs/0.36/viewpagerandroid.html
+++ b/docs/0.36/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.36/viewpagerandroid/index.html b/docs/0.36/viewpagerandroid/index.html
index 7c343960120..57125e992e7 100644
--- a/docs/0.36/viewpagerandroid/index.html
+++ b/docs/0.36/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.37/image.html b/docs/0.37/image.html
index 744a886c40b..a5749c3e3d4 100644
--- a/docs/0.37/image.html
+++ b/docs/0.37/image.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.37/image/index.html b/docs/0.37/image/index.html
index 744a886c40b..a5749c3e3d4 100644
--- a/docs/0.37/image/index.html
+++ b/docs/0.37/image/index.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.37/view.html b/docs/0.37/view.html
index 92ae169320a..410c2a525c4 100644
--- a/docs/0.37/view.html
+++ b/docs/0.37/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.37/view/index.html b/docs/0.37/view/index.html
index 92ae169320a..410c2a525c4 100644
--- a/docs/0.37/view/index.html
+++ b/docs/0.37/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.37/viewpagerandroid.html b/docs/0.37/viewpagerandroid.html
index 5ee89f5a944..29d88347a57 100644
--- a/docs/0.37/viewpagerandroid.html
+++ b/docs/0.37/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.37/viewpagerandroid/index.html b/docs/0.37/viewpagerandroid/index.html
index 5ee89f5a944..29d88347a57 100644
--- a/docs/0.37/viewpagerandroid/index.html
+++ b/docs/0.37/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.38/image.html b/docs/0.38/image.html
index 033af71fdb6..c1f098efabd 100644
--- a/docs/0.38/image.html
+++ b/docs/0.38/image.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.38/image/index.html b/docs/0.38/image/index.html
index 033af71fdb6..c1f098efabd 100644
--- a/docs/0.38/image/index.html
+++ b/docs/0.38/image/index.html
@@ -257,7 +257,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.38/view.html b/docs/0.38/view.html
index fd604a2fcc1..b127fff4f50 100644
--- a/docs/0.38/view.html
+++ b/docs/0.38/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.38/view/index.html b/docs/0.38/view/index.html
index fd604a2fcc1..b127fff4f50 100644
--- a/docs/0.38/view/index.html
+++ b/docs/0.38/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.38/viewpagerandroid.html b/docs/0.38/viewpagerandroid.html
index bfeb930576a..e491479c997 100644
--- a/docs/0.38/viewpagerandroid.html
+++ b/docs/0.38/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.38/viewpagerandroid/index.html b/docs/0.38/viewpagerandroid/index.html
index bfeb930576a..e491479c997 100644
--- a/docs/0.38/viewpagerandroid/index.html
+++ b/docs/0.38/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.39/image.html b/docs/0.39/image.html
index e946b71e429..7feeaa06c90 100644
--- a/docs/0.39/image.html
+++ b/docs/0.39/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.39/image/index.html b/docs/0.39/image/index.html
index e946b71e429..7feeaa06c90 100644
--- a/docs/0.39/image/index.html
+++ b/docs/0.39/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.39/view.html b/docs/0.39/view.html
index 658b8232c03..00b5773c808 100644
--- a/docs/0.39/view.html
+++ b/docs/0.39/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.39/view/index.html b/docs/0.39/view/index.html
index 658b8232c03..00b5773c808 100644
--- a/docs/0.39/view/index.html
+++ b/docs/0.39/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.39/viewpagerandroid.html b/docs/0.39/viewpagerandroid.html
index e4182e82211..cf9bb59716a 100644
--- a/docs/0.39/viewpagerandroid.html
+++ b/docs/0.39/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.39/viewpagerandroid/index.html b/docs/0.39/viewpagerandroid/index.html
index e4182e82211..cf9bb59716a 100644
--- a/docs/0.39/viewpagerandroid/index.html
+++ b/docs/0.39/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.40/image.html b/docs/0.40/image.html
index 4ac5b507ed4..66a906a61b9 100644
--- a/docs/0.40/image.html
+++ b/docs/0.40/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.40/image/index.html b/docs/0.40/image/index.html
index 4ac5b507ed4..66a906a61b9 100644
--- a/docs/0.40/image/index.html
+++ b/docs/0.40/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.40/view.html b/docs/0.40/view.html
index 8e663807968..924ab8c4b7d 100644
--- a/docs/0.40/view.html
+++ b/docs/0.40/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.40/view/index.html b/docs/0.40/view/index.html
index 8e663807968..924ab8c4b7d 100644
--- a/docs/0.40/view/index.html
+++ b/docs/0.40/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.40/viewpagerandroid.html b/docs/0.40/viewpagerandroid.html
index 922b95bf53e..1a7e5b3d8ad 100644
--- a/docs/0.40/viewpagerandroid.html
+++ b/docs/0.40/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.40/viewpagerandroid/index.html b/docs/0.40/viewpagerandroid/index.html
index 922b95bf53e..1a7e5b3d8ad 100644
--- a/docs/0.40/viewpagerandroid/index.html
+++ b/docs/0.40/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.41/image.html b/docs/0.41/image.html
index 6692388001e..cb3d9de1dc7 100644
--- a/docs/0.41/image.html
+++ b/docs/0.41/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.41/image/index.html b/docs/0.41/image/index.html
index 6692388001e..cb3d9de1dc7 100644
--- a/docs/0.41/image/index.html
+++ b/docs/0.41/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.41/view.html b/docs/0.41/view.html
index c2481d864b5..8853e2e6f9f 100644
--- a/docs/0.41/view.html
+++ b/docs/0.41/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.41/view/index.html b/docs/0.41/view/index.html
index c2481d864b5..8853e2e6f9f 100644
--- a/docs/0.41/view/index.html
+++ b/docs/0.41/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.41/viewpagerandroid.html b/docs/0.41/viewpagerandroid.html
index 0d8e8b7c748..92fbe12ec1a 100644
--- a/docs/0.41/viewpagerandroid.html
+++ b/docs/0.41/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.41/viewpagerandroid/index.html b/docs/0.41/viewpagerandroid/index.html
index 0d8e8b7c748..92fbe12ec1a 100644
--- a/docs/0.41/viewpagerandroid/index.html
+++ b/docs/0.41/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.42/image.html b/docs/0.42/image.html
index 1482b213f5a..bc5dfb5c849 100644
--- a/docs/0.42/image.html
+++ b/docs/0.42/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.42/image/index.html b/docs/0.42/image/index.html
index 1482b213f5a..bc5dfb5c849 100644
--- a/docs/0.42/image/index.html
+++ b/docs/0.42/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.42/view.html b/docs/0.42/view.html
index f1408d2062c..0b0895a7a50 100644
--- a/docs/0.42/view.html
+++ b/docs/0.42/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.42/view/index.html b/docs/0.42/view/index.html
index f1408d2062c..0b0895a7a50 100644
--- a/docs/0.42/view/index.html
+++ b/docs/0.42/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.42/viewpagerandroid.html b/docs/0.42/viewpagerandroid.html
index a8704c8580a..557b13dac20 100644
--- a/docs/0.42/viewpagerandroid.html
+++ b/docs/0.42/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.42/viewpagerandroid/index.html b/docs/0.42/viewpagerandroid/index.html
index a8704c8580a..557b13dac20 100644
--- a/docs/0.42/viewpagerandroid/index.html
+++ b/docs/0.42/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.43/image.html b/docs/0.43/image.html
index 1d5d1b52e55..7353ba1a185 100644
--- a/docs/0.43/image.html
+++ b/docs/0.43/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.43/image/index.html b/docs/0.43/image/index.html
index 1d5d1b52e55..7353ba1a185 100644
--- a/docs/0.43/image/index.html
+++ b/docs/0.43/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.43/touchablenativefeedback.html b/docs/0.43/touchablenativefeedback.html
index 1a40eba62a7..f0513a542be 100644
--- a/docs/0.43/touchablenativefeedback.html
+++ b/docs/0.43/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.43/touchablenativefeedback/index.html b/docs/0.43/touchablenativefeedback/index.html
index 1a40eba62a7..f0513a542be 100644
--- a/docs/0.43/touchablenativefeedback/index.html
+++ b/docs/0.43/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.43/view.html b/docs/0.43/view.html
index 523ebcb87e5..48b3ce7fe6a 100644
--- a/docs/0.43/view.html
+++ b/docs/0.43/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.43/view/index.html b/docs/0.43/view/index.html
index 523ebcb87e5..48b3ce7fe6a 100644
--- a/docs/0.43/view/index.html
+++ b/docs/0.43/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.43/viewpagerandroid.html b/docs/0.43/viewpagerandroid.html
index d0281677d3e..34dfaab8c41 100644
--- a/docs/0.43/viewpagerandroid.html
+++ b/docs/0.43/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.43/viewpagerandroid/index.html b/docs/0.43/viewpagerandroid/index.html
index d0281677d3e..34dfaab8c41 100644
--- a/docs/0.43/viewpagerandroid/index.html
+++ b/docs/0.43/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.44/flatlist.html b/docs/0.44/flatlist.html
index b08bce77d40..3e614f88e34 100644
--- a/docs/0.44/flatlist.html
+++ b/docs/0.44/flatlist.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.44/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props that aren't explicitly listed here along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.44/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props that aren't explicitly listed here along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.44/flatlist/index.html b/docs/0.44/flatlist/index.html
index b08bce77d40..3e614f88e34 100644
--- a/docs/0.44/flatlist/index.html
+++ b/docs/0.44/flatlist/index.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.44/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props that aren't explicitly listed here along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.44/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props that aren't explicitly listed here along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.44/image.html b/docs/0.44/image.html
index f4e597d1711..e36c6d7b4a4 100644
--- a/docs/0.44/image.html
+++ b/docs/0.44/image.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.44/image/index.html b/docs/0.44/image/index.html
index f4e597d1711..e36c6d7b4a4 100644
--- a/docs/0.44/image/index.html
+++ b/docs/0.44/image/index.html
@@ -262,7 +262,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.44/touchablenativefeedback.html b/docs/0.44/touchablenativefeedback.html
index 20c4498550d..057aa345537 100644
--- a/docs/0.44/touchablenativefeedback.html
+++ b/docs/0.44/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.44/touchablenativefeedback/index.html b/docs/0.44/touchablenativefeedback/index.html
index 20c4498550d..057aa345537 100644
--- a/docs/0.44/touchablenativefeedback/index.html
+++ b/docs/0.44/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.44/view.html b/docs/0.44/view.html
index 55326055ffc..fc50a601cb3 100644
--- a/docs/0.44/view.html
+++ b/docs/0.44/view.html
@@ -339,7 +339,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -349,7 +349,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.44/view/index.html b/docs/0.44/view/index.html
index 55326055ffc..fc50a601cb3 100644
--- a/docs/0.44/view/index.html
+++ b/docs/0.44/view/index.html
@@ -339,7 +339,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -349,7 +349,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.44/viewpagerandroid.html b/docs/0.44/viewpagerandroid.html
index 064062fb1ca..4025c5ae1d2 100644
--- a/docs/0.44/viewpagerandroid.html
+++ b/docs/0.44/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.44/viewpagerandroid/index.html b/docs/0.44/viewpagerandroid/index.html
index 064062fb1ca..4025c5ae1d2 100644
--- a/docs/0.44/viewpagerandroid/index.html
+++ b/docs/0.44/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.45/flatlist.html b/docs/0.45/flatlist.html
index 9d6d6740405..4d1212a310e 100644
--- a/docs/0.45/flatlist.html
+++ b/docs/0.45/flatlist.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.45/flatlist/index.html b/docs/0.45/flatlist/index.html
index 9d6d6740405..4d1212a310e 100644
--- a/docs/0.45/flatlist/index.html
+++ b/docs/0.45/flatlist/index.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.45/sectionlist.html b/docs/0.45/sectionlist.html
index 0aa48645b00..a311249140c 100644
--- a/docs/0.45/sectionlist.html
+++ b/docs/0.45/sectionlist.html
@@ -101,7 +101,7 @@
   ]}
 /&gt;
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.45/sectionlist/index.html b/docs/0.45/sectionlist/index.html
index 0aa48645b00..a311249140c 100644
--- a/docs/0.45/sectionlist/index.html
+++ b/docs/0.45/sectionlist/index.html
@@ -101,7 +101,7 @@
   ]}
 /&gt;
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.45/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.45/touchablenativefeedback.html b/docs/0.45/touchablenativefeedback.html
index 18af18166ea..44ad17b29f1 100644
--- a/docs/0.45/touchablenativefeedback.html
+++ b/docs/0.45/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.45/touchablenativefeedback/index.html b/docs/0.45/touchablenativefeedback/index.html
index 18af18166ea..44ad17b29f1 100644
--- a/docs/0.45/touchablenativefeedback/index.html
+++ b/docs/0.45/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.45/view.html b/docs/0.45/view.html
index 4b9afa1aa14..25914aa09f5 100644
--- a/docs/0.45/view.html
+++ b/docs/0.45/view.html
@@ -340,7 +340,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -350,7 +350,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.45/view/index.html b/docs/0.45/view/index.html
index 4b9afa1aa14..25914aa09f5 100644
--- a/docs/0.45/view/index.html
+++ b/docs/0.45/view/index.html
@@ -340,7 +340,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -350,7 +350,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.45/viewpagerandroid.html b/docs/0.45/viewpagerandroid.html
index 911408e3ec4..1cbfb3e5123 100644
--- a/docs/0.45/viewpagerandroid.html
+++ b/docs/0.45/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.45/viewpagerandroid/index.html b/docs/0.45/viewpagerandroid/index.html
index 911408e3ec4..1cbfb3e5123 100644
--- a/docs/0.45/viewpagerandroid/index.html
+++ b/docs/0.45/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.46/flatlist.html b/docs/0.46/flatlist.html
index acdad917cd7..8e736177639 100644
--- a/docs/0.46/flatlist.html
+++ b/docs/0.46/flatlist.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.46/flatlist/index.html b/docs/0.46/flatlist/index.html
index acdad917cd7..8e736177639 100644
--- a/docs/0.46/flatlist/index.html
+++ b/docs/0.46/flatlist/index.html
@@ -144,7 +144,7 @@ class MyList extends React.PureComponent {
   }
 }
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.46/sectionlist.html b/docs/0.46/sectionlist.html
index fad7911d886..cdf770a76d1 100644
--- a/docs/0.46/sectionlist.html
+++ b/docs/0.46/sectionlist.html
@@ -101,7 +101,7 @@
   ]}
 /&gt;
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.46/sectionlist/index.html b/docs/0.46/sectionlist/index.html
index fad7911d886..cdf770a76d1 100644
--- a/docs/0.46/sectionlist/index.html
+++ b/docs/0.46/sectionlist/index.html
@@ -101,7 +101,7 @@
   ]}
 /&gt;
 </code></pre>
-<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits it's props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
+<p>This is a convenience wrapper around <a href="/react-native/docs/0.46/virtualizedlist"><code>&lt;VirtualizedList&gt;</code></a>, and thus inherits its props (as well as those of <code>ScrollView</code>) that aren't explicitly listed here, along with the following caveats:</p>
 <ul>
 <li>Internal state is not preserved when content scrolls out of the render window. Make sure all your data is captured in the item data or external stores like Flux, Redux, or Relay.</li>
 <li>This is a <code>PureComponent</code> which means that it will not re-render if <code>props</code> remain shallow-equal. Make sure that everything your <code>renderItem</code> function depends on is passed as a prop (e.g. <code>extraData</code>) that is not <code>===</code> after updates, otherwise your UI may not update on changes. This includes the <code>data</code> prop and parent component state.</li>
diff --git a/docs/0.46/touchablenativefeedback.html b/docs/0.46/touchablenativefeedback.html
index 48cd5816019..321a41bdc10 100644
--- a/docs/0.46/touchablenativefeedback.html
+++ b/docs/0.46/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.46/touchablenativefeedback/index.html b/docs/0.46/touchablenativefeedback/index.html
index 48cd5816019..321a41bdc10 100644
--- a/docs/0.46/touchablenativefeedback/index.html
+++ b/docs/0.46/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.46/view.html b/docs/0.46/view.html
index 3ad3ac50d0f..6eca35b38c3 100644
--- a/docs/0.46/view.html
+++ b/docs/0.46/view.html
@@ -340,7 +340,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -350,7 +350,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.46/view/index.html b/docs/0.46/view/index.html
index 3ad3ac50d0f..6eca35b38c3 100644
--- a/docs/0.46/view/index.html
+++ b/docs/0.46/view/index.html
@@ -340,7 +340,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -350,7 +350,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.46/viewpagerandroid.html b/docs/0.46/viewpagerandroid.html
index fa8664f4673..3c5185442b1 100644
--- a/docs/0.46/viewpagerandroid.html
+++ b/docs/0.46/viewpagerandroid.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.46/viewpagerandroid/index.html b/docs/0.46/viewpagerandroid/index.html
index fa8664f4673..3c5185442b1 100644
--- a/docs/0.46/viewpagerandroid/index.html
+++ b/docs/0.46/viewpagerandroid/index.html
@@ -162,7 +162,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.47/touchablenativefeedback.html b/docs/0.47/touchablenativefeedback.html
index 8eac572b4de..dc62e1e7146 100644
--- a/docs/0.47/touchablenativefeedback.html
+++ b/docs/0.47/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.47/touchablenativefeedback/index.html b/docs/0.47/touchablenativefeedback/index.html
index 8eac572b4de..dc62e1e7146 100644
--- a/docs/0.47/touchablenativefeedback/index.html
+++ b/docs/0.47/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.47/view.html b/docs/0.47/view.html
index 7be1866535f..04e2429c7a8 100644
--- a/docs/0.47/view.html
+++ b/docs/0.47/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.47/view/index.html b/docs/0.47/view/index.html
index 7be1866535f..04e2429c7a8 100644
--- a/docs/0.47/view/index.html
+++ b/docs/0.47/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.47/viewpagerandroid.html b/docs/0.47/viewpagerandroid.html
index 2238cfff424..50b0811d5cb 100644
--- a/docs/0.47/viewpagerandroid.html
+++ b/docs/0.47/viewpagerandroid.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.47/viewpagerandroid/index.html b/docs/0.47/viewpagerandroid/index.html
index 2238cfff424..50b0811d5cb 100644
--- a/docs/0.47/viewpagerandroid/index.html
+++ b/docs/0.47/viewpagerandroid/index.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.48/image.html b/docs/0.48/image.html
index 42f60f55d52..74d95723258 100644
--- a/docs/0.48/image.html
+++ b/docs/0.48/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.48/image/index.html b/docs/0.48/image/index.html
index 42f60f55d52..74d95723258 100644
--- a/docs/0.48/image/index.html
+++ b/docs/0.48/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.48/touchablenativefeedback.html b/docs/0.48/touchablenativefeedback.html
index 3439269d295..c26c9386f39 100644
--- a/docs/0.48/touchablenativefeedback.html
+++ b/docs/0.48/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.48/touchablenativefeedback/index.html b/docs/0.48/touchablenativefeedback/index.html
index 3439269d295..c26c9386f39 100644
--- a/docs/0.48/touchablenativefeedback/index.html
+++ b/docs/0.48/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.48/view.html b/docs/0.48/view.html
index 6206d460e7d..9e416146c79 100644
--- a/docs/0.48/view.html
+++ b/docs/0.48/view.html
@@ -358,7 +358,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -368,7 +368,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.48/view/index.html b/docs/0.48/view/index.html
index 6206d460e7d..9e416146c79 100644
--- a/docs/0.48/view/index.html
+++ b/docs/0.48/view/index.html
@@ -358,7 +358,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -368,7 +368,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.48/viewpagerandroid.html b/docs/0.48/viewpagerandroid.html
index 2f0df84cb89..46a01c1d9b3 100644
--- a/docs/0.48/viewpagerandroid.html
+++ b/docs/0.48/viewpagerandroid.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.48/viewpagerandroid/index.html b/docs/0.48/viewpagerandroid/index.html
index 2f0df84cb89..46a01c1d9b3 100644
--- a/docs/0.48/viewpagerandroid/index.html
+++ b/docs/0.48/viewpagerandroid/index.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.49/image.html b/docs/0.49/image.html
index 41eb075d866..8b90740977a 100644
--- a/docs/0.49/image.html
+++ b/docs/0.49/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.49/image/index.html b/docs/0.49/image/index.html
index 41eb075d866..8b90740977a 100644
--- a/docs/0.49/image/index.html
+++ b/docs/0.49/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.49/touchablenativefeedback.html b/docs/0.49/touchablenativefeedback.html
index 6835b4c0e81..b8a0b2c249b 100644
--- a/docs/0.49/touchablenativefeedback.html
+++ b/docs/0.49/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.49/touchablenativefeedback/index.html b/docs/0.49/touchablenativefeedback/index.html
index 6835b4c0e81..b8a0b2c249b 100644
--- a/docs/0.49/touchablenativefeedback/index.html
+++ b/docs/0.49/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.49/view.html b/docs/0.49/view.html
index 6814605be59..560a23798d6 100644
--- a/docs/0.49/view.html
+++ b/docs/0.49/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.49/view/index.html b/docs/0.49/view/index.html
index 6814605be59..560a23798d6 100644
--- a/docs/0.49/view/index.html
+++ b/docs/0.49/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.49/viewpagerandroid.html b/docs/0.49/viewpagerandroid.html
index 7b2a08f9f52..918bbe1714d 100644
--- a/docs/0.49/viewpagerandroid.html
+++ b/docs/0.49/viewpagerandroid.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.49/viewpagerandroid/index.html b/docs/0.49/viewpagerandroid/index.html
index 7b2a08f9f52..918bbe1714d 100644
--- a/docs/0.49/viewpagerandroid/index.html
+++ b/docs/0.49/viewpagerandroid/index.html
@@ -163,7 +163,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.5/navigatorios.html b/docs/0.5/navigatorios.html
index ab010396586..26ce4b51ec0 100644
--- a/docs/0.5/navigatorios.html
+++ b/docs/0.5/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.5/navigatorios/index.html b/docs/0.5/navigatorios/index.html
index ab010396586..26ce4b51ec0 100644
--- a/docs/0.5/navigatorios/index.html
+++ b/docs/0.5/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.5/view.html b/docs/0.5/view.html
index d731eec66a1..5601b90702a 100644
--- a/docs/0.5/view.html
+++ b/docs/0.5/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.5/view/index.html b/docs/0.5/view/index.html
index d731eec66a1..5601b90702a 100644
--- a/docs/0.5/view/index.html
+++ b/docs/0.5/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.5/viewpagerandroid.html b/docs/0.5/viewpagerandroid.html
index 0ac174c85e6..d07e12ba801 100644
--- a/docs/0.5/viewpagerandroid.html
+++ b/docs/0.5/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.5/viewpagerandroid/index.html b/docs/0.5/viewpagerandroid/index.html
index 0ac174c85e6..d07e12ba801 100644
--- a/docs/0.5/viewpagerandroid/index.html
+++ b/docs/0.5/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.50/image.html b/docs/0.50/image.html
index a5c1ad7afcf..f786f202f7c 100644
--- a/docs/0.50/image.html
+++ b/docs/0.50/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.50/image/index.html b/docs/0.50/image/index.html
index a5c1ad7afcf..f786f202f7c 100644
--- a/docs/0.50/image/index.html
+++ b/docs/0.50/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.50/touchablenativefeedback.html b/docs/0.50/touchablenativefeedback.html
index 2cece8de332..7c348ed0a30 100644
--- a/docs/0.50/touchablenativefeedback.html
+++ b/docs/0.50/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.50/touchablenativefeedback/index.html b/docs/0.50/touchablenativefeedback/index.html
index 2cece8de332..7c348ed0a30 100644
--- a/docs/0.50/touchablenativefeedback/index.html
+++ b/docs/0.50/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.50/view.html b/docs/0.50/view.html
index d619546c157..f3cf3ece07a 100644
--- a/docs/0.50/view.html
+++ b/docs/0.50/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.50/view/index.html b/docs/0.50/view/index.html
index d619546c157..f3cf3ece07a 100644
--- a/docs/0.50/view/index.html
+++ b/docs/0.50/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.50/viewpagerandroid.html b/docs/0.50/viewpagerandroid.html
index 558f910dbf1..5821f79653f 100644
--- a/docs/0.50/viewpagerandroid.html
+++ b/docs/0.50/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.50/viewpagerandroid/index.html b/docs/0.50/viewpagerandroid/index.html
index 558f910dbf1..5821f79653f 100644
--- a/docs/0.50/viewpagerandroid/index.html
+++ b/docs/0.50/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.51/image.html b/docs/0.51/image.html
index c6ea1e379af..fde321bc9de 100644
--- a/docs/0.51/image.html
+++ b/docs/0.51/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.51/image/index.html b/docs/0.51/image/index.html
index c6ea1e379af..fde321bc9de 100644
--- a/docs/0.51/image/index.html
+++ b/docs/0.51/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.51/touchablenativefeedback.html b/docs/0.51/touchablenativefeedback.html
index f0e9031c9a7..d9a397ad111 100644
--- a/docs/0.51/touchablenativefeedback.html
+++ b/docs/0.51/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.51/touchablenativefeedback/index.html b/docs/0.51/touchablenativefeedback/index.html
index f0e9031c9a7..d9a397ad111 100644
--- a/docs/0.51/touchablenativefeedback/index.html
+++ b/docs/0.51/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.51/view.html b/docs/0.51/view.html
index 8216cc77b98..749d27d0d4c 100644
--- a/docs/0.51/view.html
+++ b/docs/0.51/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.51/view/index.html b/docs/0.51/view/index.html
index 8216cc77b98..749d27d0d4c 100644
--- a/docs/0.51/view/index.html
+++ b/docs/0.51/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.51/viewpagerandroid.html b/docs/0.51/viewpagerandroid.html
index a61ee40b861..82fc1b04706 100644
--- a/docs/0.51/viewpagerandroid.html
+++ b/docs/0.51/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.51/viewpagerandroid/index.html b/docs/0.51/viewpagerandroid/index.html
index a61ee40b861..82fc1b04706 100644
--- a/docs/0.51/viewpagerandroid/index.html
+++ b/docs/0.51/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.52/image.html b/docs/0.52/image.html
index c0c5a223311..ca43385e376 100644
--- a/docs/0.52/image.html
+++ b/docs/0.52/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.52/image/index.html b/docs/0.52/image/index.html
index c0c5a223311..ca43385e376 100644
--- a/docs/0.52/image/index.html
+++ b/docs/0.52/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.52/touchablenativefeedback.html b/docs/0.52/touchablenativefeedback.html
index e8df64698ba..ce1096a8e43 100644
--- a/docs/0.52/touchablenativefeedback.html
+++ b/docs/0.52/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.52/touchablenativefeedback/index.html b/docs/0.52/touchablenativefeedback/index.html
index e8df64698ba..ce1096a8e43 100644
--- a/docs/0.52/touchablenativefeedback/index.html
+++ b/docs/0.52/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.52/view.html b/docs/0.52/view.html
index 7b8875c3517..1e844d69bf4 100644
--- a/docs/0.52/view.html
+++ b/docs/0.52/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.52/view/index.html b/docs/0.52/view/index.html
index 7b8875c3517..1e844d69bf4 100644
--- a/docs/0.52/view/index.html
+++ b/docs/0.52/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.52/viewpagerandroid.html b/docs/0.52/viewpagerandroid.html
index 23128a3cdfc..0e3ba79b659 100644
--- a/docs/0.52/viewpagerandroid.html
+++ b/docs/0.52/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.52/viewpagerandroid/index.html b/docs/0.52/viewpagerandroid/index.html
index 23128a3cdfc..0e3ba79b659 100644
--- a/docs/0.52/viewpagerandroid/index.html
+++ b/docs/0.52/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.53/image.html b/docs/0.53/image.html
index cc2b2b398ac..2a83f5236d7 100644
--- a/docs/0.53/image.html
+++ b/docs/0.53/image.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.53/image/index.html b/docs/0.53/image/index.html
index cc2b2b398ac..2a83f5236d7 100644
--- a/docs/0.53/image/index.html
+++ b/docs/0.53/image/index.html
@@ -309,7 +309,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.53/touchablenativefeedback.html b/docs/0.53/touchablenativefeedback.html
index 94616f90818..af250a6fc7c 100644
--- a/docs/0.53/touchablenativefeedback.html
+++ b/docs/0.53/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.53/touchablenativefeedback/index.html b/docs/0.53/touchablenativefeedback/index.html
index 94616f90818..af250a6fc7c 100644
--- a/docs/0.53/touchablenativefeedback/index.html
+++ b/docs/0.53/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.53/view.html b/docs/0.53/view.html
index 3b214566b8f..2c51c0032a1 100644
--- a/docs/0.53/view.html
+++ b/docs/0.53/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.53/view/index.html b/docs/0.53/view/index.html
index 3b214566b8f..2c51c0032a1 100644
--- a/docs/0.53/view/index.html
+++ b/docs/0.53/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.53/viewpagerandroid.html b/docs/0.53/viewpagerandroid.html
index f94093eccde..098edbec2d3 100644
--- a/docs/0.53/viewpagerandroid.html
+++ b/docs/0.53/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.53/viewpagerandroid/index.html b/docs/0.53/viewpagerandroid/index.html
index f94093eccde..098edbec2d3 100644
--- a/docs/0.53/viewpagerandroid/index.html
+++ b/docs/0.53/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.54/image.html b/docs/0.54/image.html
index dff07129f17..b82a5a37da5 100644
--- a/docs/0.54/image.html
+++ b/docs/0.54/image.html
@@ -311,7 +311,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 <li><p><code>center</code>: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.</p></li>
 </ul>
 <table>
diff --git a/docs/0.54/image/index.html b/docs/0.54/image/index.html
index dff07129f17..b82a5a37da5 100644
--- a/docs/0.54/image/index.html
+++ b/docs/0.54/image/index.html
@@ -311,7 +311,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 <li><p><code>center</code>: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.</p></li>
 </ul>
 <table>
diff --git a/docs/0.54/touchablenativefeedback.html b/docs/0.54/touchablenativefeedback.html
index ef7014c0f40..74e987053d8 100644
--- a/docs/0.54/touchablenativefeedback.html
+++ b/docs/0.54/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.54/touchablenativefeedback/index.html b/docs/0.54/touchablenativefeedback/index.html
index ef7014c0f40..74e987053d8 100644
--- a/docs/0.54/touchablenativefeedback/index.html
+++ b/docs/0.54/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.54/view.html b/docs/0.54/view.html
index 385a482b501..658a2f100da 100644
--- a/docs/0.54/view.html
+++ b/docs/0.54/view.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.54/view/index.html b/docs/0.54/view/index.html
index 385a482b501..658a2f100da 100644
--- a/docs/0.54/view/index.html
+++ b/docs/0.54/view/index.html
@@ -354,7 +354,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -364,7 +364,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.54/viewpagerandroid.html b/docs/0.54/viewpagerandroid.html
index ecc51659c46..fb550d3da13 100644
--- a/docs/0.54/viewpagerandroid.html
+++ b/docs/0.54/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.54/viewpagerandroid/index.html b/docs/0.54/viewpagerandroid/index.html
index ecc51659c46..fb550d3da13 100644
--- a/docs/0.54/viewpagerandroid/index.html
+++ b/docs/0.54/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.55/image.html b/docs/0.55/image.html
index 759131be1a9..ab3611cd5aa 100644
--- a/docs/0.55/image.html
+++ b/docs/0.55/image.html
@@ -312,7 +312,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 <li><p><code>center</code>: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.</p></li>
 </ul>
 <table>
diff --git a/docs/0.55/image/index.html b/docs/0.55/image/index.html
index 759131be1a9..ab3611cd5aa 100644
--- a/docs/0.55/image/index.html
+++ b/docs/0.55/image/index.html
@@ -312,7 +312,7 @@ AppRegistry.registerComponent(
 <li><p><code>cover</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or larger than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>contain</code>: Scale the image uniformly (maintain the image's aspect ratio) so that both dimensions (width and height) of the image will be equal to or less than the corresponding dimension of the view (minus padding).</p></li>
 <li><p><code>stretch</code>: Scale width and height independently, This may change the aspect ratio of the src.</p></li>
-<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep it's size and aspect ratio. (iOS only)</p></li>
+<li><p><code>repeat</code>: Repeat the image to cover the frame of the view. The image will keep its size and aspect ratio. (iOS only)</p></li>
 <li><p><code>center</code>: Center the image in the view along both dimensions. If the image is larger than the view, scale it down uniformly so that it is contained in the view.</p></li>
 </ul>
 <table>
diff --git a/docs/0.55/touchablenativefeedback.html b/docs/0.55/touchablenativefeedback.html
index ee32262a755..fbbb081f7bc 100644
--- a/docs/0.55/touchablenativefeedback.html
+++ b/docs/0.55/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.55/touchablenativefeedback/index.html b/docs/0.55/touchablenativefeedback/index.html
index ee32262a755..fbbb081f7bc 100644
--- a/docs/0.55/touchablenativefeedback/index.html
+++ b/docs/0.55/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.55/view.html b/docs/0.55/view.html
index 73e9283cfd0..34c29bd805a 100644
--- a/docs/0.55/view.html
+++ b/docs/0.55/view.html
@@ -355,7 +355,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -365,7 +365,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.55/view/index.html b/docs/0.55/view/index.html
index 73e9283cfd0..34c29bd805a 100644
--- a/docs/0.55/view/index.html
+++ b/docs/0.55/view/index.html
@@ -355,7 +355,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -365,7 +365,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.55/viewpagerandroid.html b/docs/0.55/viewpagerandroid.html
index b5f49205253..9d1602338a0 100644
--- a/docs/0.55/viewpagerandroid.html
+++ b/docs/0.55/viewpagerandroid.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.55/viewpagerandroid/index.html b/docs/0.55/viewpagerandroid/index.html
index b5f49205253..9d1602338a0 100644
--- a/docs/0.55/viewpagerandroid/index.html
+++ b/docs/0.55/viewpagerandroid/index.html
@@ -166,7 +166,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.56/touchablenativefeedback.html b/docs/0.56/touchablenativefeedback.html
index 8524bdf0a04..2b3db87a410 100644
--- a/docs/0.56/touchablenativefeedback.html
+++ b/docs/0.56/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.56/touchablenativefeedback/index.html b/docs/0.56/touchablenativefeedback/index.html
index 8524bdf0a04..2b3db87a410 100644
--- a/docs/0.56/touchablenativefeedback/index.html
+++ b/docs/0.56/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.56/view.html b/docs/0.56/view.html
index 8d1477ebd40..fc96cc125b5 100644
--- a/docs/0.56/view.html
+++ b/docs/0.56/view.html
@@ -355,7 +355,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -365,7 +365,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.56/view/index.html b/docs/0.56/view/index.html
index 8d1477ebd40..fc96cc125b5 100644
--- a/docs/0.56/view/index.html
+++ b/docs/0.56/view/index.html
@@ -355,7 +355,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -365,7 +365,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.57/touchablenativefeedback.html b/docs/0.57/touchablenativefeedback.html
index 21585bcb268..6b7f8f63b6a 100644
--- a/docs/0.57/touchablenativefeedback.html
+++ b/docs/0.57/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.57/touchablenativefeedback/index.html b/docs/0.57/touchablenativefeedback/index.html
index 21585bcb268..6b7f8f63b6a 100644
--- a/docs/0.57/touchablenativefeedback/index.html
+++ b/docs/0.57/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.57/view.html b/docs/0.57/view.html
index 94c1930117a..64fe932a2ea 100644
--- a/docs/0.57/view.html
+++ b/docs/0.57/view.html
@@ -370,7 +370,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -380,7 +380,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.57/view/index.html b/docs/0.57/view/index.html
index 94c1930117a..64fe932a2ea 100644
--- a/docs/0.57/view/index.html
+++ b/docs/0.57/view/index.html
@@ -370,7 +370,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -380,7 +380,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.58/touchablenativefeedback.html b/docs/0.58/touchablenativefeedback.html
index 677bfc3481b..548a227957b 100644
--- a/docs/0.58/touchablenativefeedback.html
+++ b/docs/0.58/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.58/touchablenativefeedback/index.html b/docs/0.58/touchablenativefeedback/index.html
index 677bfc3481b..548a227957b 100644
--- a/docs/0.58/touchablenativefeedback/index.html
+++ b/docs/0.58/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.58/view.html b/docs/0.58/view.html
index 2fc55142950..d9665ebb9f0 100644
--- a/docs/0.58/view.html
+++ b/docs/0.58/view.html
@@ -370,7 +370,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -380,7 +380,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.58/view/index.html b/docs/0.58/view/index.html
index 2fc55142950..d9665ebb9f0 100644
--- a/docs/0.58/view/index.html
+++ b/docs/0.58/view/index.html
@@ -370,7 +370,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -380,7 +380,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.59/touchablenativefeedback.html b/docs/0.59/touchablenativefeedback.html
index 01bf35f191c..72188203e76 100644
--- a/docs/0.59/touchablenativefeedback.html
+++ b/docs/0.59/touchablenativefeedback.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.59/touchablenativefeedback/index.html b/docs/0.59/touchablenativefeedback/index.html
index 01bf35f191c..72188203e76 100644
--- a/docs/0.59/touchablenativefeedback/index.html
+++ b/docs/0.59/touchablenativefeedback/index.html
@@ -146,7 +146,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.59/view.html b/docs/0.59/view.html
index 239f8af1c25..ed72debddc5 100644
--- a/docs/0.59/view.html
+++ b/docs/0.59/view.html
@@ -382,7 +382,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -392,7 +392,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.59/view/index.html b/docs/0.59/view/index.html
index 239f8af1c25..ed72debddc5 100644
--- a/docs/0.59/view/index.html
+++ b/docs/0.59/view/index.html
@@ -382,7 +382,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -392,7 +392,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: all;
diff --git a/docs/0.6/navigatorios.html b/docs/0.6/navigatorios.html
index f9f0ae02d32..b2310904853 100644
--- a/docs/0.6/navigatorios.html
+++ b/docs/0.6/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.6/navigatorios/index.html b/docs/0.6/navigatorios/index.html
index f9f0ae02d32..b2310904853 100644
--- a/docs/0.6/navigatorios/index.html
+++ b/docs/0.6/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.6/view.html b/docs/0.6/view.html
index 385d5ce9e66..d1310248619 100644
--- a/docs/0.6/view.html
+++ b/docs/0.6/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.6/view/index.html b/docs/0.6/view/index.html
index 385d5ce9e66..d1310248619 100644
--- a/docs/0.6/view/index.html
+++ b/docs/0.6/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.6/viewpagerandroid.html b/docs/0.6/viewpagerandroid.html
index 1aa855b0e70..167c25a436a 100644
--- a/docs/0.6/viewpagerandroid.html
+++ b/docs/0.6/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.6/viewpagerandroid/index.html b/docs/0.6/viewpagerandroid/index.html
index 1aa855b0e70..167c25a436a 100644
--- a/docs/0.6/viewpagerandroid/index.html
+++ b/docs/0.6/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.60/touchablenativefeedback.html b/docs/0.60/touchablenativefeedback.html
index 66bf9102d42..c46c4a4f1eb 100644
--- a/docs/0.60/touchablenativefeedback.html
+++ b/docs/0.60/touchablenativefeedback.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.60/touchablenativefeedback/index.html b/docs/0.60/touchablenativefeedback/index.html
index 66bf9102d42..c46c4a4f1eb 100644
--- a/docs/0.60/touchablenativefeedback/index.html
+++ b/docs/0.60/touchablenativefeedback/index.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/0.7/navigatorios.html b/docs/0.7/navigatorios.html
index a7a759a5a9c..dfdfb9e8a3b 100644
--- a/docs/0.7/navigatorios.html
+++ b/docs/0.7/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.7/navigatorios/index.html b/docs/0.7/navigatorios/index.html
index a7a759a5a9c..dfdfb9e8a3b 100644
--- a/docs/0.7/navigatorios/index.html
+++ b/docs/0.7/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.7/view.html b/docs/0.7/view.html
index 19746134a15..a58c278a370 100644
--- a/docs/0.7/view.html
+++ b/docs/0.7/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.7/view/index.html b/docs/0.7/view/index.html
index 19746134a15..a58c278a370 100644
--- a/docs/0.7/view/index.html
+++ b/docs/0.7/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.7/viewpagerandroid.html b/docs/0.7/viewpagerandroid.html
index 67a8ffdfddd..93bc967283c 100644
--- a/docs/0.7/viewpagerandroid.html
+++ b/docs/0.7/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.7/viewpagerandroid/index.html b/docs/0.7/viewpagerandroid/index.html
index 67a8ffdfddd..93bc967283c 100644
--- a/docs/0.7/viewpagerandroid/index.html
+++ b/docs/0.7/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.8/navigatorios.html b/docs/0.8/navigatorios.html
index 676f78b0e91..2ba5fedad92 100644
--- a/docs/0.8/navigatorios.html
+++ b/docs/0.8/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.8/navigatorios/index.html b/docs/0.8/navigatorios/index.html
index 676f78b0e91..2ba5fedad92 100644
--- a/docs/0.8/navigatorios/index.html
+++ b/docs/0.8/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.8/view.html b/docs/0.8/view.html
index ea655d31c51..fc9df5a201e 100644
--- a/docs/0.8/view.html
+++ b/docs/0.8/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.8/view/index.html b/docs/0.8/view/index.html
index ea655d31c51..fc9df5a201e 100644
--- a/docs/0.8/view/index.html
+++ b/docs/0.8/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.8/viewpagerandroid.html b/docs/0.8/viewpagerandroid.html
index 19883392c22..6a4a95f5c8a 100644
--- a/docs/0.8/viewpagerandroid.html
+++ b/docs/0.8/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.8/viewpagerandroid/index.html b/docs/0.8/viewpagerandroid/index.html
index 19883392c22..6a4a95f5c8a 100644
--- a/docs/0.8/viewpagerandroid/index.html
+++ b/docs/0.8/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.9/navigatorios.html b/docs/0.9/navigatorios.html
index 4306704ac1e..55187215941 100644
--- a/docs/0.9/navigatorios.html
+++ b/docs/0.9/navigatorios.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.9/navigatorios/index.html b/docs/0.9/navigatorios/index.html
index 4306704ac1e..55187215941 100644
--- a/docs/0.9/navigatorios/index.html
+++ b/docs/0.9/navigatorios/index.html
@@ -83,7 +83,7 @@
   );
 },
 </code></pre>
-<p>Now MyView will be rendered by the navigator. It will recieve the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
+<p>Now MyView will be rendered by the navigator. It will receive the route object in the <code>route</code> prop, a navigator, and all of the props specified in <code>passProps</code>.</p>
 <p>See the initialRoute propType for a complete definition of a route.</p>
 <h4><a class="anchor" aria-hidden="true" id="navigator"></a><a href="#navigator" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigator</h4>
 <p>A <code>navigator</code> is an object of navigation functions that a view can call. It is passed as a prop to any component rendered by NavigatorIOS.</p>
diff --git a/docs/0.9/view.html b/docs/0.9/view.html
index 5ad11cc2252..d564faf75d2 100644
--- a/docs/0.9/view.html
+++ b/docs/0.9/view.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.9/view/index.html b/docs/0.9/view/index.html
index 5ad11cc2252..d564faf75d2 100644
--- a/docs/0.9/view/index.html
+++ b/docs/0.9/view/index.html
@@ -303,7 +303,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
     <span class="hljs-attribute">pointer-events</span>: none;
 }
@@ -311,7 +311,7 @@
     <span class="hljs-attribute">pointer-events</span>: all;
 }
 </code></pre></li>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
     <span class="hljs-attribute">pointer-events</span>: all;
 }
diff --git a/docs/0.9/viewpagerandroid.html b/docs/0.9/viewpagerandroid.html
index 15c02914ce0..ffde591b641 100644
--- a/docs/0.9/viewpagerandroid.html
+++ b/docs/0.9/viewpagerandroid.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/0.9/viewpagerandroid/index.html b/docs/0.9/viewpagerandroid/index.html
index 15c02914ce0..ffde591b641 100644
--- a/docs/0.9/viewpagerandroid/index.html
+++ b/docs/0.9/viewpagerandroid/index.html
@@ -108,7 +108,7 @@ var styles = {
 <ul>
 <li>idle, meaning there is no interaction with the page scroller happening at the time</li>
 <li>dragging, meaning there is currently an interaction with the page scroller</li>
-<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing it's closing or opening animation</li>
+<li>settling, meaning that there was an interaction with the page scroller, and the page scroller is now finishing its closing or opening animation</li>
 </ul>
 <table>
 <thead>
diff --git a/docs/next/animations.html b/docs/next/animations.html
index c96e73d82c1..777f7d92c92 100644
--- a/docs/next/animations.html
+++ b/docs/next/animations.html
@@ -288,7 +288,7 @@ Animated<span class="token punctuation">.</span><span class="token function">tim
 </code></pre>
 <p>You can see the native driver in action by running the <a href="https://github.com/facebook/react-native/blob/master/RNTester/">RNTester app</a>, then loading the Native Animated Example. You can also take a look at the <a href="https://github.com/facebook/react-native/blob/master/RNTester/js/NativeAnimationsExample.js">source code</a> to learn how these examples were produced.</p>
 <h4><a class="anchor" aria-hidden="true" id="caveats"></a><a href="#caveats" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Caveats</h4>
-<p>Not everything you can do with <code>Animated</code> is currently supported by the native driver. The main limitation is that you can only animate non-layout properties: things like <code>transform</code> and <code>opacity</code> will work, but flexbox and position properties will not. When using <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
+<p>Not everything you can do with <code>Animated</code> is currently supported by the native driver. The main limitation is that you can only animate non-layout properties: things like <code>transform</code> and <code>opacity</code> will work, but Flexbox and position properties will not. When using <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
 <p>When an animation is running, it can prevent <code>VirtualizedList</code> components from rendering more rows. If you need to run a long or looping animation while the user is scrolling through a list, you can use <code>isInteraction: false</code> in your animation's config to prevent this issue.</p>
 <h3><a class="anchor" aria-hidden="true" id="bear-in-mind"></a><a href="#bear-in-mind" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bear in mind</h3>
 <p>While using transform styles such as <code>rotateY</code>, <code>rotateX</code>, and others ensure the transform style <code>perspective</code> is in place. At this time some animations may not render on Android without it. Example below.</p>
@@ -309,7 +309,7 @@ Animated<span class="token punctuation">.</span><span class="token function">tim
 <li><a href="https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js">NativeAnimationsExample</a></li>
 </ul>
 <h2><a class="anchor" aria-hidden="true" id="layoutanimation-api"></a><a href="#layoutanimation-api" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code>LayoutAnimation</code> API</h2>
-<p><code>LayoutAnimation</code> allows you to globally configure <code>create</code> and <code>update</code> animations that will be used for all views in the next render/layout cycle. This is useful for doing flexbox layout updates without bothering to measure or calculate specific properties in order to animate them directly, and is especially useful when layout changes may affect ancestors, for example a &quot;see more&quot; expansion that also increases the size of the parent and pushes down the row below which would otherwise require explicit coordination between the components in order to animate them all in sync.</p>
+<p><code>LayoutAnimation</code> allows you to globally configure <code>create</code> and <code>update</code> animations that will be used for all views in the next render/layout cycle. This is useful for doing Flexbox layout updates without bothering to measure or calculate specific properties in order to animate them directly, and is especially useful when layout changes may affect ancestors, for example a &quot;see more&quot; expansion that also increases the size of the parent and pushes down the row below which would otherwise require explicit coordination between the components in order to animate them all in sync.</p>
 <p>Note that although <code>LayoutAnimation</code> is very powerful and can be quite useful, it provides much less control than <code>Animated</code> and other animation libraries, so you may need to use another approach if you can't get <code>LayoutAnimation</code> to do what you want.</p>
 <p>Note that in order to get this to work on <strong>Android</strong> you need to set the following flags via <code>UIManager</code>:</p>
 <pre><code class="hljs css language-jsx">UIManager<span class="token punctuation">.</span>setLayoutAnimationEnabledExperimental <span class="token operator">&amp;&amp;</span>
diff --git a/docs/next/animations/index.html b/docs/next/animations/index.html
index c96e73d82c1..777f7d92c92 100644
--- a/docs/next/animations/index.html
+++ b/docs/next/animations/index.html
@@ -288,7 +288,7 @@ Animated<span class="token punctuation">.</span><span class="token function">tim
 </code></pre>
 <p>You can see the native driver in action by running the <a href="https://github.com/facebook/react-native/blob/master/RNTester/">RNTester app</a>, then loading the Native Animated Example. You can also take a look at the <a href="https://github.com/facebook/react-native/blob/master/RNTester/js/NativeAnimationsExample.js">source code</a> to learn how these examples were produced.</p>
 <h4><a class="anchor" aria-hidden="true" id="caveats"></a><a href="#caveats" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Caveats</h4>
-<p>Not everything you can do with <code>Animated</code> is currently supported by the native driver. The main limitation is that you can only animate non-layout properties: things like <code>transform</code> and <code>opacity</code> will work, but flexbox and position properties will not. When using <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
+<p>Not everything you can do with <code>Animated</code> is currently supported by the native driver. The main limitation is that you can only animate non-layout properties: things like <code>transform</code> and <code>opacity</code> will work, but Flexbox and position properties will not. When using <code>Animated.event</code>, it will only work with direct events and not bubbling events. This means it does not work with <code>PanResponder</code> but does work with things like <code>ScrollView#onScroll</code>.</p>
 <p>When an animation is running, it can prevent <code>VirtualizedList</code> components from rendering more rows. If you need to run a long or looping animation while the user is scrolling through a list, you can use <code>isInteraction: false</code> in your animation's config to prevent this issue.</p>
 <h3><a class="anchor" aria-hidden="true" id="bear-in-mind"></a><a href="#bear-in-mind" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bear in mind</h3>
 <p>While using transform styles such as <code>rotateY</code>, <code>rotateX</code>, and others ensure the transform style <code>perspective</code> is in place. At this time some animations may not render on Android without it. Example below.</p>
@@ -309,7 +309,7 @@ Animated<span class="token punctuation">.</span><span class="token function">tim
 <li><a href="https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js">NativeAnimationsExample</a></li>
 </ul>
 <h2><a class="anchor" aria-hidden="true" id="layoutanimation-api"></a><a href="#layoutanimation-api" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code>LayoutAnimation</code> API</h2>
-<p><code>LayoutAnimation</code> allows you to globally configure <code>create</code> and <code>update</code> animations that will be used for all views in the next render/layout cycle. This is useful for doing flexbox layout updates without bothering to measure or calculate specific properties in order to animate them directly, and is especially useful when layout changes may affect ancestors, for example a &quot;see more&quot; expansion that also increases the size of the parent and pushes down the row below which would otherwise require explicit coordination between the components in order to animate them all in sync.</p>
+<p><code>LayoutAnimation</code> allows you to globally configure <code>create</code> and <code>update</code> animations that will be used for all views in the next render/layout cycle. This is useful for doing Flexbox layout updates without bothering to measure or calculate specific properties in order to animate them directly, and is especially useful when layout changes may affect ancestors, for example a &quot;see more&quot; expansion that also increases the size of the parent and pushes down the row below which would otherwise require explicit coordination between the components in order to animate them all in sync.</p>
 <p>Note that although <code>LayoutAnimation</code> is very powerful and can be quite useful, it provides much less control than <code>Animated</code> and other animation libraries, so you may need to use another approach if you can't get <code>LayoutAnimation</code> to do what you want.</p>
 <p>Note that in order to get this to work on <strong>Android</strong> you need to set the following flags via <code>UIManager</code>:</p>
 <pre><code class="hljs css language-jsx">UIManager<span class="token punctuation">.</span>setLayoutAnimationEnabledExperimental <span class="token operator">&amp;&amp;</span>
diff --git a/docs/next/communication-ios.html b/docs/next/communication-ios.html
index d1c8513c9c0..b541f0f2b98 100644
--- a/docs/next/communication-ios.html
+++ b/docs/next/communication-ios.html
@@ -157,7 +157,7 @@ rootView.appProperties = @{<span class="hljs-string">@"images"</span> : imageLis
   [<span class="hljs-keyword">self</span>.view addSubview:rootView];
 }
 </code></pre>
-<p>When we have a fixed size root view, we need to respect its bounds on the JS side. In other words, we need to ensure that the React Native content can be contained within the fixed-size root view. The easiest way to ensure this is to use flexbox layout. If you use absolute positioning, and React components are visible outside the root view's bounds, you'll get overlap with native views, causing some features to behave unexpectedly. For instance, 'TouchableHighlight' will not highlight your touches outside the root view's bounds.</p>
+<p>When we have a fixed size root view, we need to respect its bounds on the JS side. In other words, we need to ensure that the React Native content can be contained within the fixed-size root view. The easiest way to ensure this is to use Flexbox layout. If you use absolute positioning, and React components are visible outside the root view's bounds, you'll get overlap with native views, causing some features to behave unexpectedly. For instance, 'TouchableHighlight' will not highlight your touches outside the root view's bounds.</p>
 <p>It's totally fine to update root view's size dynamically by re-setting its frame property. React Native will take care of the content's layout.</p>
 <h4><a class="anchor" aria-hidden="true" id="react-native-content-with-flexible-size"></a><a href="#react-native-content-with-flexible-size" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>React Native content with flexible size</h4>
 <p>In some cases we'd like to render content of initially unknown size. Let's say the size will be defined dynamically in JS. We have two solutions to this problem.</p>
diff --git a/docs/next/communication-ios/index.html b/docs/next/communication-ios/index.html
index d1c8513c9c0..b541f0f2b98 100644
--- a/docs/next/communication-ios/index.html
+++ b/docs/next/communication-ios/index.html
@@ -157,7 +157,7 @@ rootView.appProperties = @{<span class="hljs-string">@"images"</span> : imageLis
   [<span class="hljs-keyword">self</span>.view addSubview:rootView];
 }
 </code></pre>
-<p>When we have a fixed size root view, we need to respect its bounds on the JS side. In other words, we need to ensure that the React Native content can be contained within the fixed-size root view. The easiest way to ensure this is to use flexbox layout. If you use absolute positioning, and React components are visible outside the root view's bounds, you'll get overlap with native views, causing some features to behave unexpectedly. For instance, 'TouchableHighlight' will not highlight your touches outside the root view's bounds.</p>
+<p>When we have a fixed size root view, we need to respect its bounds on the JS side. In other words, we need to ensure that the React Native content can be contained within the fixed-size root view. The easiest way to ensure this is to use Flexbox layout. If you use absolute positioning, and React components are visible outside the root view's bounds, you'll get overlap with native views, causing some features to behave unexpectedly. For instance, 'TouchableHighlight' will not highlight your touches outside the root view's bounds.</p>
 <p>It's totally fine to update root view's size dynamically by re-setting its frame property. React Native will take care of the content's layout.</p>
 <h4><a class="anchor" aria-hidden="true" id="react-native-content-with-flexible-size"></a><a href="#react-native-content-with-flexible-size" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>React Native content with flexible size</h4>
 <p>In some cases we'd like to render content of initially unknown size. Let's say the size will be defined dynamically in JS. We have two solutions to this problem.</p>
diff --git a/docs/next/flexbox.html b/docs/next/flexbox.html
index 7226c5ea9c7..666edffd80d 100644
--- a/docs/next/flexbox.html
+++ b/docs/next/flexbox.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Layout with Flexbox · React Native</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content="en"/><meta property="og:title" content="Layout with Flexbox · React Native"/><meta property="og:type" content="website"/><meta property="og:url" content="https://facebook.github.io/react-native/"/><meta property="og:description" content="A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="twitter:card" content="summary"/><link rel="shortcut icon" href="/react-native/img/favicon.ico"/><link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/solarized-dark.min.css"/><link rel="alternate" type="application/atom+xml" href="https://facebook.github.io/react-native/blog/atom.xml" title="React Native Blog ATOM Feed"/><link rel="alternate" type="application/rss+xml" href="https://facebook.github.io/react-native/blog/feed.xml" title="React Native Blog RSS Feed"/><script>
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Layout with Flexbox · React Native</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content="en"/><meta property="og:title" content="Layout with Flexbox · React Native"/><meta property="og:type" content="website"/><meta property="og:url" content="https://facebook.github.io/react-native/"/><meta property="og:description" content="A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="twitter:card" content="summary"/><link rel="shortcut icon" href="/react-native/img/favicon.ico"/><link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/solarized-dark.min.css"/><link rel="alternate" type="application/atom+xml" href="https://facebook.github.io/react-native/blog/atom.xml" title="React Native Blog ATOM Feed"/><link rel="alternate" type="application/rss+xml" href="https://facebook.github.io/react-native/blog/feed.xml" title="React Native Blog RSS Feed"/><script>
               (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
               (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
               m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -68,7 +68,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://github.com/facebook/react-native-website/blob/master/docs/flexbox.md" target="_blank" rel="noreferrer noopener">Edit</a><h1 class="postHeaderTitle">Layout with Flexbox</h1></header><article><div><span><p>A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes.</p>
+        </script></nav></div><div class="container mainContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://github.com/facebook/react-native-website/blob/master/docs/flexbox.md" target="_blank" rel="noreferrer noopener">Edit</a><h1 class="postHeaderTitle">Layout with Flexbox</h1></header><article><div><span><p>A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes.</p>
 <p>You will normally use a combination of <code>flexDirection</code>, <code>alignItems</code>, and <code>justifyContent</code> to achieve the right layout.</p>
 <blockquote>
 <p>Flexbox works the same way in React Native as it does in CSS on the web, with a few exceptions. The defaults are different, with <code>flexDirection</code> defaulting to <code>column</code> instead of <code>row</code>, and the <code>flex</code> parameter only supporting a single number.</p>
diff --git a/docs/next/flexbox/index.html b/docs/next/flexbox/index.html
index 7226c5ea9c7..666edffd80d 100644
--- a/docs/next/flexbox/index.html
+++ b/docs/next/flexbox/index.html
@@ -1,4 +1,4 @@
-<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Layout with Flexbox · React Native</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content="en"/><meta property="og:title" content="Layout with Flexbox · React Native"/><meta property="og:type" content="website"/><meta property="og:url" content="https://facebook.github.io/react-native/"/><meta property="og:description" content="A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="twitter:card" content="summary"/><link rel="shortcut icon" href="/react-native/img/favicon.ico"/><link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/solarized-dark.min.css"/><link rel="alternate" type="application/atom+xml" href="https://facebook.github.io/react-native/blog/atom.xml" title="React Native Blog ATOM Feed"/><link rel="alternate" type="application/rss+xml" href="https://facebook.github.io/react-native/blog/feed.xml" title="React Native Blog RSS Feed"/><script>
+<!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta http-equiv="X-UA-Compatible" content="IE=edge"/><title>Layout with Flexbox · React Native</title><meta name="viewport" content="width=device-width"/><meta name="generator" content="Docusaurus"/><meta name="description" content="A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="docsearch:version" content="next"/><meta name="docsearch:language" content="en"/><meta property="og:title" content="Layout with Flexbox · React Native"/><meta property="og:type" content="website"/><meta property="og:url" content="https://facebook.github.io/react-native/"/><meta property="og:description" content="A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes."/><meta name="twitter:card" content="summary"/><link rel="shortcut icon" href="/react-native/img/favicon.ico"/><link rel="stylesheet" href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/solarized-dark.min.css"/><link rel="alternate" type="application/atom+xml" href="https://facebook.github.io/react-native/blog/atom.xml" title="React Native Blog ATOM Feed"/><link rel="alternate" type="application/rss+xml" href="https://facebook.github.io/react-native/blog/feed.xml" title="React Native Blog RSS Feed"/><script>
               (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
               (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
               m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
@@ -68,7 +68,7 @@
                 };
               }
             });
-        </script></nav></div><div class="container mainContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://github.com/facebook/react-native-website/blob/master/docs/flexbox.md" target="_blank" rel="noreferrer noopener">Edit</a><h1 class="postHeaderTitle">Layout with Flexbox</h1></header><article><div><span><p>A component can specify the layout of its children using the flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes.</p>
+        </script></nav></div><div class="container mainContainer"><div class="wrapper"><div class="post"><header class="postHeader"><a class="edit-page-link button" href="https://github.com/facebook/react-native-website/blob/master/docs/flexbox.md" target="_blank" rel="noreferrer noopener">Edit</a><h1 class="postHeaderTitle">Layout with Flexbox</h1></header><article><div><span><p>A component can specify the layout of its children using the Flexbox algorithm. Flexbox is designed to provide a consistent layout on different screen sizes.</p>
 <p>You will normally use a combination of <code>flexDirection</code>, <code>alignItems</code>, and <code>justifyContent</code> to achieve the right layout.</p>
 <blockquote>
 <p>Flexbox works the same way in React Native as it does in CSS on the web, with a few exceptions. The defaults are different, with <code>flexDirection</code> defaulting to <code>column</code> instead of <code>row</code>, and the <code>flex</code> parameter only supporting a single number.</p>
diff --git a/docs/next/integration-with-existing-apps.html b/docs/next/integration-with-existing-apps.html
index 25df756c256..e3b1ce76db3 100644
--- a/docs/next/integration-with-existing-apps.html
+++ b/docs/next/integration-with-existing-apps.html
@@ -192,7 +192,7 @@ target <span class="hljs-string">'NumberTileGame'</span> <span class="hljs-keywo
   pod <span class="hljs-string">'React-jsi'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsi'</span>
   pod <span class="hljs-string">'React-jsiexecutor'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsiexecutor'</span>
   pod <span class="hljs-string">'React-jsinspector'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsinspector'</span>
-  pod <span class="hljs-string">'yoga'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/yoga'</span>
+  pod <span class="hljs-string">'Yoga'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/yoga'</span>
 
   pod <span class="hljs-string">'DoubleConversion'</span>, :<span class="hljs-function"><span class="hljs-params">podspec</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'</span>
   pod <span class="hljs-string">'glog'</span>, :<span class="hljs-function"><span class="hljs-params">podspec</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/glog.podspec'</span>
@@ -221,7 +221,7 @@ target <span class="hljs-string">'swift-2048'</span> <span class="hljs-keyword">
     <span class="hljs-comment"># Add any other subspecs you want to use in your project</span>
   ]
   <span class="hljs-comment"># Explicitly include Yoga if you are using RN &gt;= 0.42.0</span>
-  pod <span class="hljs-string">"yoga"</span>, <span class="hljs-symbol">:path</span> =&gt; <span class="hljs-string">"../node_modules/react-native/ReactCommon/yoga"</span>
+  pod <span class="hljs-string">"Yoga"</span>, <span class="hljs-symbol">:path</span> =&gt; <span class="hljs-string">"../node_modules/react-native/ReactCommon/yoga"</span>
 
   <span class="hljs-comment"># Third party deps podspec link</span>
   pod <span class="hljs-string">'DoubleConversion'</span>, <span class="hljs-symbol">:podspec</span> =&gt; <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'</span>
diff --git a/docs/next/integration-with-existing-apps/index.html b/docs/next/integration-with-existing-apps/index.html
index 25df756c256..e3b1ce76db3 100644
--- a/docs/next/integration-with-existing-apps/index.html
+++ b/docs/next/integration-with-existing-apps/index.html
@@ -192,7 +192,7 @@ target <span class="hljs-string">'NumberTileGame'</span> <span class="hljs-keywo
   pod <span class="hljs-string">'React-jsi'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsi'</span>
   pod <span class="hljs-string">'React-jsiexecutor'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsiexecutor'</span>
   pod <span class="hljs-string">'React-jsinspector'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/jsinspector'</span>
-  pod <span class="hljs-string">'yoga'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/yoga'</span>
+  pod <span class="hljs-string">'Yoga'</span>, :<span class="hljs-function"><span class="hljs-params">path</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/ReactCommon/yoga'</span>
 
   pod <span class="hljs-string">'DoubleConversion'</span>, :<span class="hljs-function"><span class="hljs-params">podspec</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'</span>
   pod <span class="hljs-string">'glog'</span>, :<span class="hljs-function"><span class="hljs-params">podspec</span> =&gt;</span> <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/glog.podspec'</span>
@@ -221,7 +221,7 @@ target <span class="hljs-string">'swift-2048'</span> <span class="hljs-keyword">
     <span class="hljs-comment"># Add any other subspecs you want to use in your project</span>
   ]
   <span class="hljs-comment"># Explicitly include Yoga if you are using RN &gt;= 0.42.0</span>
-  pod <span class="hljs-string">"yoga"</span>, <span class="hljs-symbol">:path</span> =&gt; <span class="hljs-string">"../node_modules/react-native/ReactCommon/yoga"</span>
+  pod <span class="hljs-string">"Yoga"</span>, <span class="hljs-symbol">:path</span> =&gt; <span class="hljs-string">"../node_modules/react-native/ReactCommon/yoga"</span>
 
   <span class="hljs-comment"># Third party deps podspec link</span>
   pod <span class="hljs-string">'DoubleConversion'</span>, <span class="hljs-symbol">:podspec</span> =&gt; <span class="hljs-string">'../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'</span>
diff --git a/docs/next/native-modules-android.html b/docs/next/native-modules-android.html
index 17f384d8571..a492ddd52e0 100644
--- a/docs/next/native-modules-android.html
+++ b/docs/next/native-modules-android.html
@@ -330,7 +330,7 @@ params<span class="token punctuation">.</span><span class="token function">putSt
     <span class="token keyword">const</span> eventEmitter <span class="token operator">=</span> <span class="token keyword">new</span> <span class="token class-name">NativeEventEmitter</span><span class="token punctuation">(</span>NativeModules<span class="token punctuation">.</span>ToastExample<span class="token punctuation">)</span><span class="token punctuation">;</span>
     eventEmitter<span class="token punctuation">.</span><span class="token function">addListener</span><span class="token punctuation">(</span><span class="token string">'EventReminder'</span><span class="token punctuation">,</span> <span class="token punctuation">(</span><span class="token parameter">event</span><span class="token punctuation">)</span> <span class="token operator">=></span> <span class="token punctuation">{</span>
        console<span class="token punctuation">.</span><span class="token function">log</span><span class="token punctuation">(</span>event<span class="token punctuation">.</span>eventProperty<span class="token punctuation">)</span> <span class="token comment">// "someValue"</span>
-    <span class="token punctuation">}</span>
+    <span class="token punctuation">}</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
     <span class="token operator">...</span>
   <span class="token punctuation">}</span>
 </code></pre>
diff --git a/docs/next/native-modules-android/index.html b/docs/next/native-modules-android/index.html
index 17f384d8571..a492ddd52e0 100644
--- a/docs/next/native-modules-android/index.html
+++ b/docs/next/native-modules-android/index.html
@@ -330,7 +330,7 @@ params<span class="token punctuation">.</span><span class="token function">putSt
     <span class="token keyword">const</span> eventEmitter <span class="token operator">=</span> <span class="token keyword">new</span> <span class="token class-name">NativeEventEmitter</span><span class="token punctuation">(</span>NativeModules<span class="token punctuation">.</span>ToastExample<span class="token punctuation">)</span><span class="token punctuation">;</span>
     eventEmitter<span class="token punctuation">.</span><span class="token function">addListener</span><span class="token punctuation">(</span><span class="token string">'EventReminder'</span><span class="token punctuation">,</span> <span class="token punctuation">(</span><span class="token parameter">event</span><span class="token punctuation">)</span> <span class="token operator">=></span> <span class="token punctuation">{</span>
        console<span class="token punctuation">.</span><span class="token function">log</span><span class="token punctuation">(</span>event<span class="token punctuation">.</span>eventProperty<span class="token punctuation">)</span> <span class="token comment">// "someValue"</span>
-    <span class="token punctuation">}</span>
+    <span class="token punctuation">}</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
     <span class="token operator">...</span>
   <span class="token punctuation">}</span>
 </code></pre>
diff --git a/docs/next/text.html b/docs/next/text.html
index 9ec852f61ad..d71e8e91642 100644
--- a/docs/next/text.html
+++ b/docs/next/text.html
@@ -157,7 +157,7 @@
 <span class="token number">9</span><span class="token operator">-</span><span class="token number">17</span><span class="token punctuation">:</span> bold<span class="token punctuation">,</span> red
 </code></pre>
 <h2><a class="anchor" aria-hidden="true" id="containers"></a><a href="#containers" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Containers</h2>
-<p>The <code>&lt;Text&gt;</code> element is special relative to layout: everything inside is no longer using the flexbox layout but using text layout. This means that elements inside of a <code>&lt;Text&gt;</code> are no longer rectangles, but wrap when they see the end of the line.</p>
+<p>The <code>&lt;Text&gt;</code> element is special relative to layout: everything inside is no longer using the Flexbox layout but using text layout. This means that elements inside of a <code>&lt;Text&gt;</code> are no longer rectangles, but wrap when they see the end of the line.</p>
 <pre><code class="hljs css language-jsx"><span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
   <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>First part and <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;/</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
   <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>second part<span class="token tag"><span class="token tag"><span class="token punctuation">&lt;/</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
diff --git a/docs/next/text/index.html b/docs/next/text/index.html
index 9ec852f61ad..d71e8e91642 100644
--- a/docs/next/text/index.html
+++ b/docs/next/text/index.html
@@ -157,7 +157,7 @@
 <span class="token number">9</span><span class="token operator">-</span><span class="token number">17</span><span class="token punctuation">:</span> bold<span class="token punctuation">,</span> red
 </code></pre>
 <h2><a class="anchor" aria-hidden="true" id="containers"></a><a href="#containers" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Containers</h2>
-<p>The <code>&lt;Text&gt;</code> element is special relative to layout: everything inside is no longer using the flexbox layout but using text layout. This means that elements inside of a <code>&lt;Text&gt;</code> are no longer rectangles, but wrap when they see the end of the line.</p>
+<p>The <code>&lt;Text&gt;</code> element is special relative to layout: everything inside is no longer using the Flexbox layout but using text layout. This means that elements inside of a <code>&lt;Text&gt;</code> are no longer rectangles, but wrap when they see the end of the line.</p>
 <pre><code class="hljs css language-jsx"><span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
   <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>First part and <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;/</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
   <span class="token tag"><span class="token tag"><span class="token punctuation">&lt;</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>second part<span class="token tag"><span class="token tag"><span class="token punctuation">&lt;/</span><span class="token class-name">Text</span></span><span class="token punctuation">></span></span>
diff --git a/docs/next/touchablenativefeedback.html b/docs/next/touchablenativefeedback.html
index c63f6b6190a..50a4d6070e0 100644
--- a/docs/next/touchablenativefeedback.html
+++ b/docs/next/touchablenativefeedback.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/next/touchablenativefeedback/index.html b/docs/next/touchablenativefeedback/index.html
index c63f6b6190a..50a4d6070e0 100644
--- a/docs/next/touchablenativefeedback/index.html
+++ b/docs/next/touchablenativefeedback/index.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/next/view.html b/docs/next/view.html
index 4e86dfce46d..717f5d7c649 100644
--- a/docs/next/view.html
+++ b/docs/next/view.html
@@ -343,7 +343,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -353,7 +353,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: auto;
diff --git a/docs/next/view/index.html b/docs/next/view/index.html
index 4e86dfce46d..717f5d7c649 100644
--- a/docs/next/view/index.html
+++ b/docs/next/view/index.html
@@ -343,7 +343,7 @@
 <ul>
 <li><code>'auto'</code>: The View can be the target of touch events.</li>
 <li><code>'none'</code>: The View is never the target of touch events.</li>
-<li><code>'box-none'</code>: The View is never the target of touch events but it's subviews can be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-none'</code>: The View is never the target of touch events but its subviews can be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-none</span> {
      <span class="hljs-attribute">pointer-events</span>: none;
@@ -353,7 +353,7 @@
 }
 </code></pre>
 <ul>
-<li><code>'box-only'</code>: The view can be the target of touch events but it's subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
+<li><code>'box-only'</code>: The view can be the target of touch events but its subviews cannot be. It behaves like if the view had the following classes in CSS:</li>
 </ul>
 <pre><code class="hljs"><span class="hljs-selector-class">.box-only</span> {
      <span class="hljs-attribute">pointer-events</span>: auto;
diff --git a/docs/touchablenativefeedback.html b/docs/touchablenativefeedback.html
index f547d157234..388db85e599 100644
--- a/docs/touchablenativefeedback.html
+++ b/docs/touchablenativefeedback.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>
diff --git a/docs/touchablenativefeedback/index.html b/docs/touchablenativefeedback/index.html
index f547d157234..388db85e599 100644
--- a/docs/touchablenativefeedback/index.html
+++ b/docs/touchablenativefeedback/index.html
@@ -198,7 +198,7 @@
 </thead>
 <tbody>
 <tr><td>color</td><td>string</td><td>Yes</td><td>The ripple color</td></tr>
-<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside it's bounds</td></tr>
+<tr><td>borderless</td><td>boolean</td><td>Yes</td><td>If the ripple can render outside its bounds</td></tr>
 </tbody>
 </table>
 <hr>