From 86c45d8bc6724c29fe4b42f1e513ce8c1b883194 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Fri, 15 Dec 2023 07:54:02 +0100 Subject: [PATCH] Fixed typos in docs. --- docs/topics/auth/default.txt | 2 +- docs/topics/cache.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt index c8140e4d228..a8d32b2fea4 100644 --- a/docs/topics/auth/default.txt +++ b/docs/topics/auth/default.txt @@ -776,7 +776,7 @@ The ``permission_required`` decorator It's a relatively common task to check whether a user has a particular permission. For that reason, Django provides a shortcut for that case: the - :func:`~django.contrib.auth.decorators.permission_required()` decorator.:: + :func:`~django.contrib.auth.decorators.permission_required()` decorator:: from django.contrib.auth.decorators import permission_required diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 5935c3e27f4..880f606aaef 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -1049,7 +1049,7 @@ of keys to be cleared: Finally, if you want to delete all the keys in the cache, use ``cache.clear()``. Be careful with this; ``clear()`` will remove *everything* -from the cache, not just the keys set by your application. : +from the cache, not just the keys set by your application: .. code-block:: pycon