README.md in cmds-0.1.5 vs README.md in cmds-0.2.0

@@ -242,11 +242,11 @@
 though keys with those names may be accessed directly via `@kwds.fetch(key)` and the like.
 
 to test for a key's presence or optionally include a value, append `?` to the method name:
 
 ```
-c = Cmds::Cmd.new <<-BLOCK
+c = Cmds.new <<-BLOCK
   defaults
   <% if current_host? %>
     -currentHost <%= current_host %>
   <% end %>
   export <%= domain %> <%= filepath %>
@@ -348,11 +348,11 @@
 
 
 ## reuse commands
 
 ```
-playbook = Cmds::Cmd.new "ansible-playbook -i %{inventory} %{playbook}"
+playbook = Cmds.new "ansible-playbook -i %{inventory} %{playbook}"
 playbook.call inventory: "./hosts", playbook: "blah.yml"
 ```
 
 currying
 
@@ -374,11 +374,11 @@
 NEEDS TEST
 
 can be accomplished with reuse and currying stuff
 
 ```
-playbook = Cmds::Cmd.new "ansible-playbook -i %{inventory} %{playbook}", inventory: "inventory/dev"
+playbook = Cmds.new "ansible-playbook -i %{inventory} %{playbook}", inventory: "inventory/dev"
 
 # run setup.yml on the development hosts
 playbook.call playbook: "setup.yml"
 
 # run setup.yml on the production hosts
@@ -388,10 +388,10 @@
 
 
 ## input
 
 ```
-c = Cmds::Cmd.new("wc", input: "blah blah blah).call
+c = Cmds.new("wc", input: "blah blah blah).call
 ```
 
 
 
 ## future..?