README.md in ruby_dep-1.3.0 vs README.md in ruby_dep-1.3.1

@@ -39,10 +39,12 @@
 
 With RubyDep, your gemspec's `required_ruby_version` can be automatically set based on which Rubies you test your gem on.
 
 What about the README? Well, just insert a link to your Travis build status page!
 
+Example: do you want to know which Ruby versions RubyDep can be installed on? Just look here: https://travis-ci.org/e2/ruby_dep
+
 If you're running Travis builds on a Ruby you support (and it's not in the "allow failures" section), it means you support that version of Ruby, right?
 
 RubyDep intelligently creates a version constraint to encompass Rubies listed in your `.travis.yml`.
 
 ## Usage (to solve Problem 1)
@@ -60,14 +62,14 @@
   s.add_development_dependency 'ruby_dep', '~> 1.1'
 ```
 
 ### In your `README.md`:
 
-Replace your mentions of "supported Ruby versions" to point to the Travis build.
+Replace your mentions of "supported Ruby versions" and just insert a link to your Travis build status page.
 
-If users see their Ruby version "green" on Travis, it suggests it's supported, right?
+If users see their Ruby version "green" on Travis, they'll see those are the versions you support and test, right?
 
-(Or, you can point to the rubygems.org site where the required Ruby version is listed).
+(Or, you can link to your project's rubygems.org page where the required Ruby version is listed).
 
 ### In your `.travis.yml`:
 
 To add a "supported Ruby", simply add it to the Travis build.