--- a/README.txt	Sun Jun 02 15:40:26 2024 -0700
+++ b/README.txt	Sun Jun 02 15:47:40 2024 -0700
@@ -79,7 +79,7 @@
 
 This microformat approach allows not only easy editing of the HTML
 documents, but the documents may be indepently served and displayed
-without the toolbox server-side. 
+without the toolbox server-side.
 
 The HTML microformat was never implemented (though, since the model
 backend is pluggable, it easily could be). Instead, the original
@@ -91,13 +91,13 @@
 A couch backend was also written.
 
       +------------+-----------+------------+
-      |Displayable?|File-based?|Concurrency?|
+      |Displayable |File-based |Concurrency |
 +-----+------------+-----------+------------+
 |HTML |Yes         |Yes        |No          |
 +-----+------------+-----------+------------+
 |JSON |Not really  |Yes        |No          |
 +-----+------------+-----------+------------+
-|Couch|No          |No         |Yes?        |
+|Couch|No          |No         |Yes         |
 +-----+------------+-----------+------------+
 
 The concurrency issue with file-based documennt backends may be
@@ -134,9 +134,9 @@
 Deployment, however, may be tailored as desired.  Any of the given
 templates may be overridden via passing a ``template_dir`` parameter
 with a path to a directory that have templates of the appropriate
-names as found in toolbox's ``templates`` directory. 
+names as found in toolbox's ``templates`` directory.
 
-Likewise, the static files (css, js, etc.) are served using ``paste``'s 
+Likewise, the static files (css, js, etc.) are served using ``paste``'s
 ``StaticURLParser`` out of toolbox's ``static`` directory. (See
 toolbox's ``factory.py``.) Notably this is *not* done using the WSGI
 app itself.  Doing it with middleware allows the deployment to be