summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Everitt <paul@agendaless.com>2013-10-09 13:53:10 -0400
committerPaul Everitt <paul@agendaless.com>2013-10-09 13:53:10 -0400
commitbd3d23330abfe39182b7c47f79f61f26e20d1221 (patch)
tree22bbfc3ea3d35d2a73a2c70b0fb5f042b48dddcd
parenta2b15855bee4893524609a941954c823bfbcec0d (diff)
downloadpyramid-bd3d23330abfe39182b7c47f79f61f26e20d1221.tar.gz
pyramid-bd3d23330abfe39182b7c47f79f61f26e20d1221.tar.bz2
pyramid-bd3d23330abfe39182b7c47f79f61f26e20d1221.zip
Hedge a little while the compendium of session add-ons is written.
-rw-r--r--docs/quick_tutorial/sessions.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/quick_tutorial/sessions.rst b/docs/quick_tutorial/sessions.rst
index ba26d0133..0f284e9a7 100644
--- a/docs/quick_tutorial/sessions.rst
+++ b/docs/quick_tutorial/sessions.rst
@@ -13,8 +13,8 @@ When people use your web application, they frequently perform a task
that requires semi-permanent data to be saved. For example, a shopping
cart. This is called a :term:`session`.
-Pyramid has basic built-in support for sessions, with add-ons such as
-*dogpile.cache* (or your own custom sessioning engine) that provide
+Pyramid has basic built-in support for sessions, with add-ons
+or your own custom sessioning engine) that can provide
richer session support. Let's take a look at the
:ref:`built-in sessioning support <sessions_chapter>`.