Skip to content
Browse files

Corrections to Active Record Validations and Callbacks guide.

  • Loading branch information...
1 parent 463223c commit a44bbfc1c7edb044ed9f73c7365a3a4a30b8b3fc @htanata htanata committed Oct 5, 2011
Showing with 3 additions and 3 deletions.
  1. +3 −3 railties/guides/source/active_record_validations_callbacks.textile
View
6 railties/guides/source/active_record_validations_callbacks.textile
@@ -105,7 +105,7 @@ Person.create(:name => "John Doe").valid? # => true
Person.create(:name => nil).valid? # => false
</ruby>
-After Active Record performing validations, any errors found can be accessed through the +errors+ instance method, which returns a collection of errors. By definition an object is valid if this collection is empty after running validations.
+After Active Record has performed validations, any errors found can be accessed through the +errors+ instance method, which returns a collection of errors. By definition, an object is valid if this collection is empty after running validations.
Note that an object instantiated with +new+ will not report errors even if it's technically invalid, because validations are not run when using +new+.
@@ -812,7 +812,7 @@ Add this line in your Gemfile:
gem "dynamic_form"
</ruby>
-Now you will have access to the two help methods +error_messages+ and +error_messages_for+ in your view templates.
+Now you will have access to the two helper methods +error_messages+ and +error_messages_for+ in your view templates.
h4. +error_messages+ and +error_messages_for+
@@ -907,7 +907,7 @@ ActionView::Base.field_error_proc = Proc.new do |html_tag, instance|
end
</ruby>
-The result look like the following:
+The result looks like the following:
!images/validation_error_messages.png(Validation error messages)!

0 comments on commit a44bbfc

Please sign in to comment.
Something went wrong with that request. Please try again.