Docs: Wording

CONTRIBUTING.rst

@@ -10,7 +10,7 @@ This document is fairly extensive and you aren't really expected
 to study this in detail for small contributions;
 
     The most important rule is that contributing must be easy
-    and that the community is friendly and not nitpicking on details
+    and that the community is friendly and not nitpicking on details,
     such as coding style.
 
 If you're reporting a bug you should read the Reporting bugs section
@@ -700,7 +700,7 @@ is following the conventions.
         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
+  character to go on. This means 78 is a soft limit, and 79 is the hard
   limit :)
 
 * Import order

celery/utils/dispatch/saferef.py

@@ -212,7 +212,7 @@ class BoundNonDescriptorMethodWeakref(BoundMethodWeakref):  # pragma: no cover
         the same, instead of assuming that the function is a descriptor.
         This approach is equally fast, but not 100% reliable because
         functions can be stored on an attribute named differenty than the
-        function's name such as in::
+        function's name, such as in::
 
             >>> class A(object):
             ...     pass
@@ -222,7 +222,7 @@ class BoundNonDescriptorMethodWeakref(BoundMethodWeakref):  # pragma: no cover
             >>> A.bar = foo
 
         This shouldn't be a common use case.  So, on platforms where methods
-        aren't descriptors (such as Jython) this implementation has the
+        aren't descriptors (e.g. Jython) this implementation has the
         advantage of working in the most cases.
     """
     def __init__(self, target, on_delete=None):

celery/utils/objects.py

@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
-"""Object related utilities including introspection, etc."""
+"""Object related utilities, including introspection, etc."""
 from __future__ import absolute_import, unicode_literals
 
 __all__ = ['Bunch', 'FallbackContext', 'mro_lookup']

celery/worker/control.py

@@ -347,7 +347,7 @@ def _iter_schedule_requests(timer, Request=Request):
 
 @inspect_command(alias='dump_reserved')
 def reserved(state, **kwargs):
-    """List of currently reserved tasks (not including scheduled/active)."""
+    """List of currently reserved tasks, not including scheduled/active."""
     reserved_tasks = (
         state.tset(worker_state.reserved_requests) -
         state.tset(worker_state.active_requests)

docs/contributing.rst

@@ -10,7 +10,7 @@ This document is fairly extensive and you aren't really expected
 to study this in detail for small contributions;
 
     The most important rule is that contributing must be easy
-    and that the community is friendly and not nitpicking on details
+    and that the community is friendly and not nitpicking on details,
     such as coding style.
 
 If you're reporting a bug you should read the Reporting bugs section