aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorvanderhoop <vanderhoop@me.com>2014-05-06 19:46:55 -0400
committerArthur Neves <arthurnn@gmail.com>2014-05-07 09:11:59 -0400
commitb345fc25119fbeadaf0047ebd59f2f59af7deb16 (patch)
tree2a9967f304119894745c136a680b26fba5f6982f /guides
parent350e3d7d2aed1e5a95db519dcbeecae0f536a5d8 (diff)
downloadrails-b345fc25119fbeadaf0047ebd59f2f59af7deb16.tar.gz
rails-b345fc25119fbeadaf0047ebd59f2f59af7deb16.tar.bz2
rails-b345fc25119fbeadaf0047ebd59f2f59af7deb16.zip
fixed typos in active_record basics [skip ci]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/active_record_basics.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/active_record_basics.md b/guides/source/active_record_basics.md
index a184f0753d..e815f6b674 100644
--- a/guides/source/active_record_basics.md
+++ b/guides/source/active_record_basics.md
@@ -309,10 +309,10 @@ into the database. There are several methods that you can use to check your
models and validate that an attribute value is not empty, is unique and not
already in the database, follows a specific format and many more.
-Validation is a very important issue to consider when persisting to database, so
+Validation is a very important issue to consider when persisting to the database, so
the methods `create`, `save` and `update` take it into account when
running: they return `false` when validation fails and they didn't actually
-perform any operation on database. All of these have a bang counterpart (that
+perform any operation on the database. All of these have a bang counterpart (that
is, `create!`, `save!` and `update!`), which are stricter in that
they raise the exception `ActiveRecord::RecordInvalid` if validation fails.
A quick example to illustrate: