[Checkins] SVN: zope.fssync/trunk/src/zope/fssync/generic.txt Minor language fixes.

[Martijn Faassen]

Log message for revision 76766:
  Minor language fixes.
  

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

-=-
Modified: zope.fssync/trunk/src/zope/fssync/generic.txt
===================================================================
--- zope.fssync/trunk/src/zope/fssync/generic.txt	2007-06-18 15:41:40 UTC (rev 76765)
+++ zope.fssync/trunk/src/zope/fssync/generic.txt	2007-06-18 15:59:12 UTC (rev 76766)
@@ -47,7 +47,7 @@
     ...     def __call__(*args, **kw):
     ...         """A generic function is callable like any other function."""
 
-Since a generic function can use the component architecture it's 
+Since a generic function can use the component architecture its 
 definition can be extremely short if it uses the common adapter lookup
 mechanism to find the specific implementation of a function. Our 
 definition of generic function uses a multi-adapter if the function is
@@ -107,7 +107,7 @@
 
 Using the equivalent `register`  and `when` decorators looks nicer. 
 Note that the order of decorators is important here. The register 
-decorator is usefull in tests, if you want to extend or replace the
+decorator is useful in tests, if you want to extend or replace the
 implementations in your Zope3 application, you should of course use 
 the corresponding ZCML adapter statement:
 
@@ -183,7 +183,7 @@
     ...
     MissingImplementation: Missing ...IPrettyPrint implementation for ...MyList
     
-Sometimes it is more usefull to have a fallback behavior and a 
+Sometimes it is more useful to have a fallback behavior and a 
 warning. This can also be achieved easily without changing the basic
 API: