From 6baa46cb8b7903c87d7855dc32d5c6a219c10ff1 Mon Sep 17 00:00:00 2001
From: Thomas Chaumeny <t.chaumeny@gmail.com>
Date: Sun, 5 Oct 2014 23:12:46 +0200
Subject: [PATCH] Updated assertQuerysetEqual documentation following
 311b3ad9db94c3e04f929c2622be4f10d759f45e

---
 docs/topics/testing/tools.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 7bbc441183..43c5fcaf48 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -1497,7 +1497,7 @@ your test suite.
 
     By default, the comparison is also ordering dependent. If ``qs`` doesn't
     provide an implicit ordering, you can set the ``ordered`` parameter to
-    ``False``, which turns the comparison into a Python set comparison.
+    ``False``, which turns the comparison into a ``collections.Counter`` comparison.
     If the order is undefined (if the given ``qs`` isn't ordered and the
     comparison is against more than one ordered values), a ``ValueError`` is
     raised.