diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index f6283f3bd2..0efb10b9dd 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -757,6 +757,14 @@ tag for protection against :doc:`Cross Site Request Forgeries
 If this processor is enabled, every ``RequestContext`` will contain a variable
 ``request``, which is the current :class:`~django.http.HttpRequest`.
 
+``django.template.context_processors.tz``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. function:: tz
+
+If this processor is enabled, every ``RequestContext`` will contain a variable
+``TIME_ZONE``, providing the name of the currently active time zone.
+
 ``django.contrib.messages.context_processors.messages``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index b8cb3041ed..3461e143cd 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -314,9 +314,9 @@ You can get the name of the current time zone using the
 
     {% get_current_timezone as TIME_ZONE %}
 
-If you enable the ``django.template.context_processors.tz`` context processor,
-each :class:`~django.template.RequestContext` will contain a ``TIME_ZONE``
-variable with the value of ``get_current_timezone()``.
+Alternatively, you can activate the
+:func:`~django.template.context_processors.tz` context processor and
+use the ``TIME_ZONE`` context variable.
 
 Template filters
 ----------------