README.md in vagrant-orchestrate-0.6.2 vs README.md in vagrant-orchestrate-0.6.3

@@ -54,14 +54,10 @@
 
 Which produces a simple default Vagrantfile that can push to managed servers:
 ```ruby
 managed_servers = %w( )
 
-required_plugins = %w( vagrant-managed-servers )
-required_plugins.each do |plugin|
-  system "vagrant plugin install #{plugin}" unless Vagrant.has_plugin? plugin
-end
 Vagrant.configure("2") do |config|
   # This disables up, provision, reload, and destroy for managed servers. Use
   # `vagrant orchestrate push` to communicate with managed servers.
   config.orchestrate.filter_managed_commands = true
 
@@ -109,14 +105,28 @@
   config.winrm.password = "PASSWORD"
 ```
 
 #### Plugins
 
-This also supports a portable and repeatable way to install plugins, just list them in the required_plugins section
+This also supports a portable and repeatable way to install plugins, just list them in the .vagrantplugins file.
+`version` and `source` are the supported values in the options hash, but neither is required.
 
 ```ruby
-required_plugins = %w( vagrant-managed-servers vagrant-hostsupdater )
+required_plugins = {}
+required_plugins["vagrant-orchestrate"] = {}
+required_plugins["vagrant-managed-servers"] = { version: "0.7.0" }
 ```
+
+If you are executing in a shared environment, like a build slave, you can create your own
+own plugin install directory by setting the `VAGRANT_HOME` variable to something relative
+to the current directory.
+
+    $ VAGRANT_HOME=./.vagrant.d vagrant orchestrate push
+
+or
+
+    > SET VAGRANT_HOME=./.vagrant.d
+    > vagrant orchestrate push
 
 #### Working with multiple environments
 
 Vagrant Orchestrate offers a way to manage multiple environments using a combination of a single servers.json file and the name of the current git branch as an indicator of the current environment.