diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-27 09:07:02 +0200 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-27 09:09:44 +0200 |
| commit | 24cffddc6f1fc19590deef6b0f948e061e246688 (patch) | |
| tree | 49cc1ac458e3c3dc4968e968331b2a2d2323f7c1 | |
| parent | f175e03fc2a759f401f7e25e153835d28bf01ee0 (diff) | |
[3.0.x] Fixed some formatting issues in docs.
Backport of 803e70b1adb71d86eb5bbb4074ef5ff96ae6e55d from master.
| -rw-r--r-- | docs/ref/checks.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt index 289defa5ba..10427f9a07 100644 --- a/docs/ref/checks.txt +++ b/docs/ref/checks.txt @@ -123,7 +123,7 @@ If you're using MySQL, the following checks will be performed: * **mysql.E001**: MySQL does not allow unique ``CharField``\s to have a ``max_length`` > 255. * **mysql.W002**: MySQL Strict Mode is not set for database connection - '<alias>'. See also :ref:`mysql-sql-mode`. + ``<alias>``. See also :ref:`mysql-sql-mode`. Model fields ------------ @@ -373,8 +373,8 @@ The following checks are run if you use the :option:`check --deploy` option: set to ``True``, so your pages will not be served with an ``'X-XSS-Protection: 1; mode=block'`` header. You should consider enabling this header to activate the browser's XSS filtering and help prevent XSS - attacks. *This check is removed in Django 3.0 as the ``X-XSS-Protection`` - header is no longer honored by modern browsers.* + attacks. *This check is removed in Django 3.0 as the* ``X-XSS-Protection`` + *header is no longer honored by modern browsers.* * **security.W008**: Your :setting:`SECURE_SSL_REDIRECT` setting is not set to ``True``. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting to ``True`` or configure |