README.md in stack-kicker-0.0.12 vs README.md in stack-kicker-0.0.13

@@ -59,11 +59,11 @@
 #### :skip_chef_prereg
 This is usually only used when :chef_server = true, it stops stack-kicker from attempting to pre-create the chef client & node and applying roles to the node.
 #### :security_group
 security group to be assigned to this node.  (set to default is you don't want to manage security groups for every role)
 #### :cloud_config_yaml
-defaults to a file which contains a simple template (lib/cloud-config.yaml in the github repo) that installs the http://apt.opscode.com repo & gpg key, as well as installing the opscode-keyring.  Can be replaced with any filename that complies with cloud-init. If the filename supplied ends in '.erb', it will be processed with ERB. See [ERB Templates](#erbtemplates) for details on available data.
+defaults to a file which contains a simple template (lib/cloud-config.yaml in the github repo) that installs the http://apt.opscode.com repo & gpg key, as well as installing the opscode-keyring.  Can be replaced with any filename that complies with cloud-init. If the filename supplied ends in '.erb', it will be processed with ERB. See [ERB Templates](#erb-templates) for details on available data.
 #### :bootstrap
 Optional filename, the contents of which will get combined with :cloud_config_yaml to form the cloud-init payload (using mime encoding, supported types are #include, ) with some variable substation (chef server ip, environment, validation.pem, roles)  See lib/chef-client-bootstrap-excl-validation-pem.sh as an example.
 
 :cloud_config_yaml & :bootstrap files can be of the following type:
 
@@ -92,28 +92,28 @@
 
 There are 3 key data sets exposed to the ERB templates:
 
 * instances - subset all_instances, just the nodes referenced/managed by this Stackfile
 * all_instances - hash of all instances running in this account
-* config - config contains all the config data from the Stackfile, as well as info about running instances in the account used by the Stackfile 
+* config - config contains all the config data from the Stackfile, as well as info about running instances in the account used by the Stackfile
 
 instances & all_instances hashes look like this:
 
 ```
 {
   "webci-az1-web0001" => {
-    :region => "az-1.region-a.geo-1", 
-    :id => 1395635, 
-    :private_ips => ["10.5.170.11"], 
-    :public_ips => ["15.185.114.181"], 
-    :az => "az-1.region-a.geo-1", 
-    :role => :web}, 
+    :region => "az-1.region-a.geo-1",
+    :id => 1395635,
+    :private_ips => ["10.5.170.11"],
+    :public_ips => ["15.185.114.181"],
+    :az => "az-1.region-a.geo-1",
+    :role => :web},
   "webci-az1-web0002" => {
-    :region => "az-1.region-a.geo-1", 
-    :id => 1396181, 
-    :private_ips => ["10.5.172.145"], 
-    :public_ips => ["15.185.110.42"], 
-    :az => "az-1.region-a.geo-1", 
+    :region => "az-1.region-a.geo-1",
+    :id => 1396181,
+    :private_ips => ["10.5.172.145"],
+    :public_ips => ["15.185.110.42"],
+    :az => "az-1.region-a.geo-1",
     :role=>:web
   }
 }
 ```
 So say you wanted to drop the private IP address of webci-az1-web0001 into the hosts file of webci-az1-web0002 via cloud-init, this fragment in your :cloud_config_yaml could be used: