From 0a1ef9bc4d30af078634c7eb5f18c02fb27797fa Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Tue, 5 Dec 2017 19:58:34 +0000 Subject: [PATCH] Deploy website Deploy website version based on c06a5cffe6ada66f94f882f712bfb447bbd7284d --- docs/0.10/sectionlist.html | 2 +- docs/0.10/virtualizedlist.html | 2 +- docs/0.11/sectionlist.html | 2 +- docs/0.11/virtualizedlist.html | 2 +- docs/0.12/sectionlist.html | 2 +- docs/0.12/virtualizedlist.html | 2 +- docs/0.13/sectionlist.html | 2 +- docs/0.13/virtualizedlist.html | 2 +- docs/0.14/sectionlist.html | 2 +- docs/0.14/virtualizedlist.html | 2 +- docs/0.15/sectionlist.html | 2 +- docs/0.15/virtualizedlist.html | 2 +- docs/0.16/sectionlist.html | 2 +- docs/0.16/virtualizedlist.html | 2 +- docs/0.17/sectionlist.html | 2 +- docs/0.17/virtualizedlist.html | 2 +- docs/0.18/sectionlist.html | 2 +- docs/0.18/virtualizedlist.html | 2 +- docs/0.19/sectionlist.html | 2 +- docs/0.19/virtualizedlist.html | 2 +- docs/0.20/sectionlist.html | 2 +- docs/0.20/virtualizedlist.html | 2 +- docs/0.21/sectionlist.html | 2 +- docs/0.21/virtualizedlist.html | 2 +- docs/0.22/sectionlist.html | 2 +- docs/0.22/virtualizedlist.html | 2 +- docs/0.23/sectionlist.html | 2 +- docs/0.23/virtualizedlist.html | 2 +- docs/0.24/sectionlist.html | 2 +- docs/0.24/virtualizedlist.html | 2 +- docs/0.25/sectionlist.html | 2 +- docs/0.25/virtualizedlist.html | 2 +- docs/0.26/sectionlist.html | 2 +- docs/0.26/virtualizedlist.html | 2 +- docs/0.27/sectionlist.html | 2 +- docs/0.27/virtualizedlist.html | 2 +- docs/0.28/sectionlist.html | 2 +- docs/0.28/virtualizedlist.html | 2 +- docs/0.29/modal.html | 2 +- docs/0.29/sectionlist.html | 2 +- docs/0.29/text.html | 2 +- docs/0.29/textinput.html | 2 +- docs/0.29/virtualizedlist.html | 2 +- docs/0.30/modal.html | 2 +- docs/0.30/sectionlist.html | 2 +- docs/0.30/textinput.html | 2 +- docs/0.30/virtualizedlist.html | 2 +- docs/0.31/modal.html | 2 +- docs/0.31/sectionlist.html | 2 +- docs/0.31/textinput.html | 2 +- docs/0.31/virtualizedlist.html | 2 +- docs/0.32/modal.html | 2 +- docs/0.32/navigatorios.html | 2 +- docs/0.32/sectionlist.html | 2 +- docs/0.32/textinput.html | 2 +- docs/0.32/virtualizedlist.html | 2 +- docs/0.33/modal.html | 2 +- docs/0.33/navigatorios.html | 2 +- docs/0.33/sectionlist.html | 2 +- docs/0.33/textinput.html | 2 +- docs/0.33/virtualizedlist.html | 2 +- docs/0.34/modal.html | 2 +- docs/0.34/navigatorios.html | 2 +- docs/0.34/sectionlist.html | 2 +- docs/0.34/textinput.html | 2 +- docs/0.34/virtualizedlist.html | 2 +- docs/0.35/modal.html | 2 +- docs/0.35/navigatorios.html | 2 +- docs/0.35/sectionlist.html | 2 +- docs/0.35/textinput.html | 2 +- docs/0.35/virtualizedlist.html | 2 +- docs/0.36/navigatorios.html | 2 +- docs/0.36/sectionlist.html | 2 +- docs/0.36/textinput.html | 2 +- docs/0.36/virtualizedlist.html | 2 +- docs/0.37/navigatorios.html | 2 +- docs/0.37/sectionlist.html | 2 +- docs/0.37/textinput.html | 2 +- docs/0.37/virtualizedlist.html | 2 +- docs/0.38/navigatorios.html | 2 +- docs/0.38/sectionlist.html | 2 +- docs/0.38/textinput.html | 2 +- docs/0.38/virtualizedlist.html | 2 +- docs/0.39/navigatorios.html | 2 +- docs/0.39/sectionlist.html | 2 +- docs/0.39/textinput.html | 2 +- docs/0.39/virtualizedlist.html | 2 +- docs/0.40/navigatorios.html | 2 +- docs/0.40/sectionlist.html | 2 +- docs/0.40/textinput.html | 2 +- docs/0.40/virtualizedlist.html | 2 +- docs/0.41/navigatorios.html | 2 +- docs/0.41/sectionlist.html | 2 +- docs/0.41/textinput.html | 2 +- docs/0.41/virtualizedlist.html | 2 +- docs/0.42/sectionlist.html | 2 +- docs/0.42/virtualizedlist.html | 2 +- docs/0.43/scrollview.html | 2 +- docs/0.43/sectionlist.html | 2 +- docs/0.43/virtualizedlist.html | 2 +- docs/0.44/scrollview.html | 2 +- docs/0.44/sectionlist.html | 4 ++-- docs/0.44/virtualizedlist.html | 6 +++--- docs/0.45/scrollview.html | 2 +- docs/0.45/sectionlist.html | 4 ++-- docs/0.45/virtualizedlist.html | 6 +++--- docs/0.46/scrollview.html | 2 +- docs/0.46/sectionlist.html | 4 ++-- docs/0.46/virtualizedlist.html | 6 +++--- docs/0.47/scrollview.html | 2 +- docs/0.47/sectionlist.html | 4 ++-- docs/0.47/virtualizedlist.html | 6 +++--- docs/0.48/scrollview.html | 2 +- docs/0.48/sectionlist.html | 4 ++-- docs/0.48/virtualizedlist.html | 6 +++--- docs/0.49/scrollview.html | 2 +- docs/0.49/sectionlist.html | 2 +- docs/0.49/virtualizedlist.html | 6 +++--- docs/0.5/sectionlist.html | 2 +- docs/0.5/virtualizedlist.html | 2 +- docs/0.50/scrollview.html | 2 +- docs/0.50/sectionlist.html | 2 +- docs/0.6/sectionlist.html | 2 +- docs/0.6/virtualizedlist.html | 2 +- docs/0.7/sectionlist.html | 2 +- docs/0.7/virtualizedlist.html | 2 +- docs/0.8/sectionlist.html | 2 +- docs/0.8/virtualizedlist.html | 2 +- docs/0.9/sectionlist.html | 2 +- docs/0.9/virtualizedlist.html | 2 +- docs/next/contributing.html | 8 ++++---- docs/next/more-resources.html | 6 +++--- docs/next/virtualizedlist.html | 6 +++--- docs/scrollview.html | 2 +- docs/sectionlist.html | 2 +- 135 files changed, 159 insertions(+), 159 deletions(-) diff --git a/docs/0.10/sectionlist.html b/docs/0.10/sectionlist.html index b65f35f0b48..7131d66c3c2 100644 --- a/docs/0.10/sectionlist.html +++ b/docs/0.10/sectionlist.html @@ -12,7 +12,7 @@
  • Scroll loading.

    • If you don't need section support and want a simpler interface, use -<FlatList>.

    +<FlatList>.

    Simple Examples:

    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.10/virtualizedlist.html b/docs/0.10/virtualizedlist.html
