+ Vagrant 0.4 has been released! Read the full list of changes.
+
diff --git a/docs/changes/changes_03x_04x.md b/docs/changes/changes_03x_04x.md
new file mode 100644
index 000000000..f91768f74
--- /dev/null
+++ b/docs/changes/changes_03x_04x.md
@@ -0,0 +1,54 @@
+---
+layout: documentation
+title: Changes - 0.3.x to 0.4.x
+---
+# Changes in Vagrant 0.4.x
+
+## VirtualBox 3.2 Support
+
+Vagrant now supports VirtualBox 3.2.0 in addition to the 3.1.x series.
+No configuration is necessary; Vagrant will automatically determine which
+VirtualBox version is running and use the correct API calls.
+
+## Multi-VM Environments
+
+Vagrant can now automate and manage multiple VMs to represent a single
+project. This allows developers to model more complex server setups on
+their development machine.
+
+TODO: More explanation + docs.
+
+## Host Only Networking
+
+Prior to 0.4.x, Vagrant could only forward ports via a NAT connection.
+Vagrant now allows VMs to specify a static IP for themselves, which
+can be accessed on the host machine or any other VMs on the same
+host only network. This feature can work hand in hand with the multi-VM
+feature announced above to provide efficient internal networking between
+VMs.
+
+TODO: Docs
+
+## Automatic Port Collision Fixes
+
+Since version 0.2.0, Vagrant has reported any potential port collisions
+for forwarded ports. This was typically a rare occurence which only cropped
+up when multiple Vagrant environments were running at the same time. With
+the introduction of multi-VM support, port collision is now quite common.
+To deal with this, Vagrant can now automatically resolve any port collisions
+which are detected.
+
+TODO: Docs
+
+## Minor Changes
+
+### `vagrant provision`
+
+`vagrant provision` can now be called at any time to simply run the provisioning
+scripts without having to reload the entire VM environment. There are certain
+limitations to this command which are discussed further on the commands
+documentation page.
+
+### Many Bug Fixes
+
+As always, a handful of bugs have been fixed since Vagrant 0.3.0.
diff --git a/docs/commands.md b/docs/commands.md
index de8296176..b8d2f83e2 100644
--- a/docs/commands.md
+++ b/docs/commands.md
@@ -11,21 +11,26 @@ run `vagrant` alone:
{% highlight bash %}
$ vagrant
-Usage: vagrant SUBCOMMAND ...
+Usage: vagrant SUBCOMMAND
+ --help Show help for the current subcommand.
+ --version Output running Vagrant version.
-Supported commands:
- box Box commands
- destroy Destroys the vagrant environment
- halt Halts the currently running vagrant environment
- init Initializes current folder for Vagrant usage
- package Packages a vagrant environment for distribution
- reload Reload the vagrant environment
- resume Resumes a suspend vagrant environment
- ssh SSH into the currently running environment
- ssh-config outputs .ssh/config valid syntax for connecting to this environment via ssh
- status Shows the status of the current environment.
- suspend Suspends the currently running vagrant environment
- up Creates the vagrant environment
+Supported subcommands:
+ box Box commands
+ destroy Destroys the vagrant environment
+ halt Halts the currently running vagrant environment
+ init Initializes current folder for Vagrant usage
+ package Packages a vagrant environment for distribution
+ provision Run the provisioner
+ reload Reload the vagrant environment
+ resume Resumes a suspend vagrant environment
+ ssh SSH into the currently running environment
+ ssh-config outputs .ssh/config valid syntax for connecting to this environment via ssh
+ status Shows the status of the Vagrant environment.
+ suspend Suspends the currently running vagrant environment
+ up Creates the vagrant environment
+
+For help on a specific subcommand, run `vagrant SUBCOMMAND --help`
{% endhighlight %}
## Built-in Help
@@ -89,6 +94,17 @@ and register an identical virtual environment for other projects or other machin
that if you intend to recreate an identical experience for another developer using Vagrant that the Vagrantfile
residing at the root of your project directory should be included, see [Vagrant Boxes](/docs/boxes.html#creating-a-box) for more information.
+
+## vagrant provision
+
+Runs the provisioning scripts without reloading the entire Vagrant environment.
+If you're just tweaking or adding some cookbooks, this command can save you a
+lot of time.
+
+Since this command doesn't reload the entire environment or reboot the VM,
+it will not add new cookbooks folders if the cookbooks folder path changes. In
+this case, please call `vagrant reload`.
+
## vagrant resume
diff --git a/docs/getting-started/boxes.md b/docs/getting-started/boxes.md
index 7cb14371c..95497715b 100644
--- a/docs/getting-started/boxes.md
+++ b/docs/getting-started/boxes.md
@@ -38,7 +38,7 @@ multiple projects at the same time. Each project uses the box as a _base_ only,
project VM is created, modifications can be made without affecting other
projects which may use the same box.
-Note that the box is given its own name, in this case "rails." This name
+Note that the box is given its own name, in this case "getting_started." This name
is used throughout Vagrant to reference that box from this point forward.
The URL is only used when adding, but never again. And the filename of the
box means nothing to the logical name given. It is simply a coincidence that