README.md in chef-provisioning-vsphere-2.0.2 vs README.md in chef-provisioning-vsphere-2.0.3

@@ -1,9 +1,11 @@
 # chef-provisioning-vsphere
 
 [![Gem Version](https://img.shields.io/gem/v/chef-provisioning-vsphere.svg)][gem]
 [![Build Status](https://travis-ci.org/chef-partners/chef-provisioning-vsphere.svg?branch=master)][travis]
+[![Inline docs](http://inch-ci.org/github/chef-partners/chef-provisioning-vsphere.svg?branch=master)](http://inch-ci.org/github/chef-partners/chef-provisioning-vsphere)
+[![Stories in Ready](https://badge.waffle.io/chef-partners/chef-provisioning-vsphere.png?label=ready&title=Ready)](https://waffle.io/chef-partners/chef-provisioning-vsphere?utm_source=badge)
 
 This is a [chef-provisioning](https://github.com/chef/chef-provisioning) provisioner for [VMware vSphere](http://www.vmware.com/products/vsphere).
 
 chef-provisioning-vsphere supports provisioning Unix/ssh and Windows/WinRMrm guest VMs.
 
@@ -319,11 +321,11 @@
           additional_disk_size_gb:
             - 10
             - 10
             - 10
             - 10
-            
+
 suites:
   - name: default
     runlist:
       - recipe[mycookbook::default]
   - name: memory-intensive
@@ -343,8 +345,10 @@
 1. Fork it ( https://github.com/[my-github-username]/chef-provisioning-vsphere/fork )
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create a new Pull Request
+
+We have attempted to `TODO` markings. If you find one, whether it's documentation or a feature, it's a great place to start helping out. `$ grep -r "TODO" lib/`
 
 [gem]: https://rubygems.org/gems/chef-provisioning-vsphere
 [travis]: https://travis-ci.org/chef-partners/chef-provisioning-vsphere