summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorDavid Smith <smithdc@gmail.com>2020-05-25 17:05:22 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2020-06-03 21:02:48 +0200
commitdbdc192ca30b70a9f22c6bc4b3155bbccd01c323 (patch)
treebb8ddf9934dcf6ba05b9dd8e081a76f02f162a36 /docs/howto
parent25352dc019d175dfa6e62a50de76cb3614955077 (diff)
Preferred usage of among/while to amongst/whilst.
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/writing-migrations.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/howto/writing-migrations.txt b/docs/howto/writing-migrations.txt
index ab1a897aa0..00dc0dfadf 100644
--- a/docs/howto/writing-migrations.txt
+++ b/docs/howto/writing-migrations.txt
@@ -327,7 +327,7 @@ If you change a :class:`~django.db.models.ManyToManyField` to use a ``through``
model, the default migration will delete the existing table and create a new
one, losing the existing relations. To avoid this, you can use
:class:`.SeparateDatabaseAndState` to rename the existing table to the new
-table name whilst telling the migration autodetector that the new model has
+table name while telling the migration autodetector that the new model has
been created. You can check the existing table name through
:djadmin:`sqlmigrate` or :djadmin:`dbshell`. You can check the new table name
with the through model's ``_meta.db_table`` property. Your new ``through``