README.md in capistrano-rails-1.1.0 vs README.md in capistrano-rails-1.1.1

@@ -6,12 +6,14 @@
   - `cap deploy:compile_assets`
 
 Some rails specific options.
 
 ```ruby
-set :rails_env, 'staging'       # If the environment differs from the stage name
-set :migration_role, 'migrator' # Defaults to 'db'
+set :rails_env, 'staging'                  # If the environment differs from the stage name
+set :migration_role, 'migrator'            # Defaults to 'db'
+set :assets_roles, [:web, :app]            # Defaults to [:web]
+set :assets_prefix, 'prepackaged-assets'   # Defaults to 'assets' this should match config.assets.prefix in your rails config/application.rb
 ```
 
 If you need to touch `public/images`, `public/javascripts` and `public/stylesheets` on each deploy:
 
 ```ruby
@@ -20,12 +22,12 @@
 
 ## Installation
 
 Add this line to your application's Gemfile:
 
-    gem 'capistrano',  '~> 3.0.0'
-    gem 'capistrano-rails'
+    gem 'capistrano',  '~> 3.1'
+    gem 'capistrano-rails', '~> 1.1'
 
 ## Usage
 
 Require everything (bundler, rails/assets and rails/migrations)
 
@@ -36,9 +38,11 @@
 
     # Capfile
     require 'capistrano/bundler' # Rails needs Bundler, right?
     require 'capistrano/rails/assets'
     require 'capistrano/rails/migrations'
+    
+Please note that any `require` should be placed in `Capfile`, not `config/deploy.rb`.
 
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)