From 269291019ec2dddddd6dd3b9833a37e7b94944ab Mon Sep 17 00:00:00 2001
From: Moayad Mardini <moayad.m@gmail.com>
Date: Mon, 19 May 2014 16:02:42 +0300
Subject: [PATCH] [1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc about
 strictly_below

The paragraph was a copy of strictly_above.

Backport of 2f43229c2f from master
---
 docs/ref/contrib/gis/geoquerysets.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt
index 0b1fee3bfe..957a0497af 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -492,16 +492,16 @@ strictly_below
 
 *Availability*: PostGIS
 
-Tests if the geometry field's bounding box is strictly above the lookup
+Tests if the geometry field's bounding box is strictly below the lookup
 geometry's bounding box.
 
 Example::
 
-    Zipcode.objects.filter(poly__strictly_above=geom)
+    Zipcode.objects.filter(poly__strictly_below=geom)
 
 PostGIS equivalent::
 
-    SELECT ... WHERE poly |>> geom
+    SELECT ... WHERE poly <<| geom
 
 
 .. _distance-lookups: