From 267b121b1e8a87adc61771ec786e6d9037df2462 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Fievet?= Date: Sun, 7 Sep 2014 11:29:20 +0200 Subject: [PATCH] [1.7.x] Fixed typo in docs/howto/custom-lookups.txt. Backport of f36ab2d3f2 from master --- docs/howto/custom-lookups.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/custom-lookups.txt b/docs/howto/custom-lookups.txt index af7c18e38ca..c02b896071a 100644 --- a/docs/howto/custom-lookups.txt +++ b/docs/howto/custom-lookups.txt @@ -226,7 +226,7 @@ backends are ``sqlite``, ``postgresql``, ``oracle`` and ``mysql``. How Django determines the lookups and transforms which are used ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -In some cases you may which to dynamically change which ``Transform`` or +In some cases you may wish to dynamically change which ``Transform`` or ``Lookup`` is returned based on the name passed in, rather than fixing it. As an example, you could have a field which stores coordinates or an arbitrary dimension, and wish to allow a syntax like ``.filter(coords__x7=4)`` to return