README.md in bower-rails-0.9.0 vs README.md in bower-rails-0.9.1

@@ -26,11 +26,11 @@
 **Install**
 
 in Gemfile
 
 ``` Ruby
-  gem "bower-rails", "~> 0.8.3"
+  gem "bower-rails", "~> 0.9.1"
 ```
 
 ##JSON configuration
 
 Bower-rails now supports the standard [bower package](https://github.com/bower/bower#defining-a-package) format out-of-the-box. Simply place your bower.json file the Rails root directory to start. Using the standard format will default all bower components to be installed under the `vendor` directory.
@@ -177,11 +177,11 @@
     "angular": "1.2.22"
   }
 }
 ```
 
-[#bower resolution]: http://jaketrent.com/post/bower-resolutions/
+[bower resolution]: http://jaketrent.com/post/bower-resolutions/
 
 ##Configuration
 
 Change options in your `config/initializers/bower_rails.rb`:
 
@@ -226,9 +226,10 @@
 * `rake bower:update` to update packages
 * `rake bower:update:prune` to update components and uninstall extraneous packages
 * `rake bower:list` to list all packages
 * `rake bower:clean` to remove all files not listed as [main files](#bower-main-files) (if specified)
 * `rake bower:resolve` to resolve [relative asset paths](#relative-asset-paths) in components
+* `rake bower:cache:clean` to clear the bower cache. This is useful when you know a component has been updated. 
 
 If you'd like to pass any bower CLI options to a rake task, like `-f`, `-j`, you can simply do:
 
 ```bash
 rake bower:install['-f']