README.md in timber-1.1.1 vs README.md in timber-1.1.2

@@ -130,11 +130,14 @@
 
 </p></details>
 
 <details><summary><strong>Tagging logs</strong></summary><p>
 
-Need a quick way to identify logs? Use tags!:
+Tags provide a quick way to identify logs. They work just like any tagging system.
+In the context of logging, they prevent obstructing the log message to
+accomplish the same thing, while also being a step down from creating a classified custom
+event. If the event is meaningful in any way, we recommend creating a custom event.
 
 ```ruby
 logger.info(message: "My log message", tag: "tag")
 
 # My log message @metadata {"level": "info", "tags": ["tag"], "context": {...}}
@@ -162,11 +165,11 @@
 
 ---
 
 </p></details>
 
-<details><summary><strong>Timings, Durations, & Metrics</strong></summary><p>
+<details><summary><strong>Timings</strong></summary><p>
 
 Timings allow you to easily capture one-off timings in your code; a simple
 way to benchmark code execution:
 
 ```ruby
@@ -295,19 +298,20 @@
 
 ## Setup
 
 <details><summary><strong>Rails (all versions, including edge)</strong></summary><p>
 
+👉 **Prefer examples?** Checkout our the [Timber install example pull request](https://github.com/timberio/ruby-rails-example-app/pulls/1)
+
+---
+
 *Replace* any existing `config.logger=` calls in `config/environments/production.rb` with:
 
 ```ruby
 # config/environments/production.rb
 
 config.logger = ActiveSupport::TaggedLogging.new(Timber::Logger.new(STDOUT))
 ```
-
-* Prefer examples? Checkout our [Ruby / Rails example app](https://github.com/timberio/ruby-rails-example-app),
-  you can see all changes by [search for "timber-change"](https://github.com/timberio/ruby-rails-example-app/search?utf8=%E2%9C%93&q=timber-change&type=Code).
 
 ---
 
 </p></details>
 
\ No newline at end of file