Author: adrian
Date: 2006-07-20 10:45:16 -0500 (Thu, 20 Jul 2006)
New Revision: 3397

Modified:
   django/trunk/django/middleware/cache.py
   django/trunk/docs/cache.txt
Log:
Small style fixes to docs from [3395]

Modified: django/trunk/django/middleware/cache.py
===================================================================
--- django/trunk/django/middleware/cache.py     2006-07-20 15:37:51 UTC (rev 
3396)
+++ django/trunk/django/middleware/cache.py     2006-07-20 15:45:16 UTC (rev 
3397)
@@ -11,7 +11,7 @@
     Only parameter-less GET or HEAD-requests with status code 200 are cached.
 
     If CACHE_MIDDLEWARE_ANONYMOUS_ONLY is set to True, only anonymous requests
-    (i.e. those node made by a logged in user) will be cached. This is a
+    (i.e., those node made by a logged-in user) will be cached. This is a
     simple and effective way of avoiding the caching of the Django admin (and
     any other user-specific content).
 

Modified: django/trunk/docs/cache.txt
===================================================================
--- django/trunk/docs/cache.txt 2006-07-20 15:37:51 UTC (rev 3396)
+++ django/trunk/docs/cache.txt 2006-07-20 15:45:16 UTC (rev 3397)
@@ -230,13 +230,13 @@
   collisions. Use an empty string if you don't care.
 
 The cache middleware caches every page that doesn't have GET or POST
-parameters. Optionally, If the ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting is
-``True``, only anonymous requests (i.e. those node made by a logged in user)
-will be cached. This is a simple and effective way of disabling caching on any
-user-specific content ( include Django's admin interface).
+parameters. Optionally, if the ``CACHE_MIDDLEWARE_ANONYMOUS_ONLY`` setting is
+``True``, only anonymous requests (i.e., those node made by a logged-in user)
+will be cached. This is a simple and effective way of disabling caching for any
+user-specific pages (include Django's admin interface).
 
-Additionally, ``CacheMiddleware`` automatically sets a few headers
-in each ``HttpResponse``:
+Additionally, ``CacheMiddleware`` automatically sets a few headers in each
+``HttpResponse``:
 
 * Sets the ``Last-Modified`` header to the current date/time when a fresh
   (uncached) version of the page is requested.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to