README.md in vendorificator-0.5.3 vs README.md in vendorificator-0.6.0

@@ -256,13 +256,13 @@
    on the vendor branch together with downloaded dependencies
  * `:extras` -- files that are needed for the tool to work, but which
    won't be committed to the vendor branch together with specs and
    dependencies
 
-Two convenience shortcuts are provided, `rubygems_bundler`, and
-`chef_berkshelf`. They take no arguments. Their definitions are
-examples as well:
+Two convenience shortcuts are provided, `rubygems_bundler`,
+and `chef_berkshelf`. Their definitions are examples
+as well:
 
 ```ruby
 tool 'rubygems', # <- rubygems_bundler
      :path => 'cache',
      :specs => [ 'Gemfile', 'Gemfile.lock' ],
@@ -271,11 +271,22 @@
 
 ```ruby
 tool 'cookbooks', # <- chef_berkshelf
      :path => 'cookbooks',
      :specs => [ 'Berksfile', 'Berksfile.lock' ],
-     :command => 'berks install --path vendor/cookbooks'
+     :command => 'berks vendor vendor/cookbooks'
 ```
+
+`rubygems_bundler` takes no arguments and it passes block to `tool`.
+
+`chef_berkshelf` takes following arguments:
+
+ - `:path` (default: `'cookbooks'`) -- path to save cookbooks
+ - `:specs` (array, always present: `Berksfile` and `Berksfile.lock`)
+   -- files treated as specs (you can specify `metadata.rb` files of your
+   local cookbooks to include their dependencies automatically)
+ - `:berks2` (default: false) -- if set to `true`, use command for
+   Berkshelf 2 (default is Berkshelf 3)
 
 #### overlay
 
 Overlays multiple modules in the same directory, instead of each of them being
 conjured in its own.