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/security.txt2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index ae880bbc2f..51d427abf4 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -783,7 +783,7 @@ uniquely identify the cache fragment:
{% load cache %}
{% cache 500 sidebar request.user.username %}
- .. sidebar for logged in user ..
+ .. sidebar for logged-in user ..
{% endcache %}
If :setting:`USE_I18N` is set to ``True`` the per-site middleware cache will
diff --git a/docs/topics/security.txt b/docs/topics/security.txt
index 2cc27786d3..057f8a1aca 100644
--- a/docs/topics/security.txt
+++ b/docs/topics/security.txt
@@ -75,7 +75,7 @@ control.
:ref:`CSRF protection works <how-csrf-works>` by checking for a secret in each
POST request. This ensures that a malicious user cannot "replay" a form POST to
-your website and have another logged in user unwittingly submit that form. The
+your website and have another logged-in user unwittingly submit that form. The
malicious user would have to know the secret, which is user specific (using a
cookie).