Meh.

2 files changed, 10 insertions, 84 deletions

diff --git a/docs/errata.rst b/docs/errata.rst
index 89e1b909a..627fc4e0e 100644
--- a/docs/errata.rst
+++ b/docs/errata.rst
@@ -1,93 +1,19 @@
 Errata for "The repoze.bfg Web Framework, Version 1.2" Printed Edition
 ======================================================================
 
-pp. 66
-------
-
-The sentence:
-
-  "Technically, traversal is a repoze.bfg subsystem that is separated
-  from traversal entirely."
-
-Should read:
-
-  "Technically, view lookup is a repoze.bfg subsystem that is
-  separated from traversal entirely."
-
-
-pp. 103
+pp. 350
 -------
 
 The sentence:
 
-  "The Context Finding and View Lookup (pp. 57) describes how a
-  context and a view name are computed using information from the
-  request. "
+  Note in the call to SessionDataManager that '3600' represents the
+  disuse timeout (5 minutes == 3600 seconds), and '5' represents a
+  write granularity time (the session will be marked as active at most
+  every five seconds).
 
 Should read:
 
-  "The chapter named Context Finding and View Lookup (pp. 57)
-  describes how, using information from the request, a context and a
-  view name are computed ."
-
-pp. 106
--------
-
-The enumeration:
-
-  2. Classes that have an ``__init__`` method that accepts ``context,
-     request``, e.g.:
-
-     .. code-block:: python
-        :linenos:
-
-        from webob import Response
-
-        class view(object):
-            def __init__(self, context, request):
-                return Response('OK')
-
-Should read:
-
-  2. Classes that have an ``__init__`` method that accepts ``context,
-     request``, and a ``__call__`` which accepts no arguments, e.g.:
-
-     .. code-block:: python
-        :linenos:
-
-        from webob import Response
-
-        class view(object):
-            def __init__(self, context, request):
-                self.context = context
-                self.request = request
-
-            def __call__(self):
-                return Response('OK')
-
-pp. 98
-------
-
-The section entitled "Global View Configurations May Match When a
-Route-Specific View Configuration Doesn't" is incorrect.  The entire
-section should be disregarded.
-
-pp. 99
-------
-
-The section entitled "context Type Registrations Bind More Tightly
-Than request Type Registrations" is incorrect.  The entire section
-should be disgregarded.
-
-pp. 83
--------
-
-A "route configuration" argument was omitted:
-
-  ``use_global_views``
-    When a request matches this route, and view lookup cannot find a
-    view which has a 'route_name' predicate argument that matches the
-    route, try to fall back to using a view that otherwise matches the
-    context, request, and view name (but does not match the route name
-    predicate).
-
+  Note in the call to SessionDataManager that '3600' represents the
+  disuse timeout (60 minutes == 3600 seconds), and '5' represents a
+  write granularity time (the session will be marked as active at most
+  every five seconds).
diff --git a/docs/tutorials/zodbsessions/index.rst b/docs/tutorials/zodbsessions/index.rst
index 43a8cf5db..7d94e2e08 100644
--- a/docs/tutorials/zodbsessions/index.rst
+++ b/docs/tutorials/zodbsessions/index.rst
@@ -157,7 +157,7 @@ Configuration
            return session
 
     Note in the call to ``SessionDataManager`` that '3600' represents
-    the disuse timeout (5 minutes == 3600 seconds), and '5' represents
+    the disuse timeout (60 minutes == 3600 seconds), and '5' represents
     a write granularity time (the session will be marked as active at
     most every five seconds).  Vary these values as necessary.