Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed a long line, a typo, and a few misspellings from [9727].

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9729 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 11d382c6c449a86be794546a27afef63027d1a90 1 parent c01098e
Gary Wilson Jr. authored January 11, 2009

Showing 1 changed file with 9 additions and 9 deletions. Show diff stats Hide diff stats

  1. 18  docs/topics/http/sessions.txt
18  docs/topics/http/sessions.txt
@@ -57,29 +57,29 @@ sure you've configured your cache; see the :ref:`cache documentation
57 57
 
58 58
 .. warning::
59 59
 
60  
-    You should only use cache-based sessions if you're using the Memcached cache
61  
-    backend. The local-memory cache backend doesn't retain data long enough to
62  
-    be a good choice, and it'll be faster to use file or database sessions
63  
-    directly instead of sending everything through the file or database cache
64  
-    backends.
  60
+    You should only use cache-based sessions if you're using the Memcached
  61
+    cache backend. The local-memory cache backend doesn't retain data long
  62
+    enough to be a good choice, and it'll be faster to use file or database
  63
+    sessions directly instead of sending everything through the file or
  64
+    database cache backends.
65 65
 
66  
-Once your cache in configured, you've got two choices for how to store data in
  66
+Once your cache is configured, you've got two choices for how to store data in
67 67
 the cache:
68 68
 
69 69
     * Set :setting:`SESSION_ENGINE` to
70 70
       ``"django.contrib.sessions.backends.cache"`` for a simple caching session
71 71
       store. Session data will be stored directly your cache. However, session
72  
-      data may not be persistant: cached data can be evicted if the cache fills
  72
+      data may not be persistent: cached data can be evicted if the cache fills
73 73
       up or if the cache server is restarted.
74 74
 
75  
-    * For persistant, cached data, set :setting:`SESSION_ENGINE` to
  75
+    * For persistent, cached data, set :setting:`SESSION_ENGINE` to
76 76
       ``"django.contrib.sessions.backends.cached_db"``. This uses a
77 77
       write-through cache -- every write to the cache will also be written to
78 78
       the database. Session reads only use the database if the data is not
79 79
       already in the cache.
80 80
 
81 81
 Both session stores are quite fast, but the simple cache is faster because it
82  
-disreguards persistance. In most cases, the ``cached_db`` backend will be fast
  82
+disregards persistence. In most cases, the ``cached_db`` backend will be fast
83 83
 enough, but if you need that last bit of performance, and are willing to let
84 84
 session data be expunged from time to time, the ``cache`` backend is for you.
85 85
 

0 notes on commit 11d382c

Please sign in to comment.
Something went wrong with that request. Please try again.