aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/migrations/using_models_in_migrations.txt
diff options
context:
space:
mode:
Diffstat (limited to 'railties/doc/guides/migrations/using_models_in_migrations.txt')
-rw-r--r--railties/doc/guides/migrations/using_models_in_migrations.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/doc/guides/migrations/using_models_in_migrations.txt b/railties/doc/guides/migrations/using_models_in_migrations.txt
index 807664e666..eda216c50a 100644
--- a/railties/doc/guides/migrations/using_models_in_migrations.txt
+++ b/railties/doc/guides/migrations/using_models_in_migrations.txt
@@ -23,7 +23,7 @@ The migration has its own minimal copy of the `Product` model and no longer care
=== Dealing with changing models ===
-For performance reasons information about the columns a model has is cached. For example if you add a column to a table and then try and use the corresponding model to insert a new row it may try and use the old column information. You can force ActiveRecord to re-read the column information with the `reset_column_information` method, for example
+For performance reasons information about the columns a model has is cached. For example if you add a column to a table and then try and use the corresponding model to insert a new row it may try and use the old column information. You can force Active Record to re-read the column information with the `reset_column_information` method, for example
[source, ruby]
-------------------------