1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
|
Subject: Fix syntax error detected by lintian
From: Alex Mestiashvili <mailatgoogl@gmail.com>
--- gearmand.orig/docs/source/gearmand.rst
+++ gearmand/docs/source/gearmand.rst
@@ -17,7 +17,7 @@
.. option:: --check-args
- Check command line and configuration file argments and then exit.
+ Check command line and configuration file arguments and then exit.
.. option:: -d [ --daemon ]
--- gearmand.orig/docs/source/libgearman/gearman_client_job_status.rst
+++ gearmand/docs/source/libgearman/gearman_client_job_status.rst
@@ -29,7 +29,7 @@
:c:type:`GEARMAN_IN_PROGRESS` if it is running. Knowing whether the job is running or not has higher precedence. :c:func:`gearman_continue` can be used for loops where you want to exit from the loop once the job has been completed.
.. warning::
- For loops you should always check :c:type:`gearman_return_t` with :c:func:`gearman_continue` even if you specifiy the argument is_known or is_running. A non-blocking IO call can return something other then :c:type:`GEARMAN_SUCCESS`, in some cases you will want to treat those values not as errors.
+ For loops you should always check :c:type:`gearman_return_t` with :c:func:`gearman_continue` even if you specify the argument is_known or is_running. A non-blocking IO call can return something other then :c:type:`GEARMAN_SUCCESS`, in some cases you will want to treat those values not as errors.
----
--- gearmand.orig/docs/source/libgearman/gearman_return_t.rst
+++ gearmand/docs/source/libgearman/gearman_return_t.rst
@@ -166,7 +166,7 @@
WORKER TO CLIENT
****************
-Client which have registed a custom :c:type:`gearman_actions_t` may use these
+Client which have registered a custom :c:type:`gearman_actions_t` may use these
value as return values to the calling client.
.. c:type:: GEARMAN_WORK_DATA
|