index c6b1d332ed3..78c55187ed7 100644
--- a/docs/0.10/virtualizedlist.html
+++ b/docs/0.10/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.10
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.10
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.11/sectionlist.html b/docs/0.11/sectionlist.html
index ffc490862b7..e7ec51f5a46 100644
--- a/docs/0.11/sectionlist.html
+++ b/docs/0.11/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.11/virtualizedlist.html b/docs/0.11/virtualizedlist.html
index d18413c500b..2956fd5d44c 100644
--- a/docs/0.11/virtualizedlist.html
+++ b/docs/0.11/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.11
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.11
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.12/sectionlist.html b/docs/0.12/sectionlist.html
index a5b7e0d8a76..40461a05d74 100644
--- a/docs/0.12/sectionlist.html
+++ b/docs/0.12/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.12/virtualizedlist.html b/docs/0.12/virtualizedlist.html
index f0ecbd00f5d..80c9b5f6241 100644
--- a/docs/0.12/virtualizedlist.html
+++ b/docs/0.12/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.12
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.12
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.13/sectionlist.html b/docs/0.13/sectionlist.html
index c9d93cca50d..5f09c4c513e 100644
--- a/docs/0.13/sectionlist.html
+++ b/docs/0.13/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.13/virtualizedlist.html b/docs/0.13/virtualizedlist.html
index e07908a268b..2c856fa0cc2 100644
--- a/docs/0.13/virtualizedlist.html
+++ b/docs/0.13/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.13
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.13
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.14/sectionlist.html b/docs/0.14/sectionlist.html
index 49549ed8c6b..8b1a042156a 100644
--- a/docs/0.14/sectionlist.html
+++ b/docs/0.14/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.14/virtualizedlist.html b/docs/0.14/virtualizedlist.html
index ddf2eb7392f..c43ce5190b0 100644
--- a/docs/0.14/virtualizedlist.html
+++ b/docs/0.14/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.14
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.14
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.15/sectionlist.html b/docs/0.15/sectionlist.html
index f83eb6edb80..6d5987055ee 100644
--- a/docs/0.15/sectionlist.html
+++ b/docs/0.15/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.15/virtualizedlist.html b/docs/0.15/virtualizedlist.html
index 99e71018aad..ab8a4599e78 100644
--- a/docs/0.15/virtualizedlist.html
+++ b/docs/0.15/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.15
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.15
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.16/sectionlist.html b/docs/0.16/sectionlist.html
index 447e4f5f8bb..851dfa77f6a 100644
--- a/docs/0.16/sectionlist.html
+++ b/docs/0.16/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.16/virtualizedlist.html b/docs/0.16/virtualizedlist.html
index 912e442a908..8e90441a304 100644
--- a/docs/0.16/virtualizedlist.html
+++ b/docs/0.16/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.16
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.16
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.17/sectionlist.html b/docs/0.17/sectionlist.html
index c07190c16d4..c21425c6411 100644
--- a/docs/0.17/sectionlist.html
+++ b/docs/0.17/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.17/virtualizedlist.html b/docs/0.17/virtualizedlist.html
index fd81c104eb5..c8727ff793b 100644
--- a/docs/0.17/virtualizedlist.html
+++ b/docs/0.17/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.17
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.17
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.18/sectionlist.html b/docs/0.18/sectionlist.html
index c9063a2776a..592b4ad14a3 100644
--- a/docs/0.18/sectionlist.html
+++ b/docs/0.18/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.18/virtualizedlist.html b/docs/0.18/virtualizedlist.html
index e66f73c9318..064e8e1661a 100644
--- a/docs/0.18/virtualizedlist.html
+++ b/docs/0.18/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.18
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.18
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.19/sectionlist.html b/docs/0.19/sectionlist.html
index 8b6e4e254c9..8071b95b853 100644
--- a/docs/0.19/sectionlist.html
+++ b/docs/0.19/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.19/virtualizedlist.html b/docs/0.19/virtualizedlist.html
index bec48f465d2..ad51c0e37c3 100644
--- a/docs/0.19/virtualizedlist.html
+++ b/docs/0.19/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.19
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.19
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.20/sectionlist.html b/docs/0.20/sectionlist.html
index 48eb8730ad5..3fc1c4b001e 100644
--- a/docs/0.20/sectionlist.html
+++ b/docs/0.20/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.20/virtualizedlist.html b/docs/0.20/virtualizedlist.html
index d0d7a2c4966..7949a1f77ef 100644
--- a/docs/0.20/virtualizedlist.html
+++ b/docs/0.20/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.20
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.20
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.21/sectionlist.html b/docs/0.21/sectionlist.html
index eebe0ad3d6e..258d494b70d 100644
--- a/docs/0.21/sectionlist.html
+++ b/docs/0.21/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.21/virtualizedlist.html b/docs/0.21/virtualizedlist.html
index 102193a44b3..4c925b5a08e 100644
--- a/docs/0.21/virtualizedlist.html
+++ b/docs/0.21/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.21
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.21
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.22/sectionlist.html b/docs/0.22/sectionlist.html
index 711b4f5dfa6..bfadebad79d 100644
--- a/docs/0.22/sectionlist.html
+++ b/docs/0.22/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.22/virtualizedlist.html b/docs/0.22/virtualizedlist.html
index 7615161700d..8ac6bd3fba6 100644
--- a/docs/0.22/virtualizedlist.html
+++ b/docs/0.22/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.22
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.22
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.23/sectionlist.html b/docs/0.23/sectionlist.html
index 8a40d2eecd8..6ea3ce3fbab 100644
--- a/docs/0.23/sectionlist.html
+++ b/docs/0.23/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.23/virtualizedlist.html b/docs/0.23/virtualizedlist.html
index 83bb48834e9..1deb81bf5e7 100644
--- a/docs/0.23/virtualizedlist.html
+++ b/docs/0.23/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.23
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.23
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.24/sectionlist.html b/docs/0.24/sectionlist.html
index 4c4989982e7..7836831a2e5 100644
--- a/docs/0.24/sectionlist.html
+++ b/docs/0.24/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.24/virtualizedlist.html b/docs/0.24/virtualizedlist.html
index abd5569a838..04fabf6f145 100644
--- a/docs/0.24/virtualizedlist.html
+++ b/docs/0.24/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.24
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.24
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.25/sectionlist.html b/docs/0.25/sectionlist.html
index faecf38b91e..31596a62e70 100644
--- a/docs/0.25/sectionlist.html
+++ b/docs/0.25/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.25/virtualizedlist.html b/docs/0.25/virtualizedlist.html
index 6af4a6bb725..3c2015793e5 100644
--- a/docs/0.25/virtualizedlist.html
+++ b/docs/0.25/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.25
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.25
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.26/sectionlist.html b/docs/0.26/sectionlist.html
index af8dc7f3763..295f8705f4d 100644
--- a/docs/0.26/sectionlist.html
+++ b/docs/0.26/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.26/virtualizedlist.html b/docs/0.26/virtualizedlist.html
index bcbd6369fbd..a413036ed97 100644
--- a/docs/0.26/virtualizedlist.html
+++ b/docs/0.26/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.26
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.26
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.27/sectionlist.html b/docs/0.27/sectionlist.html
index 08f932f7cb2..d11ecdf7a6c 100644
--- a/docs/0.27/sectionlist.html
+++ b/docs/0.27/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.27/virtualizedlist.html b/docs/0.27/virtualizedlist.html
index 0b1dc46734a..fa488111700 100644
--- a/docs/0.27/virtualizedlist.html
+++ b/docs/0.27/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.27
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.27
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.28/sectionlist.html b/docs/0.28/sectionlist.html
index da48c37d6f4..e382032a2b3 100644
--- a/docs/0.28/sectionlist.html
+++ b/docs/0.28/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.28/virtualizedlist.html b/docs/0.28/virtualizedlist.html
index e4858e19a08..6c89249be05 100644
--- a/docs/0.28/virtualizedlist.html
+++ b/docs/0.28/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.28
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.28
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.29/modal.html b/docs/0.29/modal.html
index bd2edf15ba2..7656e788af7 100644
--- a/docs/0.29/modal.html
+++ b/docs/0.29/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.29/sectionlist.html b/docs/0.29/sectionlist.html
index 58d6191f7a3..1531189e9c7 100644
--- a/docs/0.29/sectionlist.html
+++ b/docs/0.29/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.29/text.html b/docs/0.29/text.html
index 5d1ba6c657a..a858a13321f 100644
--- a/docs/0.29/text.html
+++ b/docs/0.29/text.html
@@ -82,7 +82,7 @@ AppRegistry.registerComponent('TextInANest', ()
 
    When set to true, indicates that the view is an accessibility element. The default value
 for a Text element is true.
    
 
    See the
-Accessibility guide
+Accessibility guide
 for more information.
    
 
diff --git a/docs/0.29/textinput.html b/docs/0.29/textinput.html
index e749474e791..ca29c4a4175 100644
--- a/docs/0.29/textinput.html
+++ b/docs/0.29/textinput.html
@@ -449,7 +449,7 @@ like passwords stay secure. The default value is false.
    
 
 
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.29/virtualizedlist.html b/docs/0.29/virtualizedlist.html
index c6983428acd..182d583d882 100644
--- a/docs/0.29/virtualizedlist.html
+++ b/docs/0.29/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.29
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.29
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.30/modal.html b/docs/0.30/modal.html
index 20a6a48a2bd..3f3814c4e72 100644
--- a/docs/0.30/modal.html
+++ b/docs/0.30/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.30/sectionlist.html b/docs/0.30/sectionlist.html
index 3b7df0dd9f8..a07363fdc71 100644
--- a/docs/0.30/sectionlist.html
+++ b/docs/0.30/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.30/textinput.html b/docs/0.30/textinput.html
index 23ca7f1473d..2f85dd625c2 100644
--- a/docs/0.30/textinput.html
+++ b/docs/0.30/textinput.html
@@ -489,7 +489,7 @@ like passwords stay secure. The default value is false.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.30/virtualizedlist.html b/docs/0.30/virtualizedlist.html
index 4cb7efd1734..60e6a56e75e 100644
--- a/docs/0.30/virtualizedlist.html
+++ b/docs/0.30/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.30
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.30
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.31/modal.html b/docs/0.31/modal.html
index dac91c881c4..a49635f0103 100644
--- a/docs/0.31/modal.html
+++ b/docs/0.31/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.31/sectionlist.html b/docs/0.31/sectionlist.html
index 185e2ed695d..e1444d70f15 100644
--- a/docs/0.31/sectionlist.html
+++ b/docs/0.31/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.31/textinput.html b/docs/0.31/textinput.html
index c1265ced591..aac12560996 100644
--- a/docs/0.31/textinput.html
+++ b/docs/0.31/textinput.html
@@ -504,7 +504,7 @@ like passwords stay secure. The default value is false.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.31/virtualizedlist.html b/docs/0.31/virtualizedlist.html
index 9afcb20f0fc..0a8a705d1e6 100644
--- a/docs/0.31/virtualizedlist.html
+++ b/docs/0.31/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.31
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.31
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.32/modal.html b/docs/0.32/modal.html
index b47610127cd..c17871373a9 100644
--- a/docs/0.32/modal.html
+++ b/docs/0.32/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.32/navigatorios.html b/docs/0.32/navigatorios.html
index 72b1b06eaf1..9631c50a6e2 100644
--- a/docs/0.32/navigatorios.html
+++ b/docs/0.32/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
    
 
    As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
    
diff --git a/docs/0.32/sectionlist.html b/docs/0.32/sectionlist.html
index 4eaebd3593f..0639c9452ad 100644
--- a/docs/0.32/sectionlist.html
+++ b/docs/0.32/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.32/textinput.html b/docs/0.32/textinput.html
index 79471324fb4..797e93e7b0d 100644
--- a/docs/0.32/textinput.html
+++ b/docs/0.32/textinput.html
@@ -505,7 +505,7 @@ like passwords stay secure. The default value is false.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.32/virtualizedlist.html b/docs/0.32/virtualizedlist.html
index 6595d185b59..d095a0e103c 100644
--- a/docs/0.32/virtualizedlist.html
+++ b/docs/0.32/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.32
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.32
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.33/modal.html b/docs/0.33/modal.html
index fd1c54ce12e..615d2bbfce1 100644
--- a/docs/0.33/modal.html
+++ b/docs/0.33/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.33/navigatorios.html b/docs/0.33/navigatorios.html
index 4e164a14ceb..56becbe283f 100644
--- a/docs/0.33/navigatorios.html
+++ b/docs/0.33/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
    
 
    As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
    
diff --git a/docs/0.33/sectionlist.html b/docs/0.33/sectionlist.html
index e259c7be417..eb35a7c5826 100644
--- a/docs/0.33/sectionlist.html
+++ b/docs/0.33/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.33/textinput.html b/docs/0.33/textinput.html
index a8bf154d230..90bc0eacd50 100644
--- a/docs/0.33/textinput.html
+++ b/docs/0.33/textinput.html
@@ -505,7 +505,7 @@ like passwords stay secure. The default value is false.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.33/virtualizedlist.html b/docs/0.33/virtualizedlist.html
index f8fe7fb44e0..5064fefb0f2 100644
--- a/docs/0.33/virtualizedlist.html
+++ b/docs/0.33/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.33
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.33
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.34/modal.html b/docs/0.34/modal.html
index 61d9861a760..c54d577935f 100644
--- a/docs/0.34/modal.html
+++ b/docs/0.34/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.34/navigatorios.html b/docs/0.34/navigatorios.html
index 37eb8d03dbf..46c89089084 100644
--- a/docs/0.34/navigatorios.html
+++ b/docs/0.34/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
    
 
    As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
    
diff --git a/docs/0.34/sectionlist.html b/docs/0.34/sectionlist.html
index 6a3e6673a45..a0c1eae5d5f 100644
--- a/docs/0.34/sectionlist.html
+++ b/docs/0.34/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.34/textinput.html b/docs/0.34/textinput.html
index ddfe797111d..2f12dd0620e 100644
--- a/docs/0.34/textinput.html
+++ b/docs/0.34/textinput.html
@@ -521,7 +521,7 @@ end: PropTypes.number,
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.34/virtualizedlist.html b/docs/0.34/virtualizedlist.html
index 8c36b0602b2..ea2912c96e0 100644
--- a/docs/0.34/virtualizedlist.html
+++ b/docs/0.34/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.34
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.34
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.35/modal.html b/docs/0.35/modal.html
index 21a414993de..19fcc90e310 100644
--- a/docs/0.35/modal.html
+++ b/docs/0.35/modal.html
@@ -6,7 +6,7 @@
           };
         
    Edit
    Modal
    The Modal component is a simple way to present content above an enclosing view.
    
 
    Note: If you need more control over how to present modals over the rest of your app,
-then consider using a top-level Navigator. Go here to compare navigation options.
    
+then consider using a top-level Navigator. Go here to compare navigation options.
    
 
    import React, { Component } from 'react';
 import { Modal, Text, TouchableHighlight, View } from 'react-native';
 
diff --git a/docs/0.35/navigatorios.html b/docs/0.35/navigatorios.html
index b10717682a3..de4338470c0 100644
--- a/docs/0.35/navigatorios.html
+++ b/docs/0.35/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
    
 
    As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
    
diff --git a/docs/0.35/sectionlist.html b/docs/0.35/sectionlist.html
index 66423777998..f929f6cc1ee 100644
--- a/docs/0.35/sectionlist.html
+++ b/docs/0.35/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.35/textinput.html b/docs/0.35/textinput.html
index 137aa2b7622..c2f5ca739f9 100644
--- a/docs/0.35/textinput.html
+++ b/docs/0.35/textinput.html
@@ -521,7 +521,7 @@ end: PropTypes.number,
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.35/virtualizedlist.html b/docs/0.35/virtualizedlist.html
index f50c0c8351b..d19cbb22a46 100644
--- a/docs/0.35/virtualizedlist.html
+++ b/docs/0.35/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.35
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.35
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.36/navigatorios.html b/docs/0.36/navigatorios.html
index 071a5a98ea9..f4498547c9e 100644
--- a/docs/0.36/navigatorios.html
+++ b/docs/0.36/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.36/sectionlist.html b/docs/0.36/sectionlist.html
index ddc5a02b6a6..fb7c08329d0 100644
--- a/docs/0.36/sectionlist.html
+++ b/docs/0.36/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.36/textinput.html b/docs/0.36/textinput.html
index 7be06b657e6..3e10506994d 100644
--- a/docs/0.36/textinput.html
+++ b/docs/0.36/textinput.html
@@ -521,7 +521,7 @@ end: PropTypes.number,
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.36/virtualizedlist.html b/docs/0.36/virtualizedlist.html
index 1079a5e66ac..ca11602e498 100644
--- a/docs/0.36/virtualizedlist.html
+++ b/docs/0.36/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.36
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.36
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.37/navigatorios.html b/docs/0.37/navigatorios.html
index cbc23acce11..9bf100bd696 100644
--- a/docs/0.37/navigatorios.html
+++ b/docs/0.37/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.37/sectionlist.html b/docs/0.37/sectionlist.html
index 63dfd8bc7a4..ca23a3cbe2d 100644
--- a/docs/0.37/sectionlist.html
+++ b/docs/0.37/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.37/textinput.html b/docs/0.37/textinput.html
index eb6f1ef8149..629977a98e7 100644
--- a/docs/0.37/textinput.html
+++ b/docs/0.37/textinput.html
@@ -481,7 +481,7 @@ the same value to position the cursor.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.37/virtualizedlist.html b/docs/0.37/virtualizedlist.html
index f28435ff3fb..472bb76cb89 100644
--- a/docs/0.37/virtualizedlist.html
+++ b/docs/0.37/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.37
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.37
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.38/navigatorios.html b/docs/0.38/navigatorios.html
index dd98e60c031..97c2d71ae47 100644
--- a/docs/0.38/navigatorios.html
+++ b/docs/0.38/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.38/sectionlist.html b/docs/0.38/sectionlist.html
index aeb8cdd6170..3dfef36b673 100644
--- a/docs/0.38/sectionlist.html
+++ b/docs/0.38/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.38/textinput.html b/docs/0.38/textinput.html
index 62bcad6fe41..f6f93cdea8d 100644
--- a/docs/0.38/textinput.html
+++ b/docs/0.38/textinput.html
@@ -487,7 +487,7 @@ the same value to position the cursor.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.38/virtualizedlist.html b/docs/0.38/virtualizedlist.html
index 49770a23a30..68ffa5ed1ea 100644
--- a/docs/0.38/virtualizedlist.html
+++ b/docs/0.38/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.38
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.38
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.39/navigatorios.html b/docs/0.39/navigatorios.html
index 7055dfe24a3..1dddc974188 100644
--- a/docs/0.39/navigatorios.html
+++ b/docs/0.39/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.39/sectionlist.html b/docs/0.39/sectionlist.html
index 8728e151e4b..a31d93bbdc8 100644
--- a/docs/0.39/sectionlist.html
+++ b/docs/0.39/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.39/textinput.html b/docs/0.39/textinput.html
index 2089534cf73..76653d16a76 100644
--- a/docs/0.39/textinput.html
+++ b/docs/0.39/textinput.html
@@ -501,7 +501,7 @@ the same value to position the cursor.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.39/virtualizedlist.html b/docs/0.39/virtualizedlist.html
index 1e440fb7ff4..8b4ce1274b3 100644
--- a/docs/0.39/virtualizedlist.html
+++ b/docs/0.39/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.39
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.39
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.40/navigatorios.html b/docs/0.40/navigatorios.html
index 7b09a89ddd1..6b1baf5b490 100644
--- a/docs/0.40/navigatorios.html
+++ b/docs/0.40/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.40/sectionlist.html b/docs/0.40/sectionlist.html
index 7fe95c64757..3f20e58fc1f 100644
--- a/docs/0.40/sectionlist.html
+++ b/docs/0.40/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.40/textinput.html b/docs/0.40/textinput.html
index 83e6a310f1a..71d305d62e4 100644
--- a/docs/0.40/textinput.html
+++ b/docs/0.40/textinput.html
@@ -503,7 +503,7 @@ the same value to position the cursor.
    
 
    
 
 
    TypeRequired
    
 
    
 
    style
    
