diff --git a/django/middleware/cache.py b/django/middleware/cache.py
index 6f995ba0b1..0d41713804 100644
--- a/django/middleware/cache.py
+++ b/django/middleware/cache.py
@@ -11,7 +11,7 @@ class CacheMiddleware(object):
     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).
 
diff --git a/docs/cache.txt b/docs/cache.txt
index 5efa2649ae..50cd3dcb0c 100644
--- a/docs/cache.txt
+++ b/docs/cache.txt
@@ -230,13 +230,13 @@ Then, add the following required settings to your Django settings file:
   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.