Fixed a doc complaint.

doc/guide/prog-zodb.tex

@@ -99,7 +99,7 @@ implement the \class{Storage} interface.
  \class{FileStorage}, which uses regular disk files, and
  \class{bsddb3Storage}, which uses Sleepycat Software's BerkeleyDB
  database.  You could write a new Storage that stored objects in a
- relational database or Metakit file, for example, if that would
+ relational database, for example, if that would
  better suit your application.  Two example storages,
  \class{DemoStorage} and \class{MappingStorage}, are available to use
  as models if you want to write a new Storage.

doc/guide/zeo.tex

@@ -30,7 +30,7 @@ XXX insert diagram here later
 Any number of processes can create a \class{ClientStorage}
 instance, and any number of threads in each process can be using that
 instance.  \class{ClientStorage} aggressively caches objects
-locally, so in order to avoid using stale data.  The ZEO server sends
+locally, so in order to avoid using stale data the ZEO server sends
 an invalidation message to all the connected \class{ClientStorage}
 instances on every write operation.  The invalidation message contains
 the object ID for each object that's been modified, letting the