-
    Styles
    
+
    Styles
    
 
diff --git a/docs/0.40/virtualizedlist.html b/docs/0.40/virtualizedlist.html
index 440fa3d1bbb..bd6b8fff628 100644
--- a/docs/0.40/virtualizedlist.html
+++ b/docs/0.40/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.40
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.40
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.41/navigatorios.html b/docs/0.41/navigatorios.html
index e4406902bec..1f05654ab3a 100644
--- a/docs/0.41/navigatorios.html
+++ b/docs/0.41/navigatorios.html
@@ -10,7 +10,7 @@ enabling you to implement a navigation stack. It works exactly the same as it
 would on a native app using UINavigationController, providing the same
 animations and behavior from UIKIt.
      
 
      As the name implies, it is only available on iOS. Take a look at
-Navigator for a similar solution for your
+Navigator for a similar solution for your
 cross-platform needs, or check out
 react-native-navigation, a
 component that aims to provide native navigation on both iOS and Android.
      
diff --git a/docs/0.41/sectionlist.html b/docs/0.41/sectionlist.html
index 4e15e02dd75..3221984943a 100644
--- a/docs/0.41/sectionlist.html
+++ b/docs/0.41/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.41/textinput.html b/docs/0.41/textinput.html
index b6dbb62f0cc..379b960b479 100644
--- a/docs/0.41/textinput.html
+++ b/docs/0.41/textinput.html
@@ -507,7 +507,7 @@ the same value to position the cursor.
    
 
    Note that not all Text styles are supported,
 see Issue#7070
 for more detail.
    
-
    Styles
    
+
    Styles
    
 
    
 
 
    TypeRequired
    
diff --git a/docs/0.41/virtualizedlist.html b/docs/0.41/virtualizedlist.html
index 52177ef65d5..05b359a6cd2 100644
--- a/docs/0.41/virtualizedlist.html
+++ b/docs/0.41/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.41
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.41
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.42/sectionlist.html b/docs/0.42/sectionlist.html
index 13292ae0b25..4161b0b3d6b 100644
--- a/docs/0.42/sectionlist.html
+++ b/docs/0.42/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.42/virtualizedlist.html b/docs/0.42/virtualizedlist.html
index 8184a4008d4..0b876065647 100644
--- a/docs/0.42/virtualizedlist.html
+++ b/docs/0.42/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.42
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.42
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.43/scrollview.html b/docs/0.43/scrollview.html
index f7e4fa8a607..fc973c4ae41 100644
--- a/docs/0.43/scrollview.html
+++ b/docs/0.43/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
      
 
      Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
      
-
      <ScrollView> vs <FlatList> - which one to use?
      
+
      <ScrollView> vs <FlatList> - which one to use?
      
 
      ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
      
 
      On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.43/sectionlist.html b/docs/0.43/sectionlist.html
index 9afca9fa1d7..adece2d0837 100644
--- a/docs/0.43/sectionlist.html
+++ b/docs/0.43/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.43/virtualizedlist.html b/docs/0.43/virtualizedlist.html
index 9f14da9ca54..0f8e19797e7 100644
--- a/docs/0.43/virtualizedlist.html
+++ b/docs/0.43/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.43
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.43
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.44/scrollview.html b/docs/0.44/scrollview.html
index 33976dffb9d..7ab6465ade6 100644
--- a/docs/0.44/scrollview.html
+++ b/docs/0.44/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
      
 
      Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
      
