README.md in omniauth-twitter-0.0.5 vs README.md in omniauth-twitter-0.0.6

@@ -4,28 +4,33 @@
 
 Twitter uses the OAuth 1.0a flow, you can read about it here: https://dev.twitter.com/docs/auth/oauth
 
 ## How To Use It
 
-Usage is as per any other OmniAuth 1.0 strategy. So let's say you're using Rails, you need to add the strategy to your `Gemfile` along side omniauth:
+Usage is as per any other OmniAuth 1.0 strategy. So let's say you're using Rails, you need to add the strategy to your `Gemfile`:
 
-    gem 'omniauth'
     gem 'omniauth-twitter'
 
 You can pull them in directly from github e.g.:
 
-    gem 'omniauth', :git => 'https://github.com/intridea/omniauth.git'
-    gem 'omniauth-twitter', :git => 'https://github.com/arunagw/omniauth-twitetr.git'
+    gem 'omniauth-twitter', :git => 'https://github.com/arunagw/omniauth-twitter.git'
 
 Once these are in, you need to add the following to your `config/initializers/omniauth.rb`:
 
     Rails.application.config.middleware.use OmniAuth::Builder do
       provider :twitter, "consumer_key", "consumer_secret" 
     end
 
 You will obviously have to put in your key and secret, which you get when you register your app with Twitter (they call them API Key and Secret Key). 
 
 Now just follow the README at: https://github.com/intridea/omniauth
+
+## Supported Rubies
+
+OmniAuth Twitter is tested under 1.8.7, 1.9.2, 1.9.3 and Ruby Enterprise Edition.
+
+[![CI Build
+Status](https://secure.travis-ci.org/arunagw/omniauth-twitter.png)](http://travis-ci.org/arunagw/omniauth-twitter)
 
 ## Note on Patches/Pull Requests
 
 - Fork the project.
 - Make your feature addition or bug fix.
\ No newline at end of file