Context Navigation

Changes between Initial Version and Version 2 of Ticket #28917

-              initial
+              v2
 Paginator (sanely!) does a check to verify that the queryset it is passed is ordered, and if it isn't, shows a warning.
+`Paginator` shows a warning if it receives an unordered queryset.
 However, if also emits this warning if passed a queryset which is guaranteed to be empty, for instance Article.objects.none()
+However, if also emits this warning if passed a queryset which is guaranteed to be empty, for instance `Article.objects.none()`.
 Working around this warning involves doing a bizarre Article.objects.none().order_by('id')
+Working around this warning involves doing a bizarre `Article.objects.none().order_by('id')`
 I believe there can be legitimate usecases for passing a .none() queryset to a paginator, for instance if a user's permissions are such that we restrict the objects they can view to the empty queryset.
+I believe there can be legitimate usecases for passing a `.none()` queryset to a paginator, for instance if a user's permissions are such that we restrict the objects they can view to the empty queryset.