Ticket #12678: 12678.diff

docs/topics/db/models.txt

@@ -1081 +1081 @@
 Now normal ``User`` queries will be unorderd and ``OrderedUser`` queries will
 be ordered by ``username``.
 
-Querysets still return the model that was requested
+QuerySets still return the model that was requested
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 There is no way to have Django return, say, a ``MyUser`` object whenever you

docs/topics/db/aggregation.txt

@@ -96 +96 @@
 =================================================
 
 The second way to generate summary values is to generate an independent
-summary for each object in a ``Queryset``. For example, if you are retrieving
+summary for each object in a ``QuerySet``. For example, if you are retrieving
 a list of books, you may want to know how many authors contributed to
 each book. Each Book has a many-to-many relationship with the Author; we
 want to summarize this relationship for each book in the ``QuerySet``.
@@ -257 +257 @@
 
 Ordinarily, annotations are generated on a per-object basis - an annotated
 ``QuerySet`` will return one result for each object in the original
-``Queryset``. However, when a ``values()`` clause is used to constrain the
+``QuerySet``. However, when a ``values()`` clause is used to constrain the
 columns that are returned in the result set, the method for evaluating
 annotations is slightly different. Instead of returning an annotated result
 for each result in the original ``QuerySet``, the original results are

docs/ref/models/querysets.txt

@@ -92 +92 @@
 than the results that are currently in the database.
 
 If you only want to pickle the necessary information to recreate the
-``Queryset`` from the database at a later time, pickle the ``query`` attribute
+``QuerySet`` from the database at a later time, pickle the ``query`` attribute
 of the ``QuerySet``. You can then recreate the original ``QuerySet`` (without
 any results loaded) using some code like this::