From e36290b4eef1faaf6ad864d3493df1458ef96fbb Mon Sep 17 00:00:00 2001
From: Matthew Tretter <m@tthewwithanm.com>
Date: Wed, 17 Jul 2013 16:09:02 -0400
Subject: [PATCH] Woops. It uses the cache if DEBUG is False.

---
 docs/caching.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/caching.rst b/docs/caching.rst
index e6ab26d..b482f1f 100644
--- a/docs/caching.rst
+++ b/docs/caching.rst
@@ -103,7 +103,7 @@ Caching Data About Generated Files
 The easiest, and most significant improvement you can make to improve the
 performance of your site is to have ImageKit cache the state of your generated
 files. The default cache file backend will already do this (if ``DEBUG`` is
-``True``), using your default Django cache backend, but you can make it way
+``False``), using your default Django cache backend, but you can make it way
 better by setting ``IMAGEKIT_CACHE_BACKEND``. Generally, once a file is
 generated, you will never be removing it; therefore, if you can, you should set
 ``IMAGEKIT_CACHE_BACKEND`` to a cache backend that will cache forever.