aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
author1334 <1334@shadowproject.net>2012-12-03 14:01:27 +0100
committer1334 <1334@shadowproject.net>2012-12-03 14:01:27 +0100
commit47d95c8c3cf48005a91c5fa258ca792e70391069 (patch)
tree404a7288b9547fdb337e3b1608847d42eebd5ac3 /guides/source
parentb0662108231f6d6a22e2be9ab2555706e481f327 (diff)
downloadrails-47d95c8c3cf48005a91c5fa258ca792e70391069.tar.gz
rails-47d95c8c3cf48005a91c5fa258ca792e70391069.tar.bz2
rails-47d95c8c3cf48005a91c5fa258ca792e70391069.zip
fix some formatting
Diffstat (limited to 'guides/source')
-rw-r--r--guides/source/migrations.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index 7b1ca9ea90..43aef85e8d 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -640,7 +640,7 @@ no such migrations, it exits. It will run these migrations in order based
on the date of the migration.
Note that running the `db:migrate` also invokes the `db:schema:dump` task, which
-will update your db/schema.rb file to match the structure of your database.
+will update your `db/schema.rb` file to match the structure of your database.
If you specify a target version, Active Record will run the required migrations
(up, down or change) until it has reached the specified version. The version
@@ -694,7 +694,7 @@ The `rake db:reset` task will drop the database, recreate it and load the
current schema into it.
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'
+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.rb](#schema-dumping-and-you).
### Running Specific Migrations