[2.2.x] Fixed #30326 -- Doc'd how to avoid persistence of F() assignment.

Backport of bfae195b0a2c8dae755610a7e23add5c6bc37b5e from master

1 files changed, 3 insertions, 1 deletions

diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index 2413952228..460a7f70d4 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -185,7 +185,9 @@ instance and will be applied on each :meth:`~Model.save()`. For example::
     reporter.save()
 
 ``stories_filed`` will be updated twice in this case. If it's initially ``1``,
-the final value will be ``3``.
+the final value will be ``3``. This persistence can be avoided by reloading the
+model object after saving it, for example, by using
+:meth:`~Model.refresh_from_db()`.
 
 Using ``F()`` in filters
 ~~~~~~~~~~~~~~~~~~~~~~~~