readme spring cleaning

README.md

@@ -18,16 +18,13 @@ use the Resque client to enqueue messages in Redis to be processed by Sidekiq.
 At the same time, Sidekiq uses multithreading so it is much more memory efficient than
 Resque (which forks a new process for every job).  You'll find that you might need
 50 200MB resque processes to peg your CPU whereas one 300MB Sidekiq process will peg
-the same CPU and perform the same amount of work.  Please see [my blog post on Resque's memory
-efficiency](http://blog.carbonfive.com/2011/09/16/improving-resques-memory-efficiency/)
- and how I was able to shrink a Carbon Five client's resque processing farm
-from 9 machines to 1 machine.
+the same CPU and perform the same amount of work.
 
 
 Requirements
 -----------------
 
-I test on Ruby 1.9.3 and JRuby 1.6.x in 1.9 mode.  Other versions/VMs are
+I test on Ruby 1.9.3 and JRuby 1.7.x.  Other versions/VMs are
 untested but I will do my best to support them.  Ruby 1.8 is not supported.
 
 Redis 2.0 or greater is required.
@@ -48,7 +45,7 @@ You can watch [Railscast #366](http://railscasts.com/episodes/366-sidekiq) to se
 ![Web UI](https://github.com/mperham/sidekiq/raw/master/examples/web-ui.png)
 
 
-Want More?
+Want to Upgrade?
 -------------------
 
 I also sell Sidekiq Pro, an extension to Sidekiq which provides more