mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-25 19:29:14 +00:00
Code Issues 32 Releases Wiki Activity

[5.2.x] Fixed spelling of "logged-in" when used as an adjective in docs.

Browse Source 
Backport of f5c944b3141c58bb4a5c7bbca61180b2ad7c13aa from main.
This commit is contained in:
mengxun 2025-08-19 23:43:05 +08:00 committed by Natalia
parent 9a720d5c50
commit 38844c348b
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/clickjacking.txt
View File

@ -15,7 +15,7 @@ have loaded in a hidden frame or iframe.
An example of clickjacking An example of clickjacking
========================== ==========================
Suppose an online store has a page where a logged in user can click "Buy Now" to Suppose an online store has a page where a logged-in user can click "Buy Now" to
purchase an item. A user has chosen to stay logged into the store all the time purchase an item. A user has chosen to stay logged into the store all the time
for convenience. An attacker site might create an "I Like Ponies" button on one for convenience. An attacker site might create an "I Like Ponies" button on one
of their own pages, and load the store's page in a transparent iframe such that of their own pages, and load the store's page in a transparent iframe such that

2
docs/topics/cache.txt
View File

@ -783,7 +783,7 @@ uniquely identify the cache fragment:
{% load cache %} {% load cache %}
{% cache 500 sidebar request.user.username %} {% cache 500 sidebar request.user.username %}
.. sidebar for logged in user .. .. sidebar for logged-in user ..
{% endcache %} {% endcache %}
If :setting:`USE_I18N` is set to ``True`` the per-site middleware cache will If :setting:`USE_I18N` is set to ``True`` the per-site middleware cache will

2
docs/topics/security.txt
View File

@ -75,7 +75,7 @@ control.
:ref:`CSRF protection works <how-csrf-works>` by checking for a secret in each :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 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 malicious user would have to know the secret, which is user specific (using a
cookie). cookie).