-
      <ScrollView> vs <FlatList> - which one to use?
      
+
      <ScrollView> vs <FlatList> - which one to use?
      
 
      ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
      
 
      On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.44/sectionlist.html b/docs/0.44/sectionlist.html
index 9454c7cf940..534937729ae 100644
--- a/docs/0.44/sectionlist.html
+++ b/docs/0.44/sectionlist.html
@@ -18,7 +18,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    If you need sticky section header support, use ListView for now.
    
 
    Simple Examples:
    
 
    <SectionList
@@ -39,7 +39,7 @@
   ]}
 />
 
    
-
    This is a convenience wrapper around <VirtualizedList>,
+
    This is a convenience wrapper around <VirtualizedList>,
 and thus inherits the following caveats:
    
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item.title} />}
@@ -133,7 +133,7 @@ updateProps: (select: 'leading' | 'trailing', newProps: Object) => void,
 }) => ?React.Element | Yes |
    
 
    
 
    sections
    
-
    The actual data to render, akin to the data prop in <FlatList>.
    
+
    The actual data to render, akin to the data prop in <FlatList>.
    
 
    General shape:
    
 
    sections: $ReadOnlyArray<{
   data: $ReadOnlyArray<SectionItem>,
diff --git a/docs/0.45/virtualizedlist.html b/docs/0.45/virtualizedlist.html
index 7fef347ccc6..2676198f468 100644
--- a/docs/0.45/virtualizedlist.html
+++ b/docs/0.45/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    0.45
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/0.46/scrollview.html b/docs/0.46/scrollview.html
index 8aeeed63fe7..ad52d0b40a2 100644
--- a/docs/0.46/scrollview.html
+++ b/docs/0.46/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
    
-
    <ScrollView> vs <FlatList> - which one to use?
    
+
    <ScrollView> vs <FlatList> - which one to use?
    
 
    ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
    
 
    On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.46/sectionlist.html b/docs/0.46/sectionlist.html
index 6c2e62a3720..3ecdb90de92 100644
--- a/docs/0.46/sectionlist.html
+++ b/docs/0.46/sectionlist.html
@@ -18,7 +18,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item.title} />}
@@ -134,7 +134,7 @@ updateProps: (select: 'leading' | 'trailing', newProps: Object) => void,
 }) => ?React.Element | Yes |
    
 
    
 
    sections
    
-
    The actual data to render, akin to the data prop in <FlatList>.
    
+
    The actual data to render, akin to the data prop in <FlatList>.
    
 
    General shape:
    
 
    sections: $ReadOnlyArray<{
   data: $ReadOnlyArray<SectionItem>,
diff --git a/docs/0.46/virtualizedlist.html b/docs/0.46/virtualizedlist.html
index dfb65d65f4f..6265b2228a8 100644
--- a/docs/0.46/virtualizedlist.html
+++ b/docs/0.46/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    0.46
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/0.47/scrollview.html b/docs/0.47/scrollview.html
index 99dacfe6224..6095d221c61 100644
--- a/docs/0.47/scrollview.html
+++ b/docs/0.47/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
    
-
    <ScrollView> vs <FlatList> - which one to use?
    
+
    <ScrollView> vs <FlatList> - which one to use?
    
 
    ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
    
 
    On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.47/sectionlist.html b/docs/0.47/sectionlist.html
index 7abf6e2b263..d4e38d24e2d 100644
--- a/docs/0.47/sectionlist.html
+++ b/docs/0.47/sectionlist.html
@@ -18,7 +18,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item.title} />}
@@ -135,7 +135,7 @@ updateProps: (select: 'leading' | 'trailing', newProps: Object) => void,
 }) => ?React.Element | Yes |
    
 
    
 
    sections
    
-
    The actual data to render, akin to the data prop in <FlatList>.
    
