aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorschneems <richard.schneeman@gmail.com>2012-10-01 20:54:48 -0400
committerschneems <richard.schneeman@gmail.com>2012-10-02 11:31:24 -0400
commitae4448253d5b710bd754d7a6dc1dbd7391c832be (patch)
tree79bee38bd87be1bd17c832f1e7a7504394d37d6d
parenteb853940d1aa5c92359b8d9fbc79142a03e9d238 (diff)
downloadrails-ae4448253d5b710bd754d7a6dc1dbd7391c832be.tar.gz
rails-ae4448253d5b710bd754d7a6dc1dbd7391c832be.tar.bz2
rails-ae4448253d5b710bd754d7a6dc1dbd7391c832be.zip
improve wording over `change` method docs
The feature is available after Rails 3.1 and this is no longer a "new" feature.
-rw-r--r--guides/source/migrations.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index 2d633175d1..6f9b435c5c 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -85,7 +85,7 @@ existing users.
### Using the change method
-Rails 3.1 makes migrations smarter by providing a new `change` method.
+Rails 3.1 and up makes migrations smarter by providing a `change` method.
This method is preferred for writing constructive migrations (adding columns or
tables). The migration knows how to migrate your database and reverse it when
the migration is rolled back without the need to write a separate `down` method.