Fixed #23597 -- Clarified the manager that {Single,Multiple}ObjectMixin.model uses.

docs/ref/class-based-views/mixins-multiple-object.txt

@@ -56,7 +56,8 @@ MultipleObjectMixin
 
         The model that this view will display data for. Specifying ``model
         = Foo`` is effectively the same as specifying ``queryset =
-        Foo.objects.all()``.
+        Foo.objects.all()``, where ``objects`` stands for ``Foo``’s
+        :ref:`default manager <default-managers>`.
 
     .. attribute:: queryset
 

docs/ref/class-based-views/mixins-single-object.txt

@@ -16,7 +16,8 @@ SingleObjectMixin
 
         The model that this view will display data for. Specifying ``model
         = Foo`` is effectively the same as specifying ``queryset =
-        Foo.objects.all()``.
+        Foo.objects.all()``, where ``objects`` stands for ``Foo``’s
+        :ref:`default manager <default-managers>`.
 
     .. attribute:: queryset
 

docs/topics/db/managers.txt

@@ -169,6 +169,11 @@ For example::
 This example allows you to request ``Person.authors.all()``, ``Person.editors.all()``,
 and ``Person.people.all()``, yielding predictable results.
 
+.. _default-managers:
+
+Default managers
+~~~~~~~~~~~~~~~~
+
 If you use custom ``Manager`` objects, take note that the first ``Manager``
 Django encounters (in the order in which they're defined in the model) has a
 special status. Django interprets the first ``Manager`` defined in a class as