From f5c944b3141c58bb4a5c7bbca61180b2ad7c13aa Mon Sep 17 00:00:00 2001
From: mengxun <30499307+mengxunQAQ@users.noreply.github.com>
Date: Tue, 19 Aug 2025 23:43:05 +0800
Subject: [PATCH] Fixed spelling of "logged-in" when used as an adjective in
 docs.

---
 docs/ref/clickjacking.txt | 2 +-
 docs/topics/cache.txt     | 2 +-
 docs/topics/security.txt  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/ref/clickjacking.txt b/docs/ref/clickjacking.txt
index 12c7afc8c4..0c8dc0339d 100644
--- a/docs/ref/clickjacking.txt
+++ b/docs/ref/clickjacking.txt
@@ -15,7 +15,7 @@ have loaded in a hidden frame or iframe.
 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
 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
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index 3f8c00d160..dbfa2c8c1e 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 1044e64e7e..272206da54 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).