aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorkishore-mohan <kishorevlrtn@gmail.com>2015-09-01 20:07:37 +0530
committerkishore-mohan <kishorevlrtn@gmail.com>2015-09-02 09:19:47 +0530
commitcf82b2e034cb99afde9c19babbb96276d3804c5b (patch)
treed81c3ca7255dfb79803caddaa91a70802a795d3d /guides
parentdc5cf37d7379e297196dbe542b958b1114ef840e (diff)
downloadrails-cf82b2e034cb99afde9c19babbb96276d3804c5b.tar.gz
rails-cf82b2e034cb99afde9c19babbb96276d3804c5b.tar.bz2
rails-cf82b2e034cb99afde9c19babbb96276d3804c5b.zip
typo "description not clear corrected with proper description and action_controller_overview file Rails' -> Rails" [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/action_controller_overview.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/action_controller_overview.md b/guides/source/action_controller_overview.md
index b4ca0df0de..19bdea2b8a 100644
--- a/guides/source/action_controller_overview.md
+++ b/guides/source/action_controller_overview.md
@@ -1114,7 +1114,7 @@ Rescue
Most likely your application is going to contain bugs or otherwise throw an exception that needs to be handled. For example, if the user follows a link to a resource that no longer exists in the database, Active Record will throw the `ActiveRecord::RecordNotFound` exception.
-Rails' default exception handling displays a "500 Server Error" message for all exceptions. If the request was made locally, a nice traceback and some added information gets displayed so you can figure out what went wrong and deal with it. If the request was remote Rails will just display a simple "500 Server Error" message to the user, or a "404 Not Found" if there was a routing error or a record could not be found. Sometimes you might want to customize how these errors are caught and how they're displayed to the user. There are several levels of exception handling available in a Rails application:
+Rails default exception handling displays a "500 Server Error" message for all exceptions. If the request was made locally, a nice traceback and some added information gets displayed so you can figure out what went wrong and deal with it. If the request was remote Rails will just display a simple "500 Server Error" message to the user, or a "404 Not Found" if there was a routing error or a record could not be found. Sometimes you might want to customize how these errors are caught and how they're displayed to the user. There are several levels of exception handling available in a Rails application:
### The Default 500 and 404 Templates