README.md in timber-1.0.7 vs README.md in timber-1.0.8

@@ -56,36 +56,29 @@
     }
   }
 }
 ```
 
-Notice we include data that isn't in the log message directly. It does the same for
-`http requests`, `sql queries`, `exceptions`, `template renderings`, and any other event
-your framework logs.
+It does the same for `http requests`, `sql queries`, `exceptions`, `template renderings`,
+and any other event your framework logs.
 
 (for a full list see [`Timber::Events`](lib/timber/events))
 
 
 ## Why Timber?
 
 Glad you asked! :)
 
-1. It's application aware and enriches your logs with data you can't get otherwise. This
-   entire process is fully managed for you.
+1. It's application aware and enriches your logs with data you can't get otherwise.
 2. It defines a shared schema across all of our libraries. Meaning your log data, across all
-   applications, will be normalized.
+   applications, is normalized.
 3. It does not alter the original log message, giving you the best of both worlds: human
    readable logs *and* rich structured events.
-4. It's completely transparent with absolutely no vendor lock-in or risk of code debt. Timber
-   adheres exactly to the `Logger` API. Meaning Timber can be installed and removed without
-   any reprocusion.
+4. It's completely transparent with absolutely no vendor lock-in or risk of code debt. It
+   does not introduce a special API, it's just good ol' loggin'.
 
-What really makes Timber unique is that at the end of the day it's just good ol' loggin'.
-No special API, no proprietary data format, the data is accessible and owned by you.
-[Woo!](http://i.giphy.com/7JYWGKgwxga5i.gif)
 
-
 ## Logging Custom Events
 
 > Another service? More lock-in? :*(
 
 Nope! Logging custom events is Just Logging™. Check it out:
@@ -111,12 +104,10 @@
 No mention of Timber anywhere!
 
 
 ## The Timber Console / Pricing
 
-Like my mother always said:
-
 > What good is structured log data if you can't search and visualize it?
 
 Enter [the Timber Console](https://timber.io). It's a modern, fast, and beautiful console for
 searching and visualizing your logs.
 
@@ -180,16 +171,10 @@
 
 ```ruby
 config.logger = ActiveSupport::TaggedLogging.new(Timber::Logger.new(STDOUT))
 ```
 
-**Warning**: Tags lack meaningful descriptions, they are a poor mans context. Not to worry though!
-Timber provides a simple system for adding custom context that you can optionally use. Checkout
-[the `Timber::CurrentContext` docs](lib/timber/current_context.rb) for examples.
-
 ---
-
-I leave you with one final thought:
 
 <p align="center" style="background: #140f2a;">
 <a href="http://github.com/timberio/timber-ruby"><img src="http://files.timber.io/images/ruby-library-readme-log-truth.png" height="947" /></a>
 </p>