Reorder

README.md

@@ -306,6 +306,18 @@ value.
 
 ## Jibber-Jabber
 
+<details><summary><strong>What specifically does the Timber library do?</strong></summary><p>
+
+1. Captures and structures your framework and 3rd party logs. (see next question)
+2. Adds useful context to every log line. (see next question)
+3. Allows you to easily add tags and timings to log. (see [Usage](#usage))
+4. Provides a framework for logging custom structured events. (see [Usage](#usage))
+5. Offers transport strategies to [send your logs](#send-your-logs) to the Timber service.
+
+---
+
+</p></details>
+
 <details><summary><strong>What are the benefits of using Timber?</strong></summary><p>
 
 1. **Data quality.** The usefulness of your logs starts here. This is why we ship libraries that
@@ -333,18 +345,6 @@ value.
 
 </p></details>
 
-<details><summary><strong>What specifically does the Timber library do?</strong></summary><p>
-
-1. Captures and structures your framework and 3rd party logs. (see next question)
-2. Adds useful context to every log line. (see next question)
-3. Allows you to easily add tags and timings to log. (see [Usage](#usage))
-4. Provides a framework for logging custom structured events. (see [Usage](#usage))
-5. Offers transport strategies to [send your logs](#send-your-logs) to the Timber service.
-
----
-
-</p></details>
-
 <details><summary><strong>What events does Timber capture & structure for me?</strong></summary><p>
 
 Out of the box you get everything in the [`Timber::Events`](lib/timber/events) namespace: