diff options
| author | Jon Moss <me@jonathanmoss.me> | 2017-03-29 16:14:06 -0400 |
|---|---|---|
| committer | Jon Moss <me@jonathanmoss.me> | 2017-03-29 16:14:06 -0400 |
| commit | f77a6be8d23f048ced4fac54f1f4caea5e0749d7 (patch) | |
| tree | 8bfef7d026f194591ae7da8f2ab4d1602ede6ef5 | |
| parent | 2d0d611c4db9ec63c9fdb602a95461acb5c44539 (diff) | |
| download | rails-f77a6be8d23f048ced4fac54f1f4caea5e0749d7.tar.gz rails-f77a6be8d23f048ced4fac54f1f4caea5e0749d7.tar.bz2 rails-f77a6be8d23f048ced4fac54f1f4caea5e0749d7.zip | |
Small grammar fix
Add comma and change verb.
[ci skip]
| -rw-r--r-- | guides/source/action_controller_overview.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/action_controller_overview.md b/guides/source/action_controller_overview.md index a43a69b7a3..5d987264f5 100644 --- a/guides/source/action_controller_overview.md +++ b/guides/source/action_controller_overview.md @@ -719,7 +719,7 @@ Now, the `LoginsController`'s `new` and `create` actions will work as before wit In addition to "before" filters, you can also run filters after an action has been executed, or both before and after. -"after" filters are similar to "before" filters, but because the action has already been run they have access to the response data that's about to be sent to the client. Obviously, "after" filters cannot stop the action from running. Please note that "after" filters are executed only after a successful action but not when an exception was raised in the request cycle. +"after" filters are similar to "before" filters, but because the action has already been run they have access to the response data that's about to be sent to the client. Obviously, "after" filters cannot stop the action from running. Please note that "after" filters are executed only after a successful action, but not when an exception is raised in the request cycle. "around" filters are responsible for running their associated actions by yielding, similar to how Rack middlewares work. |