summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/cache.txt2
-rw-r--r--docs/topics/http/sessions.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index 563ab3837f..37384c3b8a 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -653,7 +653,7 @@ disable caching for a view (using the
.. _i18n-cache-key:
If :setting:`USE_I18N` is set to ``True`` then the generated cache key will
-include the name of the active :term:`language<language code>` -- see also
+include the name of the active :term:`language<language code>` (see also
:ref:`how-django-discovers-language-preference`). This allows you to easily
cache multilingual sites without having to create the cache key yourself.
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt
index 6fb329dd9a..4cc5634780 100644
--- a/docs/topics/http/sessions.txt
+++ b/docs/topics/http/sessions.txt
@@ -448,7 +448,7 @@ serializing these values is often straightforward
writing a decoder that can reliably get back the same thing that you put in is
more fragile. For example, you run the risk of returning a ``datetime`` that
was actually a string that just happened to be in the same format chosen for
-``datetime``\s).
+``datetime``\s.
Your serializer class must implement two methods,
``dumps(self, obj)`` and ``loads(self, data)``, to serialize and deserialize