summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorHaki Benita <hakibenita@gmail.com>2021-06-29 15:07:12 +0300
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-07-16 20:26:24 +0200
commit0ee092c8dd4f4ebdf51b6912d4150e26fb8066f9 (patch)
tree0569df9cb25a6ef0fbaee15494b25ecb97244dcd /docs
parentb7d25d025e0ae44c421fa0a9044623752c200d8b (diff)
[3.2.x] Fixed typo in docs/topics/signals.txt.
Backport of 59404e8cfea3d79d5f4df5b9a5bd731da212c8d3 from main
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/signals.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/topics/signals.txt b/docs/topics/signals.txt
index b76a000b34..523c225beb 100644
--- a/docs/topics/signals.txt
+++ b/docs/topics/signals.txt
@@ -5,10 +5,10 @@ Signals
.. module:: django.dispatch
:synopsis: Signal dispatch
-Django includes a "signal dispatcher" which helps allow decoupled applications
-get notified when actions occur elsewhere in the framework. In a nutshell,
-signals allow certain *senders* to notify a set of *receivers* that some action
-has taken place. They're especially useful when many pieces of code may be
+Django includes a "signal dispatcher" which helps decoupled applications get
+notified when actions occur elsewhere in the framework. In a nutshell, signals
+allow certain *senders* to notify a set of *receivers* that some action has
+taken place. They're especially useful when many pieces of code may be
interested in the same events.
Django provides a :doc:`set of built-in signals </ref/signals>` that let user