Added link to the Django ORM Lookup Type topic in the django docs.

This will help a user know what exactly are we talking about when we say lookup types in Django ORM.
carltongibson · Nov 25, 2013 · 4f906b6 · 4f906b6
1 parent 012833b
commit 4f906b6
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/ref/filters.txt b/docs/ref/filters.txt
@@ -118,8 +118,8 @@ recieves a ``QuerySet`` and the value to filter on and should return a
 ``lookup_type``
 ~~~~~~~~~~~~~~~
 
-The type of lookup that should be performed using the Django ORM.  All the
-normal options are allowed, and should be provided as a string.  You can also
+The type of lookup that should be performed using the [Django ORM](https://docs.djangoproject.com/en/dev/ref/models/querysets/#field-lookups "Django's ORM Lookups").  
+All the normal options are allowed, and should be provided as a string.  You can also
 provide either ``None`` or a ``list`` or a ``tuple``.  If ``None`` is provided,
 then the user can select the lookup type from all the ones available in the Django
 ORM.  If a ``list`` or ``tuple`` is provided, then the user can select from those

diff --git a/docs/usage.txt b/docs/usage.txt
@@ -46,7 +46,7 @@ declarative syntax::
             fields = ['price', 'release_date']
 
 Filters take a ``lookup_type`` argument which specifies what lookup type to
-use with Django's ORM.  So here when a user entered a price it would show all
+use with [Django's ORM](https://docs.djangoproject.com/en/dev/ref/models/querysets/#field-lookups "Django's ORM Lookups").  So here when a user entered a price it would show all
 Products with a price less than that.
 
 Items in the ``fields`` sequence in the ``Meta`` class may include