From 672de44e242369d29136bbf1f3ae1059dd787936 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 12 Nov 2015 17:29:03 -0500 Subject: [PATCH] [1.9.x] Replaced "inbuilt" with more common "built-in". Backport of a8f05f405f8b78e13d7c4c9ffd73d6182b6fc4d5 from master --- docs/ref/models/querysets.txt | 2 +- docs/releases/1.7.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 458c70d736..310cfdb1d5 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -2197,7 +2197,7 @@ specified as keyword arguments to the ``QuerySet`` methods :meth:`filter()`, For an introduction, see :ref:`models and database queries documentation `. -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 ` for model fields. As a convenience when no lookup type is provided (like in diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt index edabb0d15e..055a017609 100644 --- a/docs/releases/1.7.txt +++ b/docs/releases/1.7.txt @@ -279,7 +279,7 @@ Custom lookups ~~~~~~~~~~~~~~ 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. The :class:`django.db.models.Lookup` class provides a way to add lookup