Browse Source

Fixes more typos and code formatting

Julien Poissonnier 13 years ago
parent
commit
fb3a8f4852
2 changed files with 9 additions and 9 deletions
  1. 4 4
      docs/contributing.rst
  2. 5 5
      docs/userguide/tasks.rst

+ 4 - 4
docs/contributing.rst

@@ -553,15 +553,15 @@ is following the conventions.
 
 
 * Lines should not exceed 78 columns.
 * Lines should not exceed 78 columns.
 
 
-  You can enforce this in :program:`vim` by setting the ``textwidth`` option::
+  You can enforce this in :program:`vim` by setting the ``textwidth`` option:
 
 
   .. code-block:: vim
   .. code-block:: vim
 
 
         set textwidth=78
         set textwidth=78
 
 
-    If adhering to this limit makes the code less readable, you have one more
-    character to go on, which means 78 is a soft limit, and 79 is the hard
-    limit :)
+  If adhering to this limit makes the code less readable, you have one more
+  character to go on, which means 78 is a soft limit, and 79 is the hard
+  limit :)
 
 
 * Import order
 * Import order
 
 

+ 5 - 5
docs/userguide/tasks.rst

@@ -556,7 +556,7 @@ limitations.
   increase the polling intervals of operations such as `result.wait()`, and
   increase the polling intervals of operations such as `result.wait()`, and
   `tasksetresult.join()`
   `tasksetresult.join()`
 
 
-* Some databases uses a default transaction isolation level that
+* Some databases use a default transaction isolation level that
   is not suitable for polling tables for changes.
   is not suitable for polling tables for changes.
 
 
   In MySQL the default transaction isolation level is `REPEATABLE-READ`, which
   In MySQL the default transaction isolation level is `REPEATABLE-READ`, which
@@ -576,7 +576,7 @@ PENDING
 ~~~~~~~
 ~~~~~~~
 
 
 Task is waiting for execution or unknown.
 Task is waiting for execution or unknown.
-Any task id that is not know is implied to be in the pending state.
+Any task id that is not known is implied to be in the pending state.
 
 
 .. state:: STARTED
 .. state:: STARTED
 
 
@@ -644,7 +644,7 @@ you could have a look at :mod:`abortable tasks <~celery.contrib.abortable>`
 which defines its own custom :state:`ABORTED` state.
 which defines its own custom :state:`ABORTED` state.
 
 
 Use :meth:`Task.update_state <celery.task.base.BaseTask.update_state>` to
 Use :meth:`Task.update_state <celery.task.base.BaseTask.update_state>` to
-update a tasks state::
+update a task's state::
 
 
     @task
     @task
     def upload_files(filenames):
     def upload_files(filenames):
@@ -666,7 +666,7 @@ Creating pickleable exceptions
 A little known Python fact is that exceptions must behave a certain
 A little known Python fact is that exceptions must behave a certain
 way to support being pickled.
 way to support being pickled.
 
 
-Tasks that raises exceptions that are not pickleable will not work
+Tasks that raise exceptions that are not pickleable will not work
 properly when Pickle is used as the serializer.
 properly when Pickle is used as the serializer.
 
 
 To make sure that your exceptions are pickleable the exception
 To make sure that your exceptions are pickleable the exception
@@ -722,7 +722,7 @@ Creating custom task classes
 ============================
 ============================
 
 
 All tasks inherit from the :class:`celery.task.Task` class.
 All tasks inherit from the :class:`celery.task.Task` class.
-The tasks body is its :meth:`run` method.
+The task's body is its :meth:`run` method.
 
 
 The following code,
 The following code,