README.md in timber-1.1.9 vs README.md in timber-1.1.10

@@ -82,16 +82,10 @@
 ---
 
 </p></details>
 
 
-
-
-
-
-
-
 ## Send your logs (choose one)
 
 <details><summary><strong>Heroku (log drains)</strong></summary><p>
 
 The recommended strategy for Heroku is to setup a
@@ -101,30 +95,30 @@
 
 ---
 
 </p></details>
 
-<details><summary><strong>All other platforms (Network / HTTP)</strong></summary><p>
+<details><summary><strong>Or, all other platforms (Network / HTTP)</strong></summary><p>
 
 1. *Specify* the Timber Network logger backend in `config/environments/production.rb`:
 
   Replace any existing `config.logger =` calls with:
 
   ```ruby
   # config/environments/production.rb (or staging, etc)
 
   network_log_device = Timber::LogDevices::Network.new(ENV['TIMBER_LOGS_KEY'])
-  config.logger = Timber::Logger.new(network_log_device) # <-- Use network_log_device instead of STDOUT
+  config.logger = ActiveSupport::TaggedLogging.new(Timber::Logger.new(network_log_device))
   ```
 
 2. Obtain your Timber API :key: by **[adding your app in Timber](https://app.timber.io)**.
 
 3. Assign your API key to the `TIMBER_LOGS_KEY` environment variable.
 
 </p></details>
 
-<details><summary><strong>Advanced setup (syslog, file tailing agent, etc)</strong></summary><p>
+<details><summary><strong>Or, advanced setup (syslog, file tailing agent, etc)</strong></summary><p>
 
 Checkout our [docs](https://timber.io/docs) for a comprehensive list of install instructions.
 
 </p></details>
 
@@ -182,13 +176,12 @@
 
 ---
 
 </p></details>
 
-<details><summary><strong>Timings</strong></summary><p>
+<details><summary><strong>Timing events</strong></summary><p>
 
-Timings allow you to easily capture one-off timings in your code; a simple
-way to benchmark code execution:
+Timings provid a simple way to time code execution:
 
 ```ruby
 start = Time.now
 # ...my code to time...
 time_ms = (Time.now - start) * 1000
\ No newline at end of file