From 7b394b9988b986429a4da4e60416e0f08ff649e5 Mon Sep 17 00:00:00 2001
From: dbogar89 <162604156+dbogar89@users.noreply.github.com>
Date: Sun, 27 Apr 2025 07:40:14 +0100
Subject: [PATCH] Fixed #36335 -- Fixed typo in docs/topics/db/managers.txt.

---
 docs/topics/db/managers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/topics/db/managers.txt b/docs/topics/db/managers.txt
index 3a7a635e49..1cd3ba962f 100644
--- a/docs/topics/db/managers.txt
+++ b/docs/topics/db/managers.txt
@@ -197,7 +197,7 @@ Using managers for related object access
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 By default, Django uses an instance of the ``Model._base_manager`` manager
-class when accessing related objects (i.e. ``choice.question``), not the
+class when accessing related objects (e.g. ``choice.question``), not the
 ``_default_manager`` on the related object. This is because Django needs to be
 able to retrieve the related object, even if it would otherwise be filtered out
 (and hence be inaccessible) by the default manager.