[6.0.x] Fixed #37039 -- Removed outdated note from QuerySet.iterator() docs.

MANAS225 · jacobtylerwalls · commit 990ab01e70fd · 2026-05-04T14:30:55.000-04:00
Backport of 7e7e969 from main.
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
@@ -2622,9 +2622,8 @@ if you call its asynchronous version ``aiterator``.
 
 A ``QuerySet`` typically caches its results internally so that repeated
 evaluations do not result in additional queries. In contrast, ``iterator()``
-will read results directly, without doing any caching at the ``QuerySet`` level
-(internally, the default iterator calls ``iterator()`` and caches the return
-value). For a ``QuerySet`` which returns a large number of objects that you
+will read results directly, without doing any caching at the ``QuerySet``
+level. For a ``QuerySet`` which returns a large number of objects that you
 only need to access once, this can result in better performance and a
 significant reduction in memory.
 
