All Windows testing has been performed from the vanilla Windows XP command prompt. Cygwin support @@ -48,7 +48,7 @@ Vagrant, and the virtualbox gem on which it relies, require that the VBoxManage  -You can add additional folders to Windows XP path by taking the following steps. First click Start, right click My Computer and select Properties. Select the Advanced tab in the window that pops up and find the Environment Variables button +You can add this or other folders to the Windows XP path by taking the following steps. First click Start, right click My Computer and select Properties. Select the Advanced tab in the window that pops up and find the Environment Variables button  @@ -73,13 +73,13 @@ After this completes you'll need to move onto the following section to connect t ### Putty -Since SSH is not easy to use/install on the command line under Windows we have included a [Putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) formatted private key generated from the keypair included with the Vagrant gem. This allows quick and easy SSH access to all Base Boxes that leverage those keys. +Since SSH is not easy to use/install on the command line under Windows we have included a [Putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) formatted private key generated from the key pair included with the Vagrant gem. This allows quick and easy SSH access to all Base Boxes that leverage that key pair. -To configure Putty we need 3 things: a user to log on with, the port that Vagrant forwarded for ssh, and the location of the ppk file. By default the first two will be `vagrant` and 2222, but there are many reasons those may be different, especially the port (other vm's services etc). If you've come here after following the quick start you'll have seen the following: +To configure Putty we need 3 things: a user to log on with, the port that Vagrant forwarded for ssh, and the location of the ppk file. By default the first two will be `vagrant` and 2222, but there are many reasons those may be different, especially the port (other vm's services etc). At this point if you issue `vagrant ssh` from the directory where you created your initial vm you should see something like the following:  -It's important to take note of both the port and the .ppk file location. If you've used the Ruby 1.8.6 installer, the above path will be the same for you. Moving on, once you've got Putty installed, opening putty.exe will present you with the connection configuration window. First enter the SSH information and a name for the connection, then open the SSH configuration sub-tree. +It's important to take note of both the port and the .ppk file location. If you've used the Ruby 1.8.6 installer, the above path will be the same for you taking into account the version of the Vagrant gem you have installed. Moving on, once you've got Putty installed, opening putty.exe will present you with the connection configuration window. First enter the SSH information and a name for the connection, then open the SSH configuration sub-tree.  @@ -87,10 +87,10 @@ Here in the `Auth` configuration section we'll take the path information provide  -Once you've done that head to the top of the configuration tree and click the `Session` tree item and save the putty configuration so it will be available for use again later. +Once you've done that head to the top of the configuration tree, click the `Session` tree item and save the putty configuration so it will be available for use again later.  -Last but not least, click the Open button to be presented with a bash prompt inside your new and shiny Vagrant virtual development environtment! +Last but not least, click the Open button to be presented with a bash prompt inside your new and shiny Vagrant virtual development environtment! If you've taken the steps above to save the configuration it should be easy to use and adapt to other virtual environments created with Vagrant.