Skip to content

Commit f5c944b

Browse files
authored
Fixed spelling of "logged-in" when used as an adjective in docs.
1 parent f02b49d commit f5c944b

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

docs/ref/clickjacking.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ have loaded in a hidden frame or iframe.
1515
An example of clickjacking
1616
==========================
1717

18-
Suppose an online store has a page where a logged in user can click "Buy Now" to
18+
Suppose an online store has a page where a logged-in user can click "Buy Now" to
1919
purchase an item. A user has chosen to stay logged into the store all the time
2020
for convenience. An attacker site might create an "I Like Ponies" button on one
2121
of their own pages, and load the store's page in a transparent iframe such that

docs/topics/cache.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -783,7 +783,7 @@ uniquely identify the cache fragment:
783783

784784
{% load cache %}
785785
{% cache 500 sidebar request.user.username %}
786-
.. sidebar for logged in user ..
786+
.. sidebar for logged-in user ..
787787
{% endcache %}
788788

789789
If :setting:`USE_I18N` is set to ``True`` the per-site middleware cache will

docs/topics/security.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ control.
7575

7676
:ref:`CSRF protection works <how-csrf-works>` by checking for a secret in each
7777
POST request. This ensures that a malicious user cannot "replay" a form POST to
78-
your website and have another logged in user unwittingly submit that form. The
78+
your website and have another logged-in user unwittingly submit that form. The
7979
malicious user would have to know the secret, which is user specific (using a
8080
cookie).
8181

0 commit comments

Comments
 (0)