aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_migrations.md
diff options
context:
space:
mode:
authorTim Wade <hello@timjwade.com>2015-05-13 21:05:48 -0700
committerTim Wade <hello@timjwade.com>2015-05-13 21:05:48 -0700
commit4cebcaeb2fd394603ac112236da19e8f3876d658 (patch)
treed88b74f294fbe5a8fddd2fd6bcb838525f800487 /guides/source/active_record_migrations.md
parentc1104a91f620fe30b940532db7e4771f03cb283e (diff)
downloadrails-4cebcaeb2fd394603ac112236da19e8f3876d658.tar.gz
rails-4cebcaeb2fd394603ac112236da19e8f3876d658.tar.bz2
rails-4cebcaeb2fd394603ac112236da19e8f3876d658.zip
[ci skip] Improve phrasing in AR migrations docs.
* insert 'and' into a poorly formed sentence. * avoid using 'reverse' twice in the same sentence (which would indicate the opposite of what is meant)
Diffstat (limited to 'guides/source/active_record_migrations.md')
-rw-r--r--guides/source/active_record_migrations.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md
index 7a994cc5de..80b1bde1c7 100644
--- a/guides/source/active_record_migrations.md
+++ b/guides/source/active_record_migrations.md
@@ -554,7 +554,7 @@ or write the `up` and `down` methods instead of using the `change` method.
Complex migrations may require processing that Active Record doesn't know how
to reverse. You can use `reversible` to specify what to do when running a
-migration what else to do when reverting it. For example:
+migration and what else to do when reverting it. For example:
```ruby
class ExampleMigration < ActiveRecord::Migration
@@ -606,7 +606,7 @@ schema, and the `down` method of your migration should revert the
transformations done by the `up` method. In other words, the database schema
should be unchanged if you do an `up` followed by a `down`. For example, if you
create a table in the `up` method, you should drop it in the `down` method. It
-is wise to reverse the transformations in precisely the reverse order they were
+is wise to perform the transformations in precisely the reverse order they were
made in the `up` method. The example in the `reversible` section is equivalent to:
```ruby