README.md in data_seeder-0.0.1 vs README.md in data_seeder-0.0.2

@@ -80,20 +80,22 @@
 
 data_seeder has default loaders for txt, csv, json and yml extensions but you can also create
 your own custom loaders.
 For instance, suppose you had the following tables:
 
-    create_table "app_errors", force: :cascade do |t|
-      t.integer "app_id"
-      t.string  "code"
-      t.string  "message"
-    end
-    add_index "app_errors", ["app_id"], name: "index_app_errors_on_app_id"
+```ruby
+create_table "apps", force: :cascade do |t|
+  t.string "name"
+end
 
-    create_table "apps", force: :cascade do |t|
-      t.string "name"
-    end
+create_table "app_errors", force: :cascade do |t|
+  t.integer "app_id"
+  t.string  "code"
+  t.string  "message"
+end
+add_index "app_errors", ["app_id"], name: "index_app_errors_on_app_id"
+```
 
 And you wanted to load up separate error messages for each app such as the following 2 files:
 
     # foo.err
     1 Something went wrong
@@ -220,9 +222,11 @@
 
 Caching of long-running stuff via pg_dump, mysqldump, or other?  This belongs with discussion of the environment-specific
 seeding above.
 
 Allow config-driven initialization so that we could require: false in the Gemfile and only load as needed.
+
+Add depends_on option.
 
 Meta
 ----
 
 * Code: `git clone git://github.com/bpardee/data_seeder.git`