aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorJon Moss <me@jonathanmoss.me>2017-08-16 10:41:25 -0400
committerJon Moss <me@jonathanmoss.me>2017-08-16 10:41:25 -0400
commit58e971c2d1f89cccda4f7494b30635e041596b31 (patch)
tree2bbc361e20e452ea594e0a67fb7e8bc6b0ee796c /guides
parent393a7aad99c1a5fbd1ff8d83390b8243267b3334 (diff)
downloadrails-58e971c2d1f89cccda4f7494b30635e041596b31.tar.gz
rails-58e971c2d1f89cccda4f7494b30635e041596b31.tar.bz2
rails-58e971c2d1f89cccda4f7494b30635e041596b31.zip
Small grammar fixes
Changed sentence to be more clear [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/active_record_callbacks.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/active_record_callbacks.md b/guides/source/active_record_callbacks.md
index fc4f773e3c..53417f012e 100644
--- a/guides/source/active_record_callbacks.md
+++ b/guides/source/active_record_callbacks.md
@@ -429,7 +429,7 @@ end
WARNING. The `after_commit` and `after_rollback` callbacks are called for all models created, updated, or destroyed within a transaction block. However, if an exception is raised within one of these callbacks, the exception will bubble up and any remaining `after_commit` or `after_rollback` methods will _not_ be executed. As such, if your callback code could raise an exception, you'll need to rescue it and handle it within the callback in order to allow other callbacks to run.
-WARNING. Using `after_create_commit` and `after_update_commit` both in the same model will override the callback which was registered first amongst them.
+WARNING. Using both `after_create_commit` and `after_update_commit` in the same model will only allow the last callback defined to take effect, and will override all others.
```ruby
class User < ApplicationRecord