Merge pull request #99 from wonda-tea-coffee/fix-typo

Fix typo

Author: jenseng

README.md

@@ -101,10 +101,10 @@ Only fire the update trigger if at least one of the columns is specified in the
 Permissions/role to check when calling trigger. PostgreSQL supports `:invoker` (default) and `:definer`, MySQL supports `:definer` (default) and arbitrary users (syntax: `'user'@'host'`).
 
 #### timing(timing)
-Required (but may be satisified by `before`/`after`). Possible values are `:before`/`:after`.
+Required (but may be satisfied by `before`/`after`). Possible values are `:before`/`:after`.
 
 #### events(*events)
-Required (but may be satisified by `before`/`after`). Possible values are `:insert`/`:update`/`:delete`/`:truncate`. MySQL/SQLite only support one action per trigger, and don't support `:truncate`.
+Required (but may be satisfied by `before`/`after`). Possible values are `:insert`/`:update`/`:delete`/`:truncate`. MySQL/SQLite only support one action per trigger, and don't support `:truncate`.
 
 #### nowrap(flag = true)
 PostgreSQL-specific option to prevent the trigger action from being wrapped in a `CREATE FUNCTION`. This is useful for executing existing triggers/functions directly, but is not compatible with the `security` setting nor can it be used with pre-9.0 PostgreSQL when supplying a `where` condition.

lib/hair_trigger.rb

@@ -62,7 +62,7 @@ def current_migrations(options = {})
         options[:skip_pending_migrations] = true
       end
 
-      # if we're in a db:schema:dump task (explict or kicked off by db:migrate),
+      # if we're in a db:schema:dump task (explicit or kicked off by db:migrate),
       # we evaluate the previous schema.rb (if it exists), and then all applied
       # migrations in order (even ones older than schema.rb). this ensures we
       # handle db:migrate:down scenarios correctly