[Checkins] SVN: zope.fssync/trunk/src/zope/fssync/README.txt Fix some minor language issues, break some overly long lines.

[Martijn Faassen]

Log message for revision 76673:
  Fix some minor language issues, break some overly long lines.
  

Changed:
  U   zope.fssync/trunk/src/zope/fssync/README.txt

-=-
Modified: zope.fssync/trunk/src/zope/fssync/README.txt
===================================================================
--- zope.fssync/trunk/src/zope/fssync/README.txt	2007-06-13 22:13:30 UTC (rev 76672)
+++ zope.fssync/trunk/src/zope/fssync/README.txt	2007-06-13 22:40:46 UTC (rev 76673)
@@ -20,7 +20,7 @@
 by humans in most circumstances a pickle format may be the most 
 complete and easy one to use.
 In the use case of content management it may be more important that 
-all metadata are readable by humans. In this case a another format, 
+all metadata are readable by humans. In this case another format, 
 e.g. RDFa, may be more appropriate.
 
 Main components
@@ -48,8 +48,8 @@
       and metadata. Alternative implementations may be use standard pickle,
       a human readable format like RDFa, or application specific formats.
 
-    - ISynchronizer: Synchronizer produce serialized pieces of a 
-      Python object (the ISerializer part of a synchronizer) and 
+    - ISynchronizer: Synchronizers produce serialized pieces of a
+      Python object (the ISerializer part of a synchronizer) and
       consume serialized data to (re-)create Python objects (the
       IDeserializer part of a synchronizer).
 
@@ -265,8 +265,8 @@
     </pickle>
     <BLANKLINE>
 
-After the registration of the necessary generators we can reimport the serialized
-data from the repository:
+After the registration of the necessary generators we can reimport the
+serialized data from the repository:
 
     >>> component.provideUtility(synchronizer.FileGenerator(),
     ...                                 provides=interfaces.IFileGenerator)
@@ -330,16 +330,17 @@
 Pickling 
 ========
 
-In many data structures, large, complex objects are composed of smaller objects. 
-These objects are typically stored in one of two ways:
+In many data structures, large, complex objects are composed of
+smaller objects.  These objects are typically stored in one of two
+ways:
 
     1.  The smaller objects are stored inside the larger object.
 
     2.  The smaller objects are allocated in their own location, 
         and the larger object stores references to them.
 
-In case 1 the object is self-contained and can be pickled completely. This is the
-default behavior of the fssync pickler:
+In case 1 the object is self-contained and can be pickled
+completely. This is the default behavior of the fssync pickler:
 
     >>> pickler = interfaces.IPickler([42])
     >>> pickler