Fixed some typos in docs. (#1308)

Author: minho42

CHANGELOG.txt

@@ -168,7 +168,7 @@ https://channels.readthedocs.io/en/latest/releases
 * ``enforce_ordering`` now works correctly with the new-style process-specific
   channels
 
-* ASGI channel layer versions are now explicitly checked for version compatability
+* ASGI channel layer versions are now explicitly checked for version compatibility
 
 
 1.1.2 (2017-04-01)

docs/deploying.rst

@@ -145,7 +145,7 @@ Alternative Web Servers
 There are also alternative `ASGI <http://asgi.readthedocs.io>`_ servers
 that you can use for serving Channels.
 
-To some degree ASGI web servers should be interchangable, they should all have
+To some degree ASGI web servers should be interchangeable, they should all have
 the same basic functionality in terms of serving HTTP and WebSocket requests.
 
 Aspects where servers may differ are in their configuration and defaults,
@@ -167,7 +167,7 @@ Nginx/Supervisor (Ubuntu)
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This example sets up a Django site on an Ubuntu server, using Nginx as the
-main webserver and supervisord to run and manage Daphne. 
+main webserver and supervisord to run and manage Daphne.
 
 First, install Nginx and Supervisor::
 

docs/releases/1.0.0.rst

@@ -110,7 +110,7 @@ Delay Server
 
 A built-in delay server, launched with `manage.py rundelay`, now ships if you
 wish to use it. It needs some extra initial setup and uses a database for
-persistance; see :doc:`/delay` for more information.
+persistence; see :doc:`/delay` for more information.
 
 
 Minor Changes

docs/releases/1.1.3.rst

@@ -17,7 +17,7 @@ Minor Changes & Bugfixes
 * ``enforce_ordering`` now works correctly with the new-style process-specific
   channels
 
-* ASGI channel layer versions are now explicitly checked for version compatability
+* ASGI channel layer versions are now explicitly checked for version compatibility
 
 
 Backwards Incompatible Changes

docs/support.rst

@@ -22,7 +22,7 @@ Apologies if this comes off as harsh, but please understand that open source mai
 of time, and if we answered all the issues and support requests there would be no time left to actually work on the code
 itself!
 
-Making bugs reproducable
+Making bugs reproducible
 ------------------------
 
 If you're struggling with an issue that only happens in a production environment and can't get it to reproduce locally
@@ -65,7 +65,7 @@ General support request
     Sorry, but we can't help out with general support requests here - the issue tracker is for reproduceable bugs and
     concrete feature requests only! Please see our support documentation (http://channels.readthedocs.io/en/latest/support.html)
     for more information about where you can get general help.
-    
+
 Non-specific bug/"It doesn't work!"
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -75,11 +75,11 @@ Non-specific bug/"It doesn't work!"
     environment, as they may not be problems in the project itself. Our support documentation
     (http://channels.readthedocs.io/en/latest/support.html) has details about how to take this sort of problem, diagnose it,
     and either fix it yourself, get help from the community, or make it into an actionable issue that we can handle.
-    
+
     Sorry we have to direct you away like this, but we get a lot of support requests every week. If you can reduce the problem
     to a clear set of steps to reproduce or an example project that fails in a fresh environment, please re-open the ticket
     with that information.
-    
+
 Problem in application code
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

docs/topics/channel_layers.rst

@@ -11,7 +11,7 @@ to make a basic task queue or to offload tasks - read more in
 
 Channels does not ship with any channel layers you can use out of the box, as
 each one depends on a different way of transporting data across a network. We
-would recommend you use ``channels_redis``, which is an offical Django-maintained
+would recommend you use ``channels_redis``, which is an official Django-maintained
 layer that uses Redis as a transport and what we'll focus the examples on here.
 
 .. note::

docs/topics/routing.rst

@@ -22,7 +22,7 @@ more protocol-specific routing underneath there.
 
 Channels expects you to be able to define a single *root application*, and
 provide the path to it as the ``ASGI_APPLICATION`` setting (think of this as
-being analagous to the ``ROOT_URLCONF`` setting in Django). There's no fixed
+being analogous to the ``ROOT_URLCONF`` setting in Django). There's no fixed
 rule as to where you need to put the routing and the root application,
 but we recommend putting them in a project-level file called ``routing.py``,
 next to ``urls.py``. You can read more about deploying Channels projects and