From 084cbe1217a79230b7bc616a40e900baeb3a45d6 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Wed, 8 Oct 2025 10:58:59 +0200 Subject: [5.2.x] Added missing backticks in docs/ref/models/fields.txt. Backport of 4a8ca8bd6906b705c4445bc915d71beda2fc4b84 from main --- docs/ref/models/fields.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 511b6e0215..de0b888f82 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1727,8 +1727,9 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in * .. attribute:: CASCADE - Cascade deletes. Django emulates the behavior of the SQL constraint ON - DELETE CASCADE and also deletes the object containing the ForeignKey. + Cascade deletes. Django emulates the behavior of the SQL constraint ``ON + DELETE CASCADE`` and also deletes the object containing the + :class:`ForeignKey`. :meth:`.Model.delete` isn't called on related models, but the :data:`~django.db.models.signals.pre_delete` and @@ -1947,9 +1948,9 @@ The possible values for :attr:`~ForeignKey.on_delete` are found in Setting it to ``False`` does not mean you can reference a swappable model even if it is swapped out - ``False`` means that the migrations made - with this ForeignKey will always reference the exact model you specify - (so it will fail hard if the user tries to run with a User model you don't - support, for example). + with this :class:`ForeignKey` will always reference the exact model you + specify (so it will fail hard if the user tries to run with a ``User`` + model you don't support, for example). If in doubt, leave it to its default of ``True``. -- cgit v1.3