README.rdoc in inherited_resources-1.2.2 vs README.rdoc in inherited_resources-1.3.0

@@ -6,12 +6,12 @@
 
 Plus, making your controllers follow a pattern, it helps you to write better
 code by following fat models and skinny controllers convention. There are
 two screencasts available besides this README:
 
-http://railscasts.com/episodes/230-inherited-resources
-http://akitaonrails.com/2009/09/01/screencast-real-thin-restful-controllers-with-inherited-resources
+* http://railscasts.com/episodes/230-inherited-resources
+* http://akitaonrails.com/2009/09/01/screencast-real-thin-restful-controllers-with-inherited-resources
 
 == Installation
 
 === Rails 3
 
@@ -37,19 +37,16 @@
 
   http://github.com/josevalim/inherited_resources/tree/v1.0
 
 == HasScope
 
-Since Inherited Resources 1.0, has_scope is not part of its core anymore.
-However, if you are using has_scope in your application, Inherited Resources
-will handle all the required hooks automatically.
+Since Inherited Resources 1.0, has_scope is not part of its core anymore but
+a gem dependency. Be sure to check the documentation to see how you can use it:
 
-has_scope gem is available at:
-
   http://github.com/plataformatec/has_scope
 
-And can be installed as:
+And it can be installed as:
 
   gem install has_scope
 
 == Responders
 
@@ -512,10 +509,12 @@
 Sometimes just DRY the controllers is not enough, if you need to DRY up your views,
 check this Wiki page:
 
 https://github.com/josevalim/inherited_resources/wiki/Views-Inheritance
 
+Notice that Rails 3.1 ships with view inheritance built-in.
+
 == Some DSL
 
 For those DSL lovers, InheritedResources won't leave you alone. You can overwrite
 your success/failure blocks straight from your class binding. For it, you just
 need to add a DSL module to your application controller:
@@ -532,11 +531,11 @@
       end
     end
 
 == Bugs and Feedback
 
-If you discover any bugs or want to drop a line, join us in the mailing list:
+If you discover any bugs, please describe it in the issues tracker, including Rails and Inherited Resources versions.
 
-http://groups.google.com/group/inherited_resources
+Questions are better handled on StackOverflow.
 
-Copyright (c) 2009 José Valim http://blog.plataformatec.com.br
+Copyright (c) 2011 José Valim http://blog.plataformatec.com.br
 See the attached MIT License.