diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index ec462ea..23838aa 100644
|
a
|
b
|
They will, however, have the same fields, relationships and ``Meta`` options
|
| 331 | 331 | when you access them in migrations, and you will NOT have any custom |
| 332 | 332 | constructors or instance methods. Plan appropriately! |
| 333 | 333 | |
| | 334 | References to functions in field options such as ``upload_to`` and |
| | 335 | ``limit_choices_to`` are serialized in migrations, so the functions will need |
| | 336 | to be kept around for as long as there is a migration referencing them. |
| | 337 | |
| 334 | 338 | In addition, the base classes of the model are just stored as pointers, |
| 335 | 339 | so you must always keep base classes around for as long as there is a migration |
| 336 | 340 | that contains a reference to them. On the plus side, methods and managers |