Fixed #31342 -- Clarified base manager docs.ticket-31342

1 files changed, 7 insertions, 5 deletions

diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt
index 473965d897..117386ab4a 100644
--- a/docs/topics/db/managers.txt
+++ b/docs/topics/db/managers.txt
@@ -214,11 +214,13 @@ appropriate for your circumstances, you can tell Django which class to use by
 setting :attr:`Meta.base_manager_name
 <django.db.models.Options.base_manager_name>`.
 
-Base managers aren't used when querying on related models. For example, if the
-``Question`` model :ref:`from the tutorial <creating-models>` had a ``deleted``
-field and a base manager that filters out instances with ``deleted=True``, a
-queryset like ``Choice.objects.filter(question__name__startswith='What')``
-would include choices related to deleted questions.
+Base managers aren't used when querying on related models, or when
+:ref:`accessing a to-many relationship <backwards-related-objects>`. For
+example, if the ``Question`` model :ref:`from the tutorial <creating-models>`
+had a ``deleted`` field and a base manager that filters out instances with
+``deleted=True``, a queryset like
+``Choice.objects.filter(question__name__startswith='What')`` would include
+choices related to deleted questions.
 
 Don't filter away any results in this type of manager subclass
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~