Fixes a few grammatical and punctuation errors.

docs/userguide/application.rst

@@ -12,7 +12,7 @@ The Celery library must be instantiated before use, this instance
 is called an application (or *app* for short).
 
 The application is thread-safe so that multiple Celery applications
-with different configuration, components and tasks can co-exist in the
+with different configurations, components and tasks can co-exist in the
 same process space.
 
 Let's create one now:
@@ -32,12 +32,12 @@ current main module (``__main__``), and the memory address of the object
 Main Name
 =========
 
-Only one of these is important, and that is the main module name,
-let's look at why that is.
+Only one of these is important, and that is the main module name.
+Let's look at why that is.
 
 When you send a task message in Celery, that message will not contain
 any source code, but only the name of the task you want to execute.
-This works similarly to how host names works on the internet: every worker
+This works similarly to how host names work on the internet: every worker
 maintains a mapping of task names to their actual functions, called the *task
 registry*.
 
@@ -154,7 +154,7 @@ from a configuration object.
 
 This can be a configuration module, or any object with configuration attributes.
 
-Note that any configuration that was previous set will be reset when
+Note that any configuration that was previously set will be reset when
 :meth:`~@config_from_object` is called.  If you want to set additional
 configuration you should do so after.
 
@@ -333,7 +333,7 @@ Finalizing the object will:
 
     #. Make sure all tasks are bound to the current app.
 
-        Tasks are bound to apps so that it can read default
+        Tasks are bound to an app so that they can read default
         values from the configuration.
 
 .. _default-app:
@@ -466,7 +466,7 @@ Abstract Tasks
 ==============
 
 All tasks created using the :meth:`~@task` decorator
-will inherit from the applications base :attr:`~@Task` class.
+will inherit from the application's base :attr:`~@Task` class.
 
 You can specify a different base class with the ``base`` argument:
 

docs/userguide/tasks.rst

@@ -150,7 +150,7 @@ if the module name is "tasks.py":
 Automatic naming and relative imports
 -------------------------------------
 
-Relative imports and automatic name generation does not go well together,
+Relative imports and automatic name generation do not go well together,
 so if you're using relative imports you should set the name explicitly.
 
 For example if the client imports the module "myapp.tasks" as ".tasks", and
@@ -555,7 +555,7 @@ General
 
     Example: `"100/m"` (hundred tasks a minute). This will enforce a minimum
     delay of 600ms between starting two tasks on the same worker instance.
-    
+
     Default is the :setting:`CELERY_DEFAULT_RATE_LIMIT` setting,
     which if not specified means rate limiting for tasks is disabled by default.
 
@@ -600,7 +600,7 @@ General
 
     A string identifying the default serialization
     method to use. Defaults to the :setting:`CELERY_TASK_SERIALIZER`
-    setting.  Can be `pickle` `json`, `yaml`, or any custom
+    setting.  Can be `pickle`, `json`, `yaml`, or any custom
     serialization methods that have been registered with
     :mod:`kombu.serialization.registry`.
 
@@ -1179,7 +1179,7 @@ Handlers
 How it works
 ============
 
-Here comes the technical details, this part isn't something you need to know,
+Here come the technical details. This part isn't something you need to know,
 but you may be interested.
 
 All defined tasks are listed in a registry.  The registry contains
@@ -1338,8 +1338,8 @@ Granularity
 -----------
 
 The task granularity is the amount of computation needed by each subtask.
-In general it is better to split the problem up into many small tasks, than
-have a few long running tasks.
+In general it is better to split the problem up into many small tasks rather
+than have a few long running tasks.
 
 With smaller tasks you can process more tasks in parallel and the tasks
 won't run long enough to block the worker from processing other waiting tasks.
@@ -1507,7 +1507,7 @@ depending on state from the current transaction*:
 Example
 =======
 
-Let's take a real world example; A blog where comments posted needs to be
+Let's take a real world example: a blog where comments posted need to be
 filtered for spam.  When the comment is created, the spam filter runs in the
 background, so the user doesn't have to wait for it to finish.