README.md in cdq-0.1.1 vs README.md in cdq-0.1.2

@@ -12,20 +12,35 @@
 wanted to take things in a different direction, so I cut loose and ended up
 rewriting almost everything.  If you pay attention, you can still find the
 genetic traces, so thanks to @alloy for sharing his work and letting me learn
 so much.
 
+[![Dependency Status](https://gemnasium.com/infinitered/cdq.png)](https://gemnasium.com/infinitered/cdq)
+[![Build Status](https://travis-ci.org/infinitered/cdq.png?branch=master)](https://travis-ci.org/infinitered/cdq)
+[![Gem Version](https://badge.fury.io/rb/cdq.png)](http://badge.fury.io/rb/cdq)
+
 ### Why use a static Data Model?
 
 By using a real data model file that gets compiled and included in your bundle,
 you can take advantage of automatic migration, which simplifies managing your
-schema as it grows, if you can follow a few simple rules.  
+schema as it grows, if you can follow a few [simple rules](https://developer.apple.com/library/ios/documentation/cocoa/conceptual/CoreDataVersioning/Articles/vmLightweightMigration.html#//apple_ref/doc/uid/TP40004399-CH4-SW2).  
 
 ## Installing
 
-Using Bundler:
+##### Quick Start:
 
+```bash
+$ gem install cdq
+$ motion create my_app # if needed
+$ cd my_app
+$ cdq init
+```
+
+This way assumes you want to use ruby-xcdm.  Run ```cdq -h``` for list of more generators.
+
+##### Using Bundler:
+
 ```ruby
 gem 'cdq'
 ```
 
 If you want to see bleeding-edge changes, point Bundler at the git repo:
@@ -49,13 +64,9 @@
 
   def application(application, didFinishLaunchingWithOptions:launchOptions)
     cdq.setup
     true
   end
-end
-
-class TopLevel
-  include CDQ
 end
 ```
 
 That's it!  You can create specific implementation classes for your entities if
 you want, but it's not required.  You can start running queries on the console or