diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index c43b256..be8dd6e 100755
a
|
b
|
will be.
|
213 | 213 | |
214 | 214 | Be aware, however, that unmigrated apps cannot depend on migrated apps, by the |
215 | 215 | very nature of not having migrations. This means that it is not generally |
216 | | possible to have an unmigrated app have a ForeignKey or ManyToManyField to |
217 | | a migrated app; some cases may work, but it will eventually fail. |
| 216 | possible to have an unmigrated app have a ``ForeignKey`` or ``ManyToManyField`` |
| 217 | to a migrated app; some cases may work, but it will eventually fail. |
| 218 | |
| 219 | .. warning:: |
| 220 | |
| 221 | Even if things appear to work with unmigrated apps depending on migrated |
| 222 | apps, Django may not generate all the necessary foreign key constraints! |
218 | 223 | |
219 | 224 | This is particularly apparent if you use swappable models (e.g. |
220 | 225 | ``AUTH_USER_MODEL``), as every app that uses swappable models will need |