README.md in chef-provisioning-vsphere-0.5.5 vs README.md in chef-provisioning-vsphere-0.5.6

@@ -9,21 +9,21 @@
 
 ### Vsphere infrastructure
 
 A vcenter and valid login credentials.
 
-### VM Teplate
+### VM Template
 
 A VM template capable of installing Chef 11.8 or newer. This can be either windows or linux flavored.
 
 ### A provisioning node (can be local)
 
-An environment equipped with the chef client and the chef-Provision-vsphere gem.
+An environment equipped with the chef client and the chef-provisioning-vsphere gem.
 
 ## A basic provisioning recipe
 
-This is a minimal machine devinition that will use a dhcp assigned ip (it assumes the presense of a dhcp server). For test purposes this uses a linked clone for a faster provisioning time. This recipe should be used with a linux template. Windows provisioned servers need to point to a chef server for the cookbooks since winrm does not support port forwarding and there fore cannot reach back on the chef-zero port to get the local cookbooks. See examples below.
+This is a minimal machine definition that will use a dhcp assigned ip (it assumes the presense of a dhcp server). For test purposes this uses a linked clone for a faster provisioning time. This recipe should be used with a linux template. Windows provisioned servers need to point to a chef server for the cookbooks since winrm does not support port forwarding and there fore cannot reach back on the chef-zero port to get the local cookbooks. See examples below.
 
 ```
 chef_gem 'chef-provisioning-vsphere' do
   action :install
   compile_time true
@@ -133,37 +133,44 @@
 }
 ```
 
 ### Domain joined windows machine
 
-Note: You must run chef-client against a server for a windows box. You cn do this locally since the provisioning recipe should not change the state of the provisioner. You will need to upload the cookbook (both the one doing the provisioning and the one used in the provisioned machine's runlist) before running `chef-client`.
-
 ```
 with_machine_options :bootstrap_options => {
   use_linked_clone: true,
   num_cpus: 2,
   memory_mb: 4096,
-  network_name: ["vlan_20_172.21.20"],
+  network_name: ['vlan_20_172.21.20'],
   datacenter: 'datacenter_name',
   resource_pool: 'cluster',
   template_name: 'path to template',
   customization_spec: {
     ipsettings: {
       dnsServerList: ['1.2.3.31','1.2.3.41']
     },
-    domain => 'blah.com',
-    domainAdmin => "[e-mail]",
-    domainAdminPassword => "Passwordyoyoyo",
-    org_name => 'acme',
-    product_id => 'CDAA-87DC-3455-FF77-2AAC',
-    win_time_zone => 4
+    domain: 'blah.com',
+    domainAdmin: '[e-mail]',
+    domainAdminPassword: 'Passwordyoyoyo',
+    org_name: 'acme',
+    product_id: 'CDAA-87DC-3455-FF77-2AAC',
+    win_time_zone: 4
   }
-  :ssh => {
-    :user => 'administrator',
-    :password => 'password',
-    :paranoid => false,
+  ssh: {
+    user: 'administrator',
+    password: 'password',
+    paranoid: false,
   }
+},
+:convergence_options => {
+  :ssl_verify_mode => :verify_none
 }
+```
+Note: You must run chef-client against a server for a windows box. You can do this locally since the provisioning recipe should not change the state of the provisioner. You will need to upload the cookbook (both the one doing the provisioning and the one used in the provisioned machine's runlist) before running `chef-client`.
+
+```
+knife cookbook upload my_cookbook
+chef-client -o 'my_cookbook::provision' -c .chef/knife.rb
 ```
 
 ## Kitchen Driver
 
 This chef-provisioning-driver comes with a test-kitchen driver. Here are example driver options you can add to your `kitchen.yml`.