README.markdown in soloist-0.0.5 vs README.markdown in soloist-0.0.6

@@ -17,13 +17,13 @@
 Just put your soloistrc file in your home directory, and point it to wherever you want to keep your cookbooks. Or just dedicate a git repo to it, and go into that directory before running soloist.
 
 # How do I write a solistrc file?
 It's a yaml file, currently with two lists to maintain:
 
-The first, _Cookbook\_Paths_, should point (using an absolute or path relative to your soloistrc file) to the directory containing your cookbooks, such was pivotal_workstation.
+The first, _cookbook\_paths_, should point (using an absolute or path relative to your soloistrc file) to the directory containing your cookbooks, such was pivotal_workstation.
 
-The second, _Recipes_ should be a list of recipes you wish to run.
+The second, _recipes_ should be a list of recipes you wish to run.
 
 # Then What?
 $> soloist
 
 
@@ -74,21 +74,21 @@
 	- ./chef/cookbooks/
 	recipes:
 	- pivotal_workstation::ack
 	env_variable_switches:
 	  RACK_ENV:
-	    development:
+	    production:
 	      cookbook_paths:
-	      - ./chef/dev_cookbooks/
+	      - ./chef/production_cookbooks/
 	      recipes:
-	      - pivotal_dev::foo
+	      - production::foo
 
 The values are merged in, so this results in a cookbook path of
 	[
       "./chef/cookbooks/",
-      "./chef/dev_cookbooks/"
+      "./chef/production_cookbooks/"
     ]
 and a recipe list of
 	[
 	  "pivotal_workstation::ack", 
-	  "pivotal_dev::foo"
+	  "production::foo"
 	]
\ No newline at end of file