[Zope3-checkins] SVN: Zope3/trunk/src/scheduler/README.txt - typos

[Christian Theune]

Log message for revision 40471:
   - typos
  

Changed:
  U   Zope3/trunk/src/scheduler/README.txt

-=-
Modified: Zope3/trunk/src/scheduler/README.txt
===================================================================
--- Zope3/trunk/src/scheduler/README.txt	2005-12-02 14:06:03 UTC (rev 40470)
+++ Zope3/trunk/src/scheduler/README.txt	2005-12-02 14:34:07 UTC (rev 40471)
@@ -11,7 +11,7 @@
 -------
 
 From a high-level point of view, the developer starts out by developing their
-own or us an existing task component:
+own or use an existing task component:
 
   >>> from scheduler import task
   >>> from twisted.internet import reactor
@@ -24,10 +24,10 @@
   >>> mytask = MyTask(callable, ('arg1', 'arg2'), {'kw1': 1, 'kw2': 2})
 
 As you can see, you only need to implement the ``computeDelayToNextCall()``
-method that used by the rescheduling mechism to determine the next time of
-execution. It is up to the developer to compute the delay, which is specified
-in seconds. Based on the system you are running on, a float for the delay
-allows you to specify sub-second intervals.
+method that is used by the rescheduling mechanism to determine the next time
+of execution. It is up to the developer to compute the delay, which is
+specified in seconds. Based on the system you are running on, a float for the
+delay allows you to specify sub-second intervals.
 
 So, now we have a task, but it has not been started:
 
@@ -166,4 +166,4 @@
 
 Finally, we need to cleanup after ourselves.
 
-  >>> time.time = orig_time
\ No newline at end of file
+  >>> time.time = orig_time