Ticket #11931: fkdocs.diff

docs/topics/db/queries.txt

@@ -622 +622 @@
     >>> print [p.headline for p in queryset] # Evaluate the query set.
     >>> print [p.pub_date for p in queryset] # Re-use the cache from the evaluation.
 
+.. _complex_lookups_with_q:
+
 Complex lookups with Q objects
 ==============================
 
@@ -629 +631 @@
 you need to execute more complex queries (for example, queries with ``OR``
 statements), you can use ``Q`` objects.
 
-A ``Q`` object (``django.db.models.Q``) is an object used to encapsulate a
+A ``Q`` object (:class:`django.db.models.Q`) is an object used to encapsulate a
 collection of keyword arguments. These keyword arguments are specified as in
 "Field lookups" above.
 

docs/ref/models/fields.txt

@@ -844 +844 @@
     current date/time to be chosen.
 
     Instead of a dictionary this can also be a :class:`~django.db.models.Q`
-    object (an object with a :meth:`get_sql` method) for more complex queries.
+    object (see :ref:`complex_lookups_with_q`) for more complex queries.
 
     ``limit_choices_to`` has no effect on the inline FormSets that are created
     to display related objects in the admin.