Deploy website

Deploy website version based on 5000ce2423efc71bb27dea835950209538ebcafa
2025-11-01 09:14:26 +00:00 · 2019-10-07 17:19:31 +00:00
parent e3faa3b70e
commit af1862f592
361 changed files with 493 additions and 493 deletions
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -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;
 }
@@ -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;
 }
@@ -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>
@@ -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>
@@ -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>
--- a/Show More
+++ b/Show More