README.md in vendorise-0.2.0 vs README.md in vendorise-0.3.0

@@ -1,9 +1,9 @@
 # Vendorise
 
-[![Gem Version](https://badge.fury.io/rb/vendorise.png)](http://badge.fury.io/rb/vendorise)
-[![Build Status](https://travis-ci.org/New-Bamboo/vendorise.png)](https://travis-ci.org/New-Bamboo/vendorise)
+[![Gem Version](http://img.shields.io/gem/v/vendorise.svg)](http://rubygems.org/gems/vendorise)
+[![Build Status](http://img.shields.io/travis/iainbeeston/vendorise/master.svg)](https://travis-ci.org/iainbeeston/vendorise)
 
 Sometimes you need to use a gem that is only available in a private git repository. There are a few ways to do this:
 
 * Install an SSH certificate on your server, but it's not always an option (for example, if you use [Heroku](http://heroku.com))
 * Use [Gemfury](http://gemfury.com), but that costs money and potentially creates privacy concerns
@@ -25,10 +25,14 @@
 
     $ gem install vendorise
 
 ## Usage
 
-1. Run `rake vendorise:gem[repo_url]` to vendorise the gem hosted at `repo_url` into `/vendor/gems`.
+1. Run `rake "vendorise:gem[repo_url]"` to vendorise the gem hosted at `repo_url` into `/vendor/gems`.
 2. Add `gem '<gem_name>', path: 'vendor/gems/<gem_name>'` to your Gemfile
 
-You can update the gem at any time by running the rake task again. Vendorise always uses the code from the master branch on git (tags are not supported yet).
+You can update the gem at any time by running the rake task again.
+
+By default the `vendorise:gem` rake task will use the master branch. To use another branch (or tag) specify it as the second parameter, like this:
+
+    rake "vendorise:gem[repo_url, branch]"