README.md in keen-0.9.10 vs README.md in keen-1.0.0

@@ -68,12 +68,10 @@
 
 Publishing events shouldn't slow your application down or make users wait longer for page loads & server requests.
 
 The Keen IO API is fast, but any synchronous network call you make will negatively impact response times. For this reason, we recommend you use the `publish_async` method to send events when latency is a concern. Alternatively, you can drop events into a background queue e.g. Delayed Jobs and publish synchronously from there.
 
-To compare asychronous vs. synchronous performance, check out the [keen-gem-example](http://keen-gem-example.herokuapp.com/) app.
-
 To publish asynchronously, first add
 [em-http-request](https://github.com/igrigorik/em-http-request) to your Gemfile. Make sure it's version 1.0 or above.
 
 ```ruby
 gem "em-http-request", "~> 1.0"
@@ -416,9 +414,13 @@
 It's not just us humans that browse the web. Spiders, crawlers, and bots share the pipes too. When it comes to analytics, this can cause a mild headache. Events generated by bots can inflate your metrics and eat up your event quota.
 
 If you want some bot protection, check out the [Voight-Kampff](https://github.com/biola/Voight-Kampff) gem. Use the gem's `request.bot?` method to detect bots and avoid logging events.
 
 ### Changelog
+
+##### 1.0.0
++ Remove support for ruby 1.9.3
++ Update a few dependencies
 
 ##### 0.9.10
 + Add ability to set the `open_time` setting for the http client.
 
 ##### 0.9.9