From e038f98bf342af716cf16e38be989c2d0f126797 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Fri, 18 May 2018 18:08:37 -0400
Subject: [PATCH] Fixed #29398 -- Doc'd that cascade deletion doesn't call
 delete() of related models.

---
 docs/ref/models/fields.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index adb12aac63..c696b770b3 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1257,6 +1257,11 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in
     Cascade deletes. Django emulates the behavior of the SQL constraint ON
     DELETE CASCADE and also deletes the object containing the ForeignKey.
 
+    :meth:`.Model.delete` isn't called on related models, but the
+    :data:`~django.db.models.signals.pre_delete` and
+    :data:`~django.db.models.signals.post_delete` signals are sent for all
+    deleted objects.
+
 * .. attribute:: PROTECT
 
     Prevent deletion of the referenced object by raising