diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-27 09:07:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-27 09:07:02 +0200 |
| commit | 803e70b1adb71d86eb5bbb4074ef5ff96ae6e55d (patch) | |
| tree | 353e9d3015319a09a2a0d61ad57639b79ac374ae /docs/topics/async.txt | |
| parent | f4bab0982aba90dd1d2a7f9b6141d72f76922fe5 (diff) | |
Fixed some formatting issues in docs.
Diffstat (limited to 'docs/topics/async.txt')
| -rw-r--r-- | docs/topics/async.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/async.txt b/docs/topics/async.txt index 3b3daeecce..c820f54879 100644 --- a/docs/topics/async.txt +++ b/docs/topics/async.txt @@ -60,7 +60,7 @@ If you want to use these, you will need to deploy Django using <async-middleware>` contexts. Some of Django's middleware is built like this, but not all. To see what middleware Django has to adapt, you can turn on debug logging for the ``django.request`` logger and look for log - messages about *`"Synchronous middleware ... adapted"*. + messages about *"Synchronous middleware ... adapted"*. In both ASGI and WSGI mode, you can still safely use asynchronous support to run code in parallel rather than serially. This is especially handy when |
