aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_basics.md
diff options
context:
space:
mode:
authorDaniel Castro <castrodd@gmail.com>2017-07-09 12:15:56 -0400
committerGitHub <noreply@github.com>2017-07-09 12:15:56 -0400
commit4f7b7c987966ef5f5963ce0f9ac1e67f0a78c987 (patch)
tree90c0d3f2207c820e55af163390701363ca23913a /guides/source/active_record_basics.md
parentb362ce6d544a1dcaef08eaf2c685f8495f94c51c (diff)
downloadrails-4f7b7c987966ef5f5963ce0f9ac1e67f0a78c987.tar.gz
rails-4f7b7c987966ef5f5963ce0f9ac1e67f0a78c987.tar.bz2
rails-4f7b7c987966ef5f5963ce0f9ac1e67f0a78c987.zip
[ci skip] Updated language on validations.
Diffstat (limited to 'guides/source/active_record_basics.md')
-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 6b3aa471f9..2ac80d8f89 100644
--- a/guides/source/active_record_basics.md
+++ b/guides/source/active_record_basics.md
@@ -314,8 +314,8 @@ already in the database, follows a specific format and many more.
Validation is a very important issue to consider when persisting to the database, so
the methods `save` and `update` take it into account when
-running: they return `false` when validation fails and they didn't actually
-perform any operation on the database. All of these have a bang counterpart (that
+running: they return `false` when validation fails and they don't actually
+perform any operations on the database. All of these have a bang counterpart (that
is, `save!` and `update!`), which are stricter in that
they raise the exception `ActiveRecord::RecordInvalid` if validation fails.
A quick example to illustrate: