diff --git a/docs/contributing.md b/docs/contributing.md
index 75783ae2912..3ef1a131d46 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -96,11 +96,11 @@ Small pull requests are much easier to review and more likely to get merged. Mak
 
 Please make sure the following is done when submitting a pull request:
 
-1.  Fork [the repository](https://github.com/facebook/react-native) and create your branch from `master`.
-2.  Add the copyright notice to the top of any new files you've added.
-3.  Describe your [**test plan**](contributing.html#test-plan) in your pull request description. Make sure to [test your changes](testing.html)!
-4.  Make sure your code lints (`npm run lint`).
-5.  If you haven't already, [sign the CLA](https://code.facebook.com/cla).
+1. Fork [the repository](https://github.com/facebook/react-native) and create your branch from `master`.
+2. Add the copyright notice to the top of any new files you've added.
+3. Describe your [**test plan**](contributing.html#test-plan) in your pull request description. Make sure to [test your changes](testing.html)!
+4. Make sure your code lints (`npm run lint`).
+5. If you haven't already, [sign the CLA](https://code.facebook.com/cla).
 
 All pull requests should be opened against the `master` branch. After opening your pull request, ensure [**all tests pass**](contributing.html#contrinuous-integration-tests) 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.
 
diff --git a/docs/performance.md b/docs/performance.md
index b6a43ab74d6..bfacb97f6c3 100644
--- a/docs/performance.md
+++ b/docs/performance.md
@@ -103,7 +103,7 @@ handleOnPress() {
 
 As mentioned above, `Navigator` animations are controlled by the JavaScript thread. Imagine the "push from right" scene transition: each frame, the new scene is moved from the right to left, starting offscreen (let's say at an x-offset of 320) and ultimately settling when the scene sits at an x-offset of
 
-0.  Each frame during this transition, the JavaScript thread needs to send a new x-offset to the main thread. If the JavaScript thread is locked up, it cannot do this and so no update occurs on that frame and the animation stutters.
+0. Each frame during this transition, the JavaScript thread needs to send a new x-offset to the main thread. If the JavaScript thread is locked up, it cannot do this and so no update occurs on that frame and the animation stutters.
 
 One solution to this is to allow for JavaScript-based animations to be offloaded to the main thread. If we were to do the same thing as in the above example with this approach, we might calculate a list of all x-offsets for the new scene when we are starting the transition and send them to the main thread to execute in an optimized way. Now that the JavaScript thread is freed of this responsibility, it's not a big deal if it drops a few frames while rendering the scene -- you probably won't even notice because you will be too distracted by the pretty transition.
 
@@ -225,8 +225,8 @@ This doesn't seem right. Why is it being called so often? Are they actually diff
 
 If you identified a native UI problem, there are usually two scenarios:
 
-1.  the UI you're trying to draw each frame involves too much work on the GPU, or
-2.  You're constructing new UI during the animation/interaction (e.g. loading in new content during a scroll).
+1. the UI you're trying to draw each frame involves too much work on the GPU, or
+2. You're constructing new UI during the animation/interaction (e.g. loading in new content during a scroll).
 
 ##### Too much GPU work
 
diff --git a/docs/running-on-device.md b/docs/running-on-device.md
index a34756401cb..43d27feb3d3 100644
--- a/docs/running-on-device.md
+++ b/docs/running-on-device.md
@@ -316,13 +316,13 @@ Open a terminal and type `/sbin/ifconfig` to find your machine's IP address.
 
 <block class="mac windows linux android" />
 
-1.  Make sure your laptop and your phone are on the **same** Wi-Fi network.
-2.  Open your React Native app on your device.
-3.  You'll see a [red screen with an error](debugging.md#in-app-errors-and-warnings). This is OK. The following steps will fix that.
-4.  Open the in-app [Developer menu](debugging.md#accessing-the-in-app-developer-menu).
-5.  Go to **Dev Settings** → **Debug server host & port for device**.
-6.  Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
-7.  Go back to the **Developer menu** and select **Reload JS**.
+1. Make sure your laptop and your phone are on the **same** Wi-Fi network.
+2. Open your React Native app on your device.
+3. You'll see a [red screen with an error](debugging.md#in-app-errors-and-warnings). This is OK. The following steps will fix that.
+4. Open the in-app [Developer menu](debugging.md#accessing-the-in-app-developer-menu).
+5. Go to **Dev Settings** → **Debug server host & port for device**.
+6. Type in your machine's IP address and the port of the local dev server (e.g. 10.0.1.1:8081).
+7. Go back to the **Developer menu** and select **Reload JS**.
 
 You can now enable Live reloading from the [Developer menu](debugging.md#accessing-the-in-app-developer-menu). Your app will reload whenever your JavaScript code has changed.
 
diff --git a/docs/sectionlist.md b/docs/sectionlist.md
index 19c133120f8..452115b0352 100644
--- a/docs/sectionlist.md
+++ b/docs/sectionlist.md
@@ -21,16 +21,19 @@ If you don't need section support and want a simpler interface, use [`<FlatList>
 Simple Examples:
 
 ```javascript
-// Example 1 (Homogeneous Rendering) 
- <SectionList 
-  renderItem={({ item, index, section }) => <Text key={index}>{item}</Text>} 
-  renderSectionHeader={({ section: { title } }) => <Text style={{ fontWeight: 'bold' }}>{title}</Text>} 
-  sections={[ 
-   { title: 'Title1', data: ['item1', 'item2'] }, 
-   { title: 'Title2', data: ['item3', 'item4'] }, 
-   { title: 'Title3', data: ['item5', 'item6'] }, 
-   ]} 
-  keyExtractor={(item, index) => item + index} />
+// Example 1 (Homogeneous Rendering)
+<SectionList
+  renderItem={({item, index, section}) => <Text key={index}>{item}</Text>}
+  renderSectionHeader={({section: {title}}) => (
+    <Text style={{fontWeight: 'bold'}}>{title}</Text>
+  )}
+  sections={[
+    {title: 'Title1', data: ['item1', 'item2']},
+    {title: 'Title2', data: ['item3', 'item4']},
+    {title: 'Title3', data: ['item5', 'item6']},
+  ]}
+  keyExtractor={(item, index) => item + index}
+/>
 ```
 
 ```javascript
diff --git a/docs/textinput.md b/docs/textinput.md
index 4560e425e09..ac29cb9e39f 100644
--- a/docs/textinput.md
+++ b/docs/textinput.md
@@ -697,8 +697,8 @@ Possible values for `textContentType` are:
 * `username`
 * `password`
 
-| Type                                                                                                                                                     | Required | Platform |
-| -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
+| Type                                                                                                                                                                                                                                                                                                                                                                                                       | Required | Platform |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- |
 | enum('none', 'URL', 'addressCity', 'addressCityAndState', 'addressState', 'countryName', 'creditCardNumber', 'emailAddress', 'familyName', 'fullStreetAddress', 'givenName', 'jobTitle', 'location', 'middleName', 'name', 'namePrefix', 'nameSuffix', 'nickname', 'organizationName', 'postalCode', 'streetAddressLine1', 'streetAddressLine2', 'sublocality', 'telephoneNumber', 'username', 'password') | No       | iOS      |
 
 ---
diff --git a/website/versioned_docs/version-0.55/sectionlist.md b/website/versioned_docs/version-0.55/sectionlist.md
index e7da558ce1b..30af827baf0 100644
--- a/website/versioned_docs/version-0.55/sectionlist.md
+++ b/website/versioned_docs/version-0.55/sectionlist.md
@@ -19,19 +19,22 @@ A performant interface for rendering sectioned lists, supporting the most handy
 
 If you don't need section support and want a simpler interface, use [`<FlatList>`](flatlist.md).
 
-Simple Examples: 
+Simple Examples:
 
 ```javascript
-// Example 1 (Homogeneous Rendering) 
- <SectionList 
-  renderItem={({ item, index, section }) => <Text key={index}>{item}</Text>} 
-  renderSectionHeader={({ section: { title } }) => <Text style={{ fontWeight: 'bold' }}>{title}</Text>} 
-  sections={[ 
-   { title: 'Title1', data: ['item1', 'item2'] }, 
-   { title: 'Title2', data: ['item3', 'item4'] }, 
-   { title: 'Title3', data: ['item5', 'item6'] }, 
-   ]} 
-  keyExtractor={(item, index) => item + index} />
+// Example 1 (Homogeneous Rendering)
+<SectionList
+  renderItem={({item, index, section}) => <Text key={index}>{item}</Text>}
+  renderSectionHeader={({section: {title}}) => (
+    <Text style={{fontWeight: 'bold'}}>{title}</Text>
+  )}
+  sections={[
+    {title: 'Title1', data: ['item1', 'item2']},
+    {title: 'Title2', data: ['item3', 'item4']},
+    {title: 'Title3', data: ['item5', 'item6']},
+  ]}
+  keyExtractor={(item, index) => item + index}
+/>
 ```
 
 ```javascript