[Debexpo-devel] [debexpo] 29/32: Fix typo about invokation

Kentaro Hayashi kenhys-guest at moszumanska.debian.org
Sat Aug 19 06:51:04 UTC 2017


This is an automated email from the git hooks/post-receive script.

kenhys-guest pushed a commit to branch master
in repository debexpo.

commit 3f60457136b50e7de9c0859dc1cd0d824e526183
Author: Kentaro Hayashi <kenhys at gmail.com>
Date:   Sun Jul 17 03:09:14 2016 +0900

    Fix typo about invokation
    
    invokation ->
    invocation
---
 docs/writing_cronjobs.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/writing_cronjobs.rst b/docs/writing_cronjobs.rst
index 1ba2147..619abfa 100644
--- a/docs/writing_cronjobs.rst
+++ b/docs/writing_cronjobs.rst
@@ -4,7 +4,7 @@
 Writing cronjobs
 ================
 
-Writing cronjobs works similar to plugins. The invokation and arguments
+Writing cronjobs works similar to plugins. The invocation and arguments
 passed are different though.
 A minimal cronjob looks like this::
 
@@ -29,16 +29,16 @@ The architecture
 ================
 
 A cronjob should be subclassed from BaseCronjob. That ensure API compliant
-invokation. A worker thread runs your jobs cyclically, persistence is guaranteed
+invocation. A worker thread runs your jobs cyclically, persistence is guaranteed
 for the object runtime. Technically, you ``must`` define two objects in your
 module.
 
-Invokation::
+Invocation::
     cronjob = ImportUpload
     schedule = datetime.timedelta(seconds = 10)
 
 The 'cronjob' attribute is an object reference which should be instantiated upon
-cronjob invokation. The 'schedule' attribute defines how often your cronjob should
+cronjob invocation. The 'schedule' attribute defines how often your cronjob should
 invoke your worker method. This must be a datetime.timedelta object. This is a soft
 guarantee. The Worker thread will guarantee you not to run the job more often than you
 specified, but it will not invoke it precisely for every delta. Your cronjob will not
@@ -76,7 +76,7 @@ The destructor
 Similarly to the constructor, don't override the destructor. Use the `teardown`
 method instead
 
-The worker method invokation
+The worker method invocation
 ============================
 
 Implement the `invoke` method as your working horse. It will be called regularly

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debexpo/debexpo.git



More information about the Debexpo-devel mailing list