Moved context_processors from django.core to django.template.

2 files changed, 3 insertions, 3 deletions

diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index 348ac64978..0360b4789b 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -311,7 +311,7 @@ time zone is unset, the default time zone applies.
 get_current_timezone
 ~~~~~~~~~~~~~~~~~~~~
 
-When the ``django.core.context_processors.tz`` context processor is
+When the ``django.template.context_processors.tz`` context processor is
 enabled -- by default, it is -- each :class:`~django.template.RequestContext`
 contains a ``TIME_ZONE`` variable that provides the name of the current time
 zone.
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index 5a61162809..5ec8f13625 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -28,7 +28,7 @@ bit of i18n-related overhead in certain places of the framework. If you don't
 use internationalization, you should take the two seconds to set
 :setting:`USE_I18N = False <USE_I18N>` in your settings file. Then Django will
 make some optimizations so as not to load the internationalization machinery.
-You'll probably also want to remove ``'django.core.context_processors.i18n'``
+You'll probably also want to remove ``'django.template.context_processors.i18n'``
 from your :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting.
 
 .. note::
@@ -1509,7 +1509,7 @@ back to the previous page.
 Make sure that the following item is in your
 :setting:`TEMPLATE_CONTEXT_PROCESSORS` list in your settings file::
 
-    'django.core.context_processors.i18n'
+    'django.template.context_processors.i18n'
 
 Activate this view by adding the following line to your URLconf::