README.rdoc in visionmedia-jspec-2.10.0 vs README.rdoc in visionmedia-jspec-2.11.0

@@ -31,10 +31,11 @@
 * `jspec` command-line utility for auto-running specs, and initializing project templates
 * Proxy or 'Spy' assertions 
 * Method Stubbing
 * Shared behaviors
 * Profiling
+* Interactive Shell
 * Ruby on Rails Integration
 * Tiny (15 kb compressed, 1300-ish LOC)
 
 == Installation
 
@@ -47,10 +48,17 @@
   $ sudo gem install visionmedia-jspec 
 
 At which point you may:
   $ jspec init myproject
 
+By default, the command above will use absolute path for all JSpec library files.
+This behavior can be a problem when you're working across different computers or
+operating systems. You can freeze the library or symlink it.
+
+  $ jspec init myproject --freeze
+  $ jspec init myproject --symlink
+
 JSpec scripts should NOT be referenced via the <script> tag, they should be
 loaded using the exec method (unless you are using the grammar-less alternative).
 Below is an example:
 
   ...
@@ -698,10 +706,24 @@
 For example $.get('/slow/4', function(){}) will take 4 seconds
 to reply, where as $.get('/status/404', function(){}) will respond
 with an 404 status code. Add additional Sinatra routes to the jspec.rb
 file to add your own functionality.
 
+== Interactive Shell
+
+JSpec provides an interactive shell through Rhino, utilize with:
+
+$ jspec shell
+
+Or to specify additional files to load:
+
+$ jspec shell lib/*.js
+
+Or view additional shell help
+
+$ jspec help shell
+
 == Ruby on Rails
 
 No additional gems are required for JSpec to work with rails, although 
 http://github.com/bhauman/jspec-rails has been created by 'bhauman'. JSpec
 supports Rails out of the box, simply execute:
@@ -720,10 +742,21 @@
   
 Or run via the terminal using Rhino:
 
   $ jspec run --rhino
   
+== Support Browsers
+
+Browsers below are supported and can be found in server/browsers.rb, however
+your spec/server.rb file may support additional browsers.
+
+* Safari
+* Chrome
+* Firefox
+* Opera
+* Internet Explorer
+  
 == Known Issues
 
 * Tabs may cause a parse error. To prevent this use 'soft tabs' (setting in your IDE/Editor)
   or use JSpec's grammar-less alternative (mentioned above).
   
@@ -760,9 +793,10 @@
 
 * Lawrence Pit
 * [e-mail]
 * [e-mail]
 * [e-mail]
+* fnando
 
 == License 
 
 (The MIT License)