diff options
| author | Jonathan Roes <jroes@jroes.net> | 2013-04-03 10:55:46 -0300 |
|---|---|---|
| committer | Jonathan Roes <jroes@jroes.net> | 2013-04-03 10:55:46 -0300 |
| commit | bf8f9c8ee28af808902c8e3da73ccb8d8fbb4cf1 (patch) | |
| tree | 3e4bb71d945d60dac5204d9be80545b95bb76d48 /guides | |
| parent | a3bb1385b07a5816d4882b32a84787ee1ab78746 (diff) | |
| download | rails-bf8f9c8ee28af808902c8e3da73ccb8d8fbb4cf1.tar.gz rails-bf8f9c8ee28af808902c8e3da73ccb8d8fbb4cf1.tar.bz2 rails-bf8f9c8ee28af808902c8e3da73ccb8d8fbb4cf1.zip | |
Typos/grammar fixes
Diffstat (limited to 'guides')
| -rw-r--r-- | guides/source/action_controller_overview.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/guides/source/action_controller_overview.md b/guides/source/action_controller_overview.md index f197591592..db91425c76 100644 --- a/guides/source/action_controller_overview.md +++ b/guides/source/action_controller_overview.md @@ -30,11 +30,11 @@ NOTE: For more details on the routing process, see [Rails Routing from the Outsi Controller Naming Convention ---------------------------- -The naming convention of controllers in Rails favors pluralization of the last word in the controller's name, although it is not strictly required (e.g. `ApplicationController`). For example, `ClientsController` is preferable to `ClientController`, `SiteAdminsController` is preferable to `SiteAdminController` or `SitesAdminsController`, and so on. +The naming convention of controllers in Rails favors pluralization of the last word in the controller's name, although it is not strictly required (e.g. `ApplicationController`). For example, `ClientsController` is preferable to `ClientController`, `SiteAdminsController` is preferable to `SiteAdminController` or `SitesAdminsController`, and so on. -Following this convention will allow you to use default route generators (e.g. `resources`, etc) without needing to qualify each `:path` or `:controller`, and keeps URL and path helpers' usage consistent throughout your applciation. See [Layouts & Rendering Guide](layouts_and_rendering.html) for more details. +Following this convention will allow you to use the default route generators (e.g. `resources`, etc) without needing to qualify each `:path` or `:controller`, and keeps URL and path helpers' usage consistent throughout your application. See [Layouts & Rendering Guide](layouts_and_rendering.html) for more details. -NOTE: Controller naming convention differs from the naming convention of Models, which prefer a singular naming convention. +NOTE: The controller naming convention differs from the naming convention of models, which expected to be named in singular form. Methods and Actions |