Refs #23919 -- Removed docs references to long integers.

2 files changed, 1 insertions, 6 deletions

diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
index 2008e65b95..b135532b2d 100644
--- a/docs/ref/forms/fields.txt
+++ b/docs/ref/forms/fields.txt
@@ -722,7 +722,7 @@ For each field, we describe the default widget used if you don't specify
     * Default widget: :class:`NumberInput` when :attr:`Field.localize` is
       ``False``, else :class:`TextInput`.
     * Empty value: ``None``
-    * Normalizes to: A Python integer or long integer.
+    * Normalizes to: A Python integer.
     * Validates that the given value is an integer. Leading and trailing
       whitespace is allowed, as in Python's ``int()`` function.
     * Error message keys: ``required``, ``invalid``, ``max_value``,
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 18e81a7da8..2893c91b8e 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1974,11 +1974,6 @@ should always use ``count()`` rather than loading all of the record into Python
 objects and calling ``len()`` on the result (unless you need to load the
 objects into memory anyway, in which case ``len()`` will be faster).
 
-Depending on which database you're using (e.g. PostgreSQL vs. MySQL),
-``count()`` may return a long integer instead of a normal Python integer. This
-is an underlying implementation quirk that shouldn't pose any real-world
-problems.
-
 Note that if you want the number of items in a ``QuerySet`` and are also
 retrieving model instances from it (for example, by iterating over it), it's
 probably more efficient to use ``len(queryset)`` which won't cause an extra