From 718ed69751c9b3923ffa99ce000e733c8350d0a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E3=81=84=E3=80=82?=
 <99417239+koupro0204@users.noreply.github.com>
Date: Tue, 7 May 2024 14:30:17 +0900
Subject: [PATCH] Fixed #35430 -- Corrected docs on timezone conversion in
 templates.

---
 docs/topics/i18n/timezones.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index c11bd03b09..0d866dac6c 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -9,7 +9,10 @@ Overview
 
 When support for time zones is enabled, Django stores datetime information in
 UTC in the database, uses time-zone-aware datetime objects internally, and
-translates them to the end user's time zone in templates and forms.
+converts them to the end user's time zone in forms. Templates will use the
+:ref:`default time zone <default-current-time-zone>`, but this can be updated
+to the end user's time zone through the use of :ref:`filters and tags
+<time-zones-in-templates>`.
 
 This is handy if your users live in more than one time zone and you want to
 display datetime information according to each user's wall clock.