Author: adrian
Date: 2008-09-07 17:55:31 -0500 (Sun, 07 Sep 2008)
New Revision: 8980

Modified:
   django/trunk/docs/topics/cache.txt
Log:
Small wording improvements to cache.txt

Modified: django/trunk/docs/topics/cache.txt
===================================================================
--- django/trunk/docs/topics/cache.txt  2008-09-07 19:15:41 UTC (rev 8979)
+++ django/trunk/docs/topics/cache.txt  2008-09-07 22:55:31 UTC (rev 8980)
@@ -186,10 +186,9 @@
 .. versionadded:: 1.0
 
 While Django includes support for a number of cache backends out-of-the-box,
-sometimes you will want to use a customised version or your own backend.  To
-use an external cache backend with Django, use a Python import path as the
-scheme portion (the part before the initial colon) of the ``CACHE_BACKEND``
-URI, like so::
+sometimes you might want to use a customized cache backend. To use an external
+cache backend with Django, use a Python import path as the scheme portion (the
+part before the initial colon) of the ``CACHE_BACKEND`` URI, like so::
 
     CACHE_BACKEND = 'path.to.backend://'
 
@@ -197,11 +196,10 @@
 as reference implementations. You'll find the code in the
 ``django/core/cache/backends/`` directory of the Django source.
 
-Note: Without a really compelling reason, like a host that doesn't support the
-them, you should stick to the cache backends included with Django. They've
-been really well-tested and are quite easy to use.
+Note: Without a really compelling reason, such as a host that doesn't support
+the them, you should stick to the cache backends included with Django. They've
+been well-tested and are easy to use.
 
-
 CACHE_BACKEND arguments
 -----------------------
 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to