diff options
| author | Mike Howard <mike@clove.com> | 2011-07-24 10:54:19 -0600 |
|---|---|---|
| committer | Mike Howard <mike@clove.com> | 2011-07-24 10:54:19 -0600 |
| commit | 25850d17ac670e754945fd39dd024c539e05ee04 (patch) | |
| tree | 9a29ce7f998a7a4d2af0b9e3e03c3fb3e0dab5c4 | |
| parent | 3665ffda8352af841b17565eb59d20da5edb2147 (diff) | |
| download | rails-25850d17ac670e754945fd39dd024c539e05ee04.tar.gz rails-25850d17ac670e754945fd39dd024c539e05ee04.tar.bz2 rails-25850d17ac670e754945fd39dd024c539e05ee04.zip | |
Changed wording of paragraph 2.1.1 Models to clarify table/model
relationship.
changed wording 'one table ... corresponds to one model' to 'each table
...'
| -rw-r--r-- | railties/guides/source/getting_started.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/getting_started.textile b/railties/guides/source/getting_started.textile index 6aca5d3420..60cd0217ad 100644 --- a/railties/guides/source/getting_started.textile +++ b/railties/guides/source/getting_started.textile @@ -50,7 +50,7 @@ At the core of Rails is the Model, View, Controller architecture, usually just c h5. Models -A model represents the information (data) of the application and the rules to manipulate that data. In the case of Rails, models are primarily used for managing the rules of interaction with a corresponding database table. In most cases, one table in your database will correspond to one model in your application. The bulk of your application's business logic will be concentrated in the models. +A model represents the information (data) of the application and the rules to manipulate that data. In the case of Rails, models are primarily used for managing the rules of interaction with a corresponding database table. In most cases, each table in your database will correspond to one model in your application. The bulk of your application's business logic will be concentrated in the models. h5. Views |