mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Fixed some typos in comments and docs.
Thanks to Mads Jenson for review.
This commit is contained in:
parent
f1d4a540b2
commit
103a6f4307
6 changed files with 9 additions and 9 deletions
|
@ -19,7 +19,7 @@ Running Django in Uvicorn
|
|||
|
||||
When Uvicorn is installed, a ``uvicorn`` command is available which runs ASGI
|
||||
applications. Uvicorn needs to be called with the location of a module
|
||||
containing a ASGI application object, followed by what the application is
|
||||
containing an ASGI application object, followed by what the application is
|
||||
called (separated by a colon).
|
||||
|
||||
For a typical Django project, invoking Uvicorn would look like::
|
||||
|
|
|
@ -194,7 +194,7 @@ When contributing to Django it's very important that your code changes don't
|
|||
introduce bugs into other areas of Django. One way to check that Django still
|
||||
works after you make your changes is by running Django's test suite. If all
|
||||
the tests still pass, then you can be reasonably sure that your changes
|
||||
work and haven't broken other parts Django. If you've never run Django's test
|
||||
work and haven't broken other parts of Django. If you've never run Django's test
|
||||
suite before, it's a good idea to run it once beforehand to get familiar with
|
||||
its output.
|
||||
|
||||
|
|
|
@ -294,8 +294,8 @@ for:
|
|||
keeping CSRF protection, consider enabling only same-origin referrers.
|
||||
|
||||
``SecurityMiddleware`` can set the ``Referrer-Policy`` header for you, based on
|
||||
the the :setting:`SECURE_REFERRER_POLICY` setting (note spelling: browsers send
|
||||
a ``Referer`` header when a user clicks a link, but the header instructing a
|
||||
the :setting:`SECURE_REFERRER_POLICY` setting (note spelling: browsers send a
|
||||
``Referer`` header when a user clicks a link, but the header instructing a
|
||||
browser whether to do so is spelled ``Referrer-Policy``). The valid values for
|
||||
this setting are:
|
||||
|
||||
|
@ -522,7 +522,7 @@ Here are some hints about the ordering of various Django middleware classes:
|
|||
|
||||
#. :class:`~django.contrib.sessions.middleware.SessionMiddleware`
|
||||
|
||||
Before any middleware that may raise an an exception to trigger an error
|
||||
Before any middleware that may raise an exception to trigger an error
|
||||
view (such as :exc:`~django.core.exceptions.PermissionDenied`) if you're
|
||||
using :setting:`CSRF_USE_SESSIONS`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue