aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/actioncontroller/introduction.txt
diff options
context:
space:
mode:
authorPratik Naik <pratiknaik@gmail.com>2008-10-16 22:13:06 +0200
committerPratik Naik <pratiknaik@gmail.com>2008-10-16 22:13:06 +0200
commit9cb5400871b660e2c6d1654346650f07bb52a0c0 (patch)
tree6cd292650cf80b25494cf2f800318f337517b732 /railties/doc/guides/actioncontroller/introduction.txt
parent517bc500ed95a84fd2aadff34fdc14cb7965bc6b (diff)
downloadrails-9cb5400871b660e2c6d1654346650f07bb52a0c0.tar.gz
rails-9cb5400871b660e2c6d1654346650f07bb52a0c0.tar.bz2
rails-9cb5400871b660e2c6d1654346650f07bb52a0c0.zip
Merge docrails
Diffstat (limited to 'railties/doc/guides/actioncontroller/introduction.txt')
-rw-r--r--railties/doc/guides/actioncontroller/introduction.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/doc/guides/actioncontroller/introduction.txt b/railties/doc/guides/actioncontroller/introduction.txt
index 35540bbc09..e4b0953b95 100644
--- a/railties/doc/guides/actioncontroller/introduction.txt
+++ b/railties/doc/guides/actioncontroller/introduction.txt
@@ -2,6 +2,6 @@
Action Controller is the C in MVC. After routing has determined which controller to use for a request, your controller is responsible for making sense of the request and producing the appropriate output. Luckily, Action Controller does most of the groundwork for you and uses smart conventions to make this as straight-forward as possible.
-For most conventional RESTful applications, the controller will receive the request (this is invisible to the developer), fetch or save data from a model and use a view to create HTML output. If your controller needs to do things a little differently, that's not a problem, this is just the most common way for a controller to work.
+For most conventional RESTful applications, the controller will receive the request (this is invisible to you as the developer), fetch or save data from a model and use a view to create HTML output. If your controller needs to do things a little differently, that's not a problem, this is just the most common way for a controller to work.
A controller can thus be thought of as a middle man between models and views. It makes the model data available to the view so it can display it to the user, and it saves or updates data from the user to the model.