Improved style of n-tuple wording in docs and comments.

2 files changed, 2 insertions, 2 deletions

diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index d96f489b81..e1575e61b2 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -227,7 +227,7 @@ modifications:
   concrete data type. Django supports adding an extra string value to the end
   of this tuple to be used as the human-readable name, or ``label``. The
   ``label`` can be a lazy translatable string. Thus, in most cases, the member
-  value will be a ``(value, label)`` two-tuple. See below for :ref:`an example
+  value will be a ``(value, label)`` 2-tuple. See below for :ref:`an example
   of subclassing choices <field-choices-enum-subclassing>` using a more complex
   data type. If a tuple is not provided, or the last item is not a (lazy)
   string, the ``label`` is :ref:`automatically generated
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 640818d2a5..cf3cb5c415 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -765,7 +765,7 @@ first item is the first field, etc. For example:
 
 If you only pass in a single field, you can also pass in the ``flat``
 parameter. If ``True``, this will mean the returned results are single values,
-rather than one-tuples. An example should make the difference clearer:
+rather than 1-tuples. An example should make the difference clearer:
 
 .. code-block:: pycon