summaryrefslogtreecommitdiff
path: root/docs/ref
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:12:40 +0200
commitde11488c52956d3746f56e71208afe3afa34ca99 (patch)
tree4f2174724137f30981b54035cbc06e1eab36900a /docs/ref
parentcfc119716813c225e3d1cae59e3da5718231ac3b (diff)
[2.2.x] Fixed typo in docs/ref/settings.txt.
Backport of 4cbe2b06ce580423c62b6e49969f7e24d57d63b8 from master
Diffstat (limited to 'docs/ref')
-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 399ffb6a77..e29093dc3a 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -388,7 +388,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
@@ -3093,7 +3093,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