+
    The actual data to render, akin to the data prop in <FlatList>.
    
 
    General shape:
    
 
    sections: $ReadOnlyArray<{
   data: $ReadOnlyArray<SectionItem>,
diff --git a/docs/0.47/virtualizedlist.html b/docs/0.47/virtualizedlist.html
index 6560beb7959..2b1c7071394 100644
--- a/docs/0.47/virtualizedlist.html
+++ b/docs/0.47/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    0.47
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/0.48/scrollview.html b/docs/0.48/scrollview.html
index 264bdd505a7..90650cba328 100644
--- a/docs/0.48/scrollview.html
+++ b/docs/0.48/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
    
-
    <ScrollView> vs <FlatList> - which one to use?
    
+
    <ScrollView> vs <FlatList> - which one to use?
    
 
    ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
    
 
    On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.48/sectionlist.html b/docs/0.48/sectionlist.html
index 5ba71a93f49..b0420360870 100644
--- a/docs/0.48/sectionlist.html
+++ b/docs/0.48/sectionlist.html
@@ -18,7 +18,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
@@ -136,7 +136,7 @@ updateProps: (select: 'leading' | 'trailing', newProps: Object) => void,
 }) => ?React.Element | Yes |
    
 
    
 
    sections
    
-
    The actual data to render, akin to the data prop in <FlatList>.
    
+
    The actual data to render, akin to the data prop in <FlatList>.
    
 
    General shape:
    
 
    sections: $ReadOnlyArray<{
   data: $ReadOnlyArray<SectionItem>,
diff --git a/docs/0.48/virtualizedlist.html b/docs/0.48/virtualizedlist.html
index 8480ed01eb9..f03fd6ccad5 100644
--- a/docs/0.48/virtualizedlist.html
+++ b/docs/0.48/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    0.48
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/0.49/scrollview.html b/docs/0.49/scrollview.html
index 1abcfe57deb..e97252c1bfb 100644
--- a/docs/0.49/scrollview.html
+++ b/docs/0.49/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
    
-
    <ScrollView> vs <FlatList> - which one to use?
    
+
    <ScrollView> vs <FlatList> - which one to use?
    
 
    ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
    
 
    On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.49/sectionlist.html b/docs/0.49/sectionlist.html
index 2018eaa5d7a..052e5745f22 100644
--- a/docs/0.49/sectionlist.html
+++ b/docs/0.49/sectionlist.html
@@ -18,7 +18,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.49/virtualizedlist.html b/docs/0.49/virtualizedlist.html
index d0d6df07d6d..3cee0f79602 100644
--- a/docs/0.49/virtualizedlist.html
+++ b/docs/0.49/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    0.49
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/0.5/sectionlist.html b/docs/0.5/sectionlist.html
index c580ed4bfad..58d192b0be7 100644
--- a/docs/0.5/sectionlist.html
+++ b/docs/0.5/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.5/virtualizedlist.html b/docs/0.5/virtualizedlist.html
index 4a0b4da3bbc..acaf7d4c605 100644
--- a/docs/0.5/virtualizedlist.html
+++ b/docs/0.5/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.5
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.5
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.50/scrollview.html b/docs/0.50/scrollview.html
index d316fe1a67c..6dadb1083bb 100644
--- a/docs/0.50/scrollview.html
+++ b/docs/0.50/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
      
 
      Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
      
-
      <ScrollView> vs <FlatList> - which one to use?
      
+
      <ScrollView> vs <FlatList> - which one to use?
      
 
      ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
      
 
      On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/0.50/sectionlist.html b/docs/0.50/sectionlist.html
index e1c1c915783..067193befde 100644
--- a/docs/0.50/sectionlist.html
+++ b/docs/0.50/sectionlist.html
@@ -18,7 +18,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.6/sectionlist.html b/docs/0.6/sectionlist.html
index a4794cd2a74..c276f76f546 100644
--- a/docs/0.6/sectionlist.html
+++ b/docs/0.6/sectionlist.html
@@ -12,7 +12,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.6/virtualizedlist.html b/docs/0.6/virtualizedlist.html
index 88eee31ec9b..6a7a0fc352d 100644
--- a/docs/0.6/virtualizedlist.html
+++ b/docs/0.6/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.6
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.6
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.7/sectionlist.html b/docs/0.7/sectionlist.html
index 5b4e66551a8..03b5942ba93 100644
--- a/docs/0.7/sectionlist.html
+++ b/docs/0.7/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.7/virtualizedlist.html b/docs/0.7/virtualizedlist.html
index 6119631fdc4..38b0a36c16a 100644
--- a/docs/0.7/virtualizedlist.html
+++ b/docs/0.7/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.7
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.7
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.8/sectionlist.html b/docs/0.8/sectionlist.html
index ea33b7c83f0..0b0ed76c98a 100644
--- a/docs/0.8/sectionlist.html
+++ b/docs/0.8/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.8/virtualizedlist.html b/docs/0.8/virtualizedlist.html
index 5fa1a6b6ae4..1064a6df530 100644
--- a/docs/0.8/virtualizedlist.html
+++ b/docs/0.8/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.8
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.8
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/0.9/sectionlist.html b/docs/0.9/sectionlist.html
index 21e31d98d42..15b645c066b 100644
--- a/docs/0.9/sectionlist.html
+++ b/docs/0.9/sectionlist.html
@@ -12,7 +12,7 @@
 
    • Scroll loading.
      • 
 
    
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}
diff --git a/docs/0.9/virtualizedlist.html b/docs/0.9/virtualizedlist.html
index 7bf3fb5258b..6255af95848 100644
--- a/docs/0.9/virtualizedlist.html
+++ b/docs/0.9/virtualizedlist.html
@@ -1,4 +1,4 @@
-VirtualizedList · React Native
    React Native
    0.9
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
+VirtualizedList · React Native
    React Native
    0.9
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList> and <SectionList> components, which are also better documented. In general, this should only really be used if you need more flexibility than FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by maintaining a finite render window of active items and replacing all items outside of the render window with appropriately sized blank space. The window adapts to scrolling behavior, and items are rendered incrementally with low-pri (after any running interactions) if they are far from the visible area, or with hi-pri otherwise to minimize the potential of seeing blank space.
    
 
    Some caveats:
    
 
      
