[1.9.x] Added missing step to transitioning squashed migrations.

Backport of d8b651a544696e586bcc941335420ff9b7bf4fb5 from master

1 files changed, 6 insertions, 5 deletions

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index a202676aea..c197c5556f 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -626,12 +626,13 @@ migrations it replaces and distribute this change to all running instances
 of your application, making sure that they run ``migrate`` to store the change
 in their database.
 
-After this has been done, you must then transition the squashed migration to
-a normal initial migration, by:
+You must then transition the squashed migration to a normal migration by:
 
-- Deleting all the migration files it replaces
-- Removing the ``replaces`` argument in the ``Migration`` class of the
-  squashed migration (this is how Django tells that it is a squashed migration)
+- Deleting all the migration files it replaces.
+- Updating all migrations that depend on the deleted migrations to depend on
+  the squashed migration instead.
+- Removing the ``replaces`` attribute in the ``Migration`` class of the
+  squashed migration (this is how Django tells that it is a squashed migration).
 
 .. note::
     Once you've squashed a migration, you should not then re-squash that squashed