aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
authorKasper Timm Hansen <kaspth@gmail.com>2017-07-09 18:27:44 +0200
committerGitHub <noreply@github.com>2017-07-09 18:27:44 +0200
commit0b6309d6bc9712c06fdc42dda8ae8bd695401b7c (patch)
tree7307cca54791721861c93aa50f67e15310a0da0f /guides/source
parent85d154f05214c113c4afd218f5d51df7d9dae144 (diff)
parent4f7b7c987966ef5f5963ce0f9ac1e67f0a78c987 (diff)
downloadrails-0b6309d6bc9712c06fdc42dda8ae8bd695401b7c.tar.gz
rails-0b6309d6bc9712c06fdc42dda8ae8bd695401b7c.tar.bz2
rails-0b6309d6bc9712c06fdc42dda8ae8bd695401b7c.zip
Merge pull request #29731 from castrodd/patch-1
[ci skip] Updated language on validations.
Diffstat (limited to 'guides/source')
-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: