diff --git a/docs/changes/changes_02x_03x.md b/docs/changes/changes_02x_03x.md
index 633ffb805..b4d51da7a 100644
--- a/docs/changes/changes_02x_03x.md
+++ b/docs/changes/changes_02x_03x.md
@@ -16,7 +16,7 @@ Vagrant now officially supports Windows as a host machine. Web developers stuck
 Windows can now develop in linux environments while continuing to use RubyMine or
 any text editor you prefer on Windows.
 
-**Windows support is new very beta. Its known to work on Windows XP and Windows 7. Windows Vista is untested.**
+**Windows support is very beta. Its known to work on Windows XP and Windows 7. Windows Vista is untested.**
 
 For a quick-start guide on Windows, see our [Windows setup guide](/docs/getting-started/setup/windows.html).
 
diff --git a/docs/provisioners/chef_solo.md b/docs/provisioners/chef_solo.md
index f40adfac2..5ddc56cdc 100644
--- a/docs/provisioners/chef_solo.md
+++ b/docs/provisioners/chef_solo.md
@@ -122,9 +122,9 @@ By default, Vagrant JSON configuration looks like the following:
 This JSON configuration is specifically thought out such that the `instance_role`
 key could be used so that cookbooks could be shared between production and development,
 possibly tweaking paths or configuration based on the `instance_role`. And
-`project_directory` is useful if you're setting up a VirtualHost for a web server,
+`directory` is useful if you're setting up a VirtualHost for a web server,
 for example, and need to set the path to the public directory within your
-`project_directory`.
+`directory`.
 
 But sometimes, cookbooks need additional, custom JSON configuration. For this
 you can specify additional JSON data in the Vagrantfile: