From 47d95c8c3cf48005a91c5fa258ca792e70391069 Mon Sep 17 00:00:00 2001
From: 1334 <1334@shadowproject.net>
Date: Mon, 3 Dec 2012 14:01:27 +0100
Subject: fix some formatting

---
 guides/source/migrations.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'guides/source')

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
-- 
cgit v1.2.3