diff --git a/docs/next/contributing.html b/docs/next/contributing.html
index 8b531ffbeae..69ffc6d032e 100644
--- a/docs/next/contributing.html
+++ b/docs/next/contributing.html
@@ -65,11 +65,11 @@
 
        
 
      1. Fork the repository and create your branch from master.
        2. 
 
      2. Add the copyright notice to the top of any new files you've added.
        3. 
-
      3. Describe your test plan in your pull request description. Make sure to test your changes!
        4. 
+
      4. Describe your test plan in your pull request description. Make sure to test your changes!
        5. 
 
      5. Make sure your code lints (npm run lint).
        6. 
 
      6. If you haven't already, sign the CLA.
        7. 
 
      
-
      All pull requests should be opened against the master branch. After opening your pull request, ensure all tests pass on Circle CI. If a test fails and you believe it is unrelated to your change, leave a comment on the pull request explaining why.
      
+
      All pull requests should be opened against the master branch. After opening your pull request, ensure all tests pass on Circle CI. If a test fails and you believe it is unrelated to your change, leave a comment on the pull request explaining why.
      
 
      
 
      Note: It is not necessary to keep clicking Merge master to your branch on the PR page. You would want to merge master if there are conflicts or tests are failing. The Facebook-GitHub-Bot ultimately squashes all commits to a single one before merging your PR.
      
 
      
@@ -82,7 +82,7 @@
 
    
 
    See What is a Test Plan? to learn more.
    
 
    Continuous integration tests
    
-
    Make sure all tests pass on Circle CI. PRs that break tests are unlikely to be merged. Learn more about testing your changes here.
    
+
    Make sure all tests pass on Circle CI. PRs that break tests are unlikely to be merged. Learn more about testing your changes here.
    
 
    Breaking changes
    
 
    When adding a new breaking change, follow this template in your pull request:
    
 
    ### New breaking change here
@@ -108,7 +108,7 @@
 
    Contributor License Agreement (CLA)
    
 
    In order to accept your pull request, we need you to submit a CLA. You only need to do this once, so if you've done this for another Facebook open source project, you're good to go. If you are submitting a pull request for the first time, the Facebook GitHub Bot will reply with a link to the CLA form. You may also complete your CLA here.
    
 
    What happens next?
    
-
    The core team will be monitoring for pull requests. Read what to expect from maintainers to understand what may happen after you open a pull request.
    
+
    The core team will be monitoring for pull requests. Read what to expect from maintainers to understand what may happen after you open a pull request.
    
 
    Style Guide
    
 
    Our linter will catch most styling issues that may exist in your code. You can check the status of your code styling by simply running npm run lint.
    
 
    However, there are still some styles that the linter cannot pick up.
    
diff --git a/docs/next/more-resources.html b/docs/next/more-resources.html
index adf980d9a4d..a95b9883e93 100644
--- a/docs/next/more-resources.html
+++ b/docs/next/more-resources.html
@@ -28,14 +28,13 @@ Native is capable of! There are also some
 example apps on GitHub.
 You can run the apps on a simulator or device, and you can see the source code
 for these apps, which is neat.
    
-
    The folks who built the app for Facebook's F8 conference in 2016 also
+
    The folks who built the app for Facebook's F8 conference also
 open-sourced the code and wrote up a
-detailed series of tutorials.
+detailed series of tutorials.
 This is useful if you want a more in-depth example that's more realistic than
 most sample apps out there.
    
 
    Extending React Native
    
 
      
-
    • Looking for a component? JS.coach
      • 
 
    • Fellow developers write and publish React Native modules to npm and open
 source them on GitHub.
      • 
 
    • Making modules helps grow the React Native ecosystem and community. We
@@ -47,6 +46,7 @@ and Native UI Components
 (iOS,
 Android)
 if you are interested in extending native functionality.
      • 
+
    • Looking for a pre-built component? Check JS.coach.
      • 
 
    
 
    Development Tools
    
 
    Nuclide is the IDE that Facebook uses internally for
diff --git a/docs/next/virtualizedlist.html b/docs/next/virtualizedlist.html
index 391ccd8ac7f..c1a450958e5 100644
--- a/docs/next/virtualizedlist.html
+++ b/docs/next/virtualizedlist.html
@@ -1,11 +1,11 @@
-VirtualizedList · React Native
    React Native
    next
    Edit
    VirtualizedList
    Base implementation for the more convenient <FlatList>
+and <SectionList> components, which are also better
 documented. In general, this should only really be used if you need more flexibility than
 FlatList provides, e.g. for use with immutable data instead of plain arrays.
    
 
    Virtualization massively improves memory consumption and performance of large lists by
diff --git a/docs/scrollview.html b/docs/scrollview.html
index ee72d8549f7..84cdf3b2c3e 100644
--- a/docs/scrollview.html
+++ b/docs/scrollview.html
@@ -15,7 +15,7 @@ view stack can lead to errors here, which the element inspector makes
 easy to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll
 view from becoming the responder.
    
-
    <ScrollView> vs <FlatList> - which one to use?
    
+
    <ScrollView> vs <FlatList> - which one to use?
    
 
    ScrollView simply renders all its react child components at once. That
 makes it very easy to understand and use.
    
 
    On the other hand, this has a performance downside. Imagine you have a very
diff --git a/docs/sectionlist.html b/docs/sectionlist.html
index 9727b92f683..4999210497d 100644
--- a/docs/sectionlist.html
+++ b/docs/sectionlist.html
@@ -18,7 +18,7 @@
 
  • Scroll loading.
    • 
 
 
    If you don't need section support and want a simpler interface, use
-<FlatList>.
    
+<FlatList>.
    
 
    Simple Examples:
    
 
    <SectionList
   renderItem={({item}) => <ListItem title={item} />}

    
 
 
    TypeRequired