From 659f88e4c96bea987b109754d22df8858f7e60d2 Mon Sep 17 00:00:00 2001 From: mguegnol <31782490+mguegnol@users.noreply.github.com> Date: Sun, 23 Mar 2025 12:02:42 -0700 Subject: [PATCH] [5.1.x] Fixed typo in docs/topics/signals.txt. Backport of e2b9a179133ebca9773c5c259f6a7d27489cf141 from main --- docs/topics/signals.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 `, +``send()``. Similar to the :ref:`case for middleware `, 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