p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Replaced "inbuilt" with more common "built-in".

This commit is contained in:
Tim Graham 2015-11-12 17:29:03 -05:00
parent 9788625277
commit a8f05f405f
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/models/querysets.txt
View File

@ -2177,7 +2177,7 @@ specified as keyword arguments to the ``QuerySet`` methods :meth:`filter()`,
For an introduction, see :ref:`models and database queries documentation For an introduction, see :ref:`models and database queries documentation
<field-lookups-intro>`. <field-lookups-intro>`.
Django's inbuilt lookups are listed below. It is also possible to write Django's built-in lookups are listed below. It is also possible to write
:doc:`custom lookups </howto/custom-lookups>` for model fields. :doc:`custom lookups </howto/custom-lookups>` for model fields.
As a convenience when no lookup type is provided (like in As a convenience when no lookup type is provided (like in

2
docs/releases/1.7.txt
View File

@ -274,7 +274,7 @@ Custom lookups
~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
It is now possible to write custom lookups and transforms for the ORM. It is now possible to write custom lookups and transforms for the ORM.
Custom lookups work just like Django's inbuilt lookups (e.g. ``lte``, Custom lookups work just like Django's built-in lookups (e.g. ``lte``,
``icontains``) while transforms are a new concept. ``icontains``) while transforms are a new concept.
The :class:`django.db.models.Lookup` class provides a way to add lookup The :class:`django.db.models.Lookup` class provides a way to add lookup