README.md in sql_migrations-2.1.0 vs README.md in sql_migrations-2.1.1

@@ -103,11 +103,11 @@
     `default` database configuration is optional, nonetheless if supplied it will not be necessary to create additional subdirectory to store migrations (look below).
 
     If you have multi-statement migrations you should provide `separator` configuration variable in `options` block. `options` key is optional in YAML.
 
 
-4.  Migrations/seed/fixtures can be executed using rake tasks. So you will need to create `Rakefile`:
+4.  Migrations/seeds/fixtures can be executed using rake tasks. So you will need to create `Rakefile`:
 
     ```ruby
     require 'bundler'
     Bundler.require
 
@@ -145,11 +145,11 @@
 5.  It's ready !
   
 
 ## Usage
 
-1.  Valid migration/seed/fixture file names match against regexp `/(\d{8})_(\d{6})_(.*)?\.sql/`. So valid filenames would be:
+1.  Valid migration/seeds/fixture file names match against regexp `/(\d{8})_(\d{6})_(.*)?\.sql/`. So valid filenames would be:
 
 
         20150303_180100_test_migration.sql
         20150303_180100_whatever_description_of_seed.sql
         20150303_180100_fixture1.sql
@@ -161,11 +161,11 @@
         db/
           migrations/
             20150303_180100_test_migration.sql
           fixtures/
             20150303_180100_fixture1.sql
-          seed/
+          seeds/
             20150303_180100_whatever_description_of_seed.sql
 
     If you want to use multiple databases, create also database directories:
 
         db/
@@ -173,10 +173,10 @@
             default/
             second_db/
           fixtures/
             default/
             second_db/
-          seed/
+          seeds/
             default/
             second_db/
 
     `default/` directory is optional, you can put migrations/seed data/fixtures for default database in base directories: