Fix formatting on migrations guide

1 files changed, 8 insertions, 7 deletions

diff --git a/guides/source/migrations.md b/guides/source/migrations.md
index 67538b85e8..657e872cd0 100644
--- a/guides/source/migrations.md
+++ b/guides/source/migrations.md
@@ -332,7 +332,7 @@ end
 
 As always, what has been generated for you is just a starting point. You can add
 or remove from it as you see fit by editing the
-@db/migrate/YYYYMMDDHHMMSS_add_details_to_products.rb@ file.
+`db/migrate/YYYYMMDDHHMMSS_add_details_to_products.rb` file.
 
 NOTE: The generated migration file for destructive migrations will still be
 old-style using the `up` and `down` methods. This is because Rails needs to know
@@ -957,12 +957,13 @@ this, then you should set the schema format to `:sql`.
 Instead of using Active Record's schema dumper, the database's structure will be
 dumped using a tool specific to the database (via the `db:structure:dump` Rake task)
 into `db/structure.sql`. For example, for the PostgreSQL RDBMS, the
-`pg_dump` utility is used. For MySQL, this file will contain the output of `SHOW
-CREATE TABLE` for the various tables. Loading these schemas is simply a question
-of executing the SQL statements they contain. By definition, this will create a
-perfect copy of the database's structure. Using the `:sql` schema format will,
-however, prevent loading the schema into a RDBMS other than the one used to
-create it.
+`pg_dump` utility is used. For MySQL, this file will contain the output of 
+`SHOW CREATE TABLE` for the various tables.
+
+Loading these schemas is simply a question of executing the SQL statements they 
+contain. By definition, this will create a perfect copy of the database's 
+structure. Using the `:sql` schema format will, however, prevent loading the 
+schema into a RDBMS other than the one used to create it.
 
 ### Schema Dumps and Source Control