summaryrefslogtreecommitdiff
path: root/docs/ref/models
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/ref/models
parent25352dc019d175dfa6e62a50de76cb3614955077 (diff)
Preferred usage of among/while to amongst/whilst.
Diffstat (limited to 'docs/ref/models')
-rw-r--r--docs/ref/models/querysets.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 2e862dbbb7..01ba71c182 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1710,7 +1710,7 @@ to refer to the queryset's model.
On PostgreSQL only, you can pass ``no_key=True`` in order to acquire a weaker
lock, that still allows creating rows that merely reference locked rows
-(through a foreign key, for example) whilst the lock is in place. The
+(through a foreign key, for example) while the lock is in place. The
PostgreSQL documentation has more details about `row-level lock modes
<https://www.postgresql.org/docs/current/explicit-locking.html#LOCKING-ROWS>`_.