From dea3eefa728df4c3919e7d5115af351ba28c6e7f Mon Sep 17 00:00:00 2001
From: bahoo <jon.c.culver@gmail.com>
Date: Mon, 27 Oct 2014 14:16:39 -0700
Subject: [PATCH] [1.7.x] Fixed typo in squashing migrations documentation

Backport of af7d66b4f2 from master
---
 docs/topics/migrations.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index dd5f5e7d1f..c43b256eff 100755
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -459,7 +459,7 @@ Once the operation sequence has been reduced as much as possible - the amount
 possible depends on how closely intertwined your models are and if you have
 any :class:`~django.db.migrations.operations.RunSQL`
 or :class:`~django.db.migrations.operations.RunPython` operations (which can't
-be optimized through) - Django will them write it back out into a new set of
+be optimized through) - Django will then write it back out into a new set of
 initial migration files.
 
 These files are marked to say they replace the previously-squashed migrations,