From fca2613ec444face807dc3aecf0d8b59acf30eae Mon Sep 17 00:00:00 2001
From: mhutchin <mike@mhutchinson.com>
Date: Fri, 7 Oct 2011 08:26:05 -0700
Subject: Correct formatting

---
 railties/guides/source/migrations.textile | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

(limited to 'railties/guides/source/migrations.textile')

diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile
index ec812f9e13..6ec4d7f70e 100644
--- a/railties/guides/source/migrations.textile
+++ b/railties/guides/source/migrations.textile
@@ -628,11 +628,7 @@ There is no need (and it is error prone) to deploy a new instance of an app by r
 
 For example, this is how the test database is created: the current development database is dumped (either to +db/schema.rb+ or +db/development.sql+) and then loaded into the test database.
 
-Schema files are also useful if you want a quick look at what attributes an Active Record object has. This information is not in the model's code and is
-frequently spread across several migrations, but is summed up in the schema
-file. The "annotate_models":http://github.com/ctran/annotate_models
-gem automatically adds and updates comments at the top of each model summarizing
-the schema if you desire that functionality.
+Schema files are also useful if you want a quick look at what attributes an Active Record object has. This information is not in the model's code and is frequently spread across several migrations, but is summed up in the schema file. The "annotate_models":http://github.com/ctran/annotate_models gem automatically adds and updates comments at the top of each model summarizing the schema if you desire that functionality.
 
 h4. Types of Schema Dumps
 
-- 
cgit v1.2.3

