From e258961e4f9074694ec34b08c318079e9ec195e0 Mon Sep 17 00:00:00 2001
From: Karen Tracey <kmtracey@gmail.com>
Date: Sat, 23 May 2009 12:58:31 +0000
Subject: [PATCH] Fixed #11188 -- Removed incorrect doc note about step being
 unsupported when slicing query sets.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@10835 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 docs/topics/db/queries.txt | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index 5ec162fa16..4aa54261c4 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -279,8 +279,7 @@ This returns the sixth through tenth objects (``OFFSET 5 LIMIT 5``)::
 
     >>> Entry.objects.all()[5:10]
     
-Negative indexing (i.e. ``Entry.objects.all()[-1]``) is not supported, nor is
-the third "step" slice parameter.
+Negative indexing (i.e. ``Entry.objects.all()[-1]``) is not supported.
 
 Generally, slicing a ``QuerySet`` returns a new ``QuerySet`` -- it doesn't
 evaluate the query. An exception is if you use the "step" parameter of Python