From a48c0180f56316b0e32bf2f4a858d1e097eb1863 Mon Sep 17 00:00:00 2001
From: Paul Wayper <paulway@redhat.com>
Date: Thu, 14 Mar 2019 14:08:02 +1100
Subject: [PATCH] [2.2.x] Fixed #30253 -- Doc'd how to order nulls in
 QuerySet.order_by().

Backport of 1025e764291167f2f34a4d55bd3d043836e74250 from master.
---
 docs/ref/models/querysets.txt | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 444c428583..51bb453b97 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -312,10 +312,14 @@ identical to::
     Entry.objects.order_by('blog__name')
 
 You can also order by :doc:`query expressions </ref/models/expressions>` by
-calling ``asc()`` or ``desc()`` on the expression::
+calling :meth:`~.Expression.asc` or :meth:`~.Expression.desc` on the
+expression::
 
     Entry.objects.order_by(Coalesce('summary', 'headline').desc())
 
+:meth:`~.Expression.asc` and :meth:`~.Expression.desc` have arguments
+(``nulls_first`` and ``nulls_last``) that control how null values are sorted.
+
 Be cautious when ordering by fields in related models if you are also using
 :meth:`distinct()`. See the note in :meth:`distinct` for an explanation of how
 related model ordering can change the expected results.