[3.0.x] Fixed #30955 -- Doc'd that only concrete base models are stored in historical models bases.

Abstract models are removed from bases when generating historical model
state since 6436f1fad9ce51f18735106ac75aeea3d6d1f310.
Backport of 8058d9d7adb189fec75a4b57565f225996c7b22c from master

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index f0daf9e8a3..36f0de1391 100644
--- a/docs/topics/migrations.txt
+++ b/docs/topics/migrations.txt
@@ -412,11 +412,11 @@ classes will need to be kept around for as long as there is a migration
 referencing them. Any :doc:`custom model fields </howto/custom-model-fields>`
 will also need to be kept, since these are imported directly by migrations.
 
-In addition, the base classes of the model are stored as pointers, so you must
-always keep base classes around for as long as there is a migration that
-contains a reference to them. On the plus side, methods and managers from these
-base classes inherit normally, so if you absolutely need access to these you
-can opt to move them into a superclass.
+In addition, the concrete base classes of the model are stored as pointers, so
+you must always keep base classes around for as long as there is a migration
+that contains a reference to them. On the plus side, methods and managers from
+these base classes inherit normally, so if you absolutely need access to these
+you can opt to move them into a superclass.
 
 To remove old references, you can :ref:`squash migrations <migration-squashing>`
 or, if there aren't many references, copy them into the migration files.