aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source
diff options
context:
space:
mode:
authorFrancesco Rodriguez <lrodriguezsanc@gmail.com>2012-05-28 23:41:49 -0500
committerFrancesco Rodriguez <lrodriguezsanc@gmail.com>2012-05-28 23:41:49 -0500
commit34f82abf017a152bace9cbb12b69ef2076b6d67d (patch)
treed9849dc2b9a98430af25197f19a9720810acfba7 /guides/source
parent2c4da97b19b04fae00b024d9fdc111a866f7e445 (diff)
downloadrails-34f82abf017a152bace9cbb12b69ef2076b6d67d.tar.gz
rails-34f82abf017a152bace9cbb12b69ef2076b6d67d.tar.bz2
rails-34f82abf017a152bace9cbb12b69ef2076b6d67d.zip
fix typos on migrations guide [ci skip]
Diffstat (limited to 'guides/source')
-rw-r--r--guides/source/migrations.textile8
1 files changed, 4 insertions, 4 deletions
diff --git a/guides/source/migrations.textile b/guides/source/migrations.textile
index 909815d6d7..248afbfb93 100644
--- a/guides/source/migrations.textile
+++ b/guides/source/migrations.textile
@@ -8,12 +8,12 @@ production machines next time you deploy.
Active Record tracks which migrations have already been run so all you have to
do is update your source and run +rake db:migrate+. Active Record will work out
-which migrations should be run by checking the hidden +schema_mirgrations+ database
+which migrations should be run by checking the hidden +schema_migrations+ database
table, which is created automatically after the initial invocaton of +rake db:migrate+.
-+schema_migrations+ contains a sole column named +versions+ that holds the time
-stamps that are preappended to generated Active Record migrations. Each time stamp
++schema_migrations+ contains a sole column named +versions+ that holds the timestamps
+that are preappended to generated Active Record migrations. Each timestamp
contained in +schema_migrations+ indicate that the migration associated with the
-time stamp has previously been invoked, and does not need to be run on future
+timestamp has previously been invoked, and does not need to be run on future
+rake db:migrate+ invocations. Active Record will also update your +db/schema.rb+
file to match the up-to-date structure of your database.