diff options
| author | mguegnol <31782490+mguegnol@users.noreply.github.com> | 2025-03-23 12:02:42 -0700 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2025-03-23 20:06:39 +0100 |
| commit | 659f88e4c96bea987b109754d22df8858f7e60d2 (patch) | |
| tree | e9b3df44021060cf0894afc48b7fed983eb3da92 | |
| parent | f581b0b5c225059662236a86f935cba090672aa0 (diff) | |
[5.1.x] Fixed typo in docs/topics/signals.txt.
Backport of e2b9a179133ebca9773c5c259f6a7d27489cf141 from main
| -rw-r--r-- | docs/topics/signals.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/signals.txt b/docs/topics/signals.txt index ea6989ed90..725d3a8138 100644 --- a/docs/topics/signals.txt +++ b/docs/topics/signals.txt @@ -318,7 +318,7 @@ Whether synchronous or asynchronous, receivers will be correctly adapted to whether ``send()`` or ``asend()`` is used. Synchronous receivers will be called using :func:`~.sync_to_async` when invoked via ``asend()``. Asynchronous receivers will be called using :func:`~.async_to_sync` when invoked via -``sync()``. Similar to the :ref:`case for middleware <async_performance>`, +``send()``. Similar to the :ref:`case for middleware <async_performance>`, there is a small performance cost to adapting receivers in this way. Note that in order to reduce the number of sync/async calling-style switches within a ``send()`` or ``asend()`` call, the receivers are grouped by whether or not |
