README.md in rufus-scheduler-3.0.9 vs README.md in rufus-scheduler-3.1.0

@@ -59,10 +59,11 @@
 
 ## related and similar gems
 
 * [whenever](https://github.com/javan/whenever) - let cron call back your Ruby code, trusted and reliable cron drives your schedule
 * [clockwork](https://github.com/tomykaira/clockwork) - rufus-scheduler inspired gem
+* [crono](https://github.com/plashchynski/crono) - an in-Rails cron scheduler
 
 (please note: rufus-scheduler is not a cron replacement)
 
 
 ## note about the 3.0 line
@@ -70,10 +71,15 @@
 It's a complete rewrite of rufus-scheduler.
 
 There is no EventMachine-based scheduler anymore.
 
 
+## I don't know what this Ruby thing is, where are my Rails?
+
+Sir, I'll drive you right to the [tracks](#so-rails).
+
+
 ## Notables changes:
 
 * As said, no more EventMachine-based scheduler
 * ```scheduler.every('100') {``` will schedule every 100 seconds (previously, it would have been 0.1s). This aligns rufus-scheduler on Ruby's ```sleep(100)```
 * The scheduler isn't catching the whole of Exception anymore, only StandardError
@@ -1367,22 +1373,9 @@
 # or even
 
 Rufus::Scheduler.parse("2013-12-12 14:00 Pacific/Saipan")
   # => 2013-12-12 04:00:00 UTC
 ```
-
-Behind the scenes, rufus-scheduler uses [tzinfo](http://tzinfo.github.io/) to deal with timezones.
-
-Here is a [list of timezones](misc/tz_all.txt) known to my Debian GNU/Linux 7. It was generated with this script:
-
-```ruby
-require 'tzinfo'
-TZInfo::Timezone.all.each { |tz| puts tz.name }
-```
-
-Unknown timezones, typos, will be rejected by tzinfo thus rufus-scheduler.
-
-On its own tzinfo derives the timezones from the system's information. On some system it needs some help, one can install the 'tzinfo-data' gem to provide the missing information.
 
 
 ## so Rails?
 
 Yes, I know, all of the above is boring and you're only looking for a snippet to paste in your Ruby-on-Rails application to schedule...