[1.9.x] Corrected use of 'affect' vs 'effect' in docs.

Backport of 021782d22b80ea57fdd5e040add58adeafaedc55 from master

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt
index e80630c768..3ba1a4efef 100644
--- a/docs/ref/migration-operations.txt
+++ b/docs/ref/migration-operations.txt
@@ -152,7 +152,7 @@ The ``preserve_default`` argument indicates whether the field's default
 value is permanent and should be baked into the project state (``True``),
 or if it is temporary and just for this migration (``False``) - usually
 because the migration is adding a non-nullable field to a table and needs
-a default value to put into existing rows. It does not effect the behavior
+a default value to put into existing rows. It does not affect the behavior
 of setting defaults in the database directly - Django never sets database
 defaults and always applies them in the Django ORM code.
 
@@ -180,7 +180,7 @@ The ``preserve_default`` argument indicates whether the field's default
 value is permanent and should be baked into the project state (``True``),
 or if it is temporary and just for this migration (``False``) - usually
 because the migration is altering a nullable field to a non-nullable one and
-needs a default value to put into existing rows. It does not effect the
+needs a default value to put into existing rows. It does not affect the
 behavior of setting defaults in the database directly - Django never sets
 database defaults and always applies them in the Django ORM code.