diff options
| author | Jaime Iniesta <jaimeiniesta@gmail.com> | 2010-08-26 09:55:26 +0200 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2010-08-26 14:23:58 +0200 |
| commit | 5430f5bd06ba71a11479bc83eda38e0d7302ecea (patch) | |
| tree | 1108e2cd8c5c1eaa172c00497bc8e6f8a65ce4e0 /activerecord/lib/active_record/callbacks.rb | |
| parent | d9f6e1693751b619cd2dffe4ca202bd5f493c90c (diff) | |
| download | rails-5430f5bd06ba71a11479bc83eda38e0d7302ecea.tar.gz rails-5430f5bd06ba71a11479bc83eda38e0d7302ecea.tar.bz2 rails-5430f5bd06ba71a11479bc83eda38e0d7302ecea.zip | |
lifecycle should be two words, life cycle
Diffstat (limited to 'activerecord/lib/active_record/callbacks.rb')
| -rw-r--r-- | activerecord/lib/active_record/callbacks.rb | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/activerecord/lib/active_record/callbacks.rb b/activerecord/lib/active_record/callbacks.rb index a31973d529..fd71d7db4e 100644 --- a/activerecord/lib/active_record/callbacks.rb +++ b/activerecord/lib/active_record/callbacks.rb @@ -3,7 +3,7 @@ require 'active_support/core_ext/array/wrap' module ActiveRecord # = Active Record Callbacks # - # Callbacks are hooks into the lifecycle of an Active Record object that allow you to trigger logic + # Callbacks are hooks into the life cycle of an Active Record object that allow you to trigger logic # before or after an alteration of the object state. This can be used to make sure that associated and # dependent objects are deleted when +destroy+ is called (by overwriting +before_destroy+) or to massage attributes # before they're validated (by overwriting +before_validation+). As an example of the callbacks initiated, consider @@ -26,7 +26,7 @@ module ActiveRecord # <tt>after_rollback</tt>. # # That's a total of ten callbacks, which gives you immense power to react and prepare for each state in the - # Active Record lifecycle. The sequence for calling <tt>Base#save</tt> for an existing record is similar, + # Active Record life cycle. The sequence for calling <tt>Base#save</tt> for an existing record is similar, # except that each <tt>_on_create</tt> callback is replaced by the corresponding <tt>_on_update</tt> callback. # # Examples: |