summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2019-04-02 09:10:11 +0200
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2019-04-02 09:10:11 +0200
commit4cbe2b06ce580423c62b6e49969f7e24d57d63b8 (patch)
tree24c9f6257125965e86d19dfb54c5d17f4f26cd34 /docs
parent7cbcf2e2cbca1acfccfd973f746a9e6abfc0052e (diff)
Fixed typo in docs/ref/settings.txt.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/settings.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 60ec1a773d..5c87aa5d24 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -386,7 +386,7 @@ See :setting:`SESSION_COOKIE_SAMESITE` for details about ``SameSite``.
Default: ``False``
Whether to use a secure cookie for the CSRF cookie. If this is set to ``True``,
-the cookie will be marked as "secure," which means browsers may ensure that the
+the cookie will be marked as "secure", which means browsers may ensure that the
cookie is only sent with an HTTPS connection.
.. setting:: CSRF_USE_SESSIONS
@@ -3076,7 +3076,7 @@ Possible values for the setting are:
Default: ``False``
Whether to use a secure cookie for the session cookie. If this is set to
-``True``, the cookie will be marked as "secure," which means browsers may
+``True``, the cookie will be marked as "secure", which means browsers may
ensure that the cookie is only sent under an HTTPS connection.
Leaving this setting off isn't a good idea because an attacker could capture an