aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/migrations.md
diff options
context:
space:
mode:
authorJuanito Fatas <katehuang0320@gmail.com>2013-09-17 00:33:14 +0800
committerJuanito Fatas <katehuang0320@gmail.com>2013-09-17 00:33:14 +0800
commit39a454d8a042bd2ced8dc659324fc51779a45ab9 (patch)
tree34aca53c822a336989bff20230e540679a5dcf56 /guides/source/migrations.md
parent678fdda54f391a7fec92e2c0d2a94b6e889c220c (diff)
downloadrails-39a454d8a042bd2ced8dc659324fc51779a45ab9.tar.gz
rails-39a454d8a042bd2ced8dc659324fc51779a45ab9.tar.bz2
rails-39a454d8a042bd2ced8dc659324fc51779a45ab9.zip
[ci skip] Improve readability of 4.3's NOTE in migration.md.
Diffstat (limited to 'guides/source/migrations.md')
-rw-r--r--guides/source/migrations.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index ab39b39a1c..3c512e0390 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -703,9 +703,9 @@ The `rake db:reset` task will drop the database and set it up again. This is
functionally equivalent to `rake db:drop db:setup`.
NOTE: This is not the same as running all the migrations. It will only use the
-contents of the current schema.rb file. If a migration can't be rolled back,
-'rake db:reset' may not help you. To find out more about dumping the schema see
-'[schema dumping and you](#schema-dumping-and-you).'
+contents of the current `schema.rb` file. If a migration can't be rolled back,
+`rake db:reset` may not help you. To find out more about dumping the schema see
+[Schema Dumping and You](#schema-dumping-and-you) section.
### Running Specific Migrations