[Checkins] SVN: zc.async/trunk/src/zc/async/ Fix typos.

[Zvezdan Petkovic]

Log message for revision 87892:
  Fix typos.
  
  

Changed:
  U   zc.async/trunk/src/zc/async/job.txt
  U   zc.async/trunk/src/zc/async/jobs_and_transactions.txt
  U   zc.async/trunk/src/zc/async/monitor.txt
  U   zc.async/trunk/src/zc/async/queue.txt
  U   zc.async/trunk/src/zc/async/subscribers.txt

-=-
Modified: zc.async/trunk/src/zc/async/job.txt
===================================================================
--- zc.async/trunk/src/zc/async/job.txt	2008-07-01 18:10:17 UTC (rev 87891)
+++ zc.async/trunk/src/zc/async/job.txt	2008-07-01 18:20:34 UTC (rev 87892)
@@ -442,7 +442,7 @@
 
 If the system fails around your code, four sorts of things might happen. In the
 context of the full zc.async system, it is the responsibility of the zc.async
-code to react as described below, and, when pertinent, your reponsibility to
+code to react as described below, and, when pertinent, your responsibility to
 make sure that the retry policy for the job does what you need.
 
 - The job never started, and timed out. zc.async should call ``fail`` on the

Modified: zc.async/trunk/src/zc/async/jobs_and_transactions.txt
===================================================================
--- zc.async/trunk/src/zc/async/jobs_and_transactions.txt	2008-07-01 18:10:17 UTC (rev 87891)
+++ zc.async/trunk/src/zc/async/jobs_and_transactions.txt	2008-07-01 18:20:34 UTC (rev 87892)
@@ -44,7 +44,7 @@
 
 Note the following:
 - if a job's wrapped callable returns a failure, that means that it
-  is taking responsiblity for any necessary abort: the job will still
+  is taking responsibility for any necessary abort: the job will still
   attempt to commit.
 - the status never changes out of COMPLETED even when a new callback is
   added.
@@ -265,4 +265,4 @@
     >>> conn = db.open()
     >>> root = conn.root()
     >>> import zc.async.configure
-    >>> zc.async.configure.base()
\ No newline at end of file
+    >>> zc.async.configure.base()

Modified: zc.async/trunk/src/zc/async/monitor.txt
===================================================================
--- zc.async/trunk/src/zc/async/monitor.txt	2008-07-01 18:10:17 UTC (rev 87891)
+++ zc.async/trunk/src/zc/async/monitor.txt	2008-07-01 18:20:34 UTC (rev 87892)
@@ -684,7 +684,7 @@
 
     >>> import zc.async.testing
     >>> reactor = zc.async.testing.Reactor()
-    >>> reactor.start() # this mokeypatches datetime.datetime.now 
+    >>> reactor.start() # this monkeypatches datetime.datetime.now 
 
     >>> import zc.async.queue
     >>> import zc.async.interfaces

Modified: zc.async/trunk/src/zc/async/queue.txt
===================================================================
--- zc.async/trunk/src/zc/async/queue.txt	2008-07-01 18:10:17 UTC (rev 87891)
+++ zc.async/trunk/src/zc/async/queue.txt	2008-07-01 18:20:34 UTC (rev 87892)
@@ -1055,7 +1055,7 @@
     >>> j3()
     42
 
-A retry policy can also request resceduling from a jobError or a commitError,
+A retry policy can also request rescheduling from a jobError or a commitError,
 although the default retry policies do not.
 
 jobError: "please reschedule now"

Modified: zc.async/trunk/src/zc/async/subscribers.txt
===================================================================
--- zc.async/trunk/src/zc/async/subscribers.txt	2008-07-01 18:10:17 UTC (rev 87891)
+++ zc.async/trunk/src/zc/async/subscribers.txt	2008-07-01 18:20:34 UTC (rev 87892)
@@ -149,7 +149,7 @@
 When an IQueues or IQueue is installed, an event is fired that provides the
 object being added, the container it is added to, and the name under which it
 is added.  Therefore, two ObjectAdded events have fired now, one for a queues
-colection and one for a queue.
+collection and one for a queue.
 
     >>> from zope.component import eventtesting
     >>> for event in eventtesting.getEvents(zc.async.interfaces.IObjectAdded):