Fix typos (#1322)

Author: minho42

CHANGELOG.txt

@@ -38,7 +38,7 @@ https://channels.readthedocs.io/en/latest/releases
 ------------------
 
 * Django middleware is now cached rather than instantiated per request
-  resulting in a sigificant speed improvement
+  resulting in a significant speed improvement
 
 * ChannelServerLiveTestCase now serves static files again
 

channels/consumer.py

@@ -40,7 +40,7 @@ async def __call__(self, receive, send):
         """
         Dispatches incoming messages to type-based handlers asynchronously.
         """
-        # Initalize channel layer
+        # Initialize channel layer
         self.channel_layer = get_channel_layer(self.channel_layer_alias)
         if self.channel_layer is not None:
             self.channel_name = await self.channel_layer.new_channel()

channels/http.py

@@ -235,7 +235,7 @@ def handle(self, body):
             )
             response = http.HttpResponseBadRequest()
         except RequestTimeout:
-            # Parsing the rquest failed, so the response is a Request Timeout error
+            # Parsing the request failed, so the response is a Request Timeout error
             response = HttpResponse("408 Request Timeout (upload too slow)", status=408)
         except RequestAborted:
             # Client closed connection on us mid request. Abort!

channels/layers.py

@@ -112,7 +112,7 @@ def compile_capacities(self, channel_capacity):
         """
         result = []
         for pattern, value in channel_capacity.items():
-            # If they passed in a precompiled regex, leave it, else intepret
+            # If they passed in a precompiled regex, leave it, else interpret
             # it as a glob.
             if hasattr(pattern, "match"):
                 result.append((pattern, value))

docs/asgi.rst

@@ -7,7 +7,7 @@ Channels and Daphne are built upon, designed to untie Channels apps from a
 specific application server and provide a common way to write application
 and middleware code.
 
-It's a spiritual successor to WSGI, designed not only run in an asychronous
+It's a spiritual successor to WSGI, designed not only run in an asynchronous
 fashion via ``asyncio``, but also supporting multiple protocols.
 
 The full ASGI spec can be found at http://asgi.readthedocs.io

docs/contributing.rst

@@ -74,7 +74,7 @@ your environment::
     pip install -e .[tests]
 
 Note the ``[tests]`` section there; that tells ``pip`` that you want to install
-the ``tests`` extra, which will bring in testing depedencies like
+the ``tests`` extra, which will bring in testing dependencies like
 ``pytest-django``.
 
 Then, you can run the tests::

docs/one-to-two.rst

@@ -82,7 +82,7 @@ Full Async
 Channels 2 is also built on a fundamental async foundation, and all servers
 are actually running an asynchronous event loop and only jumping to synchronous
 code when you interact with the Django view system or ORM. That means that
-you, too, can write fully asychronous code if you wish.
+you, too, can write fully asynchronous code if you wish.
 
 It's not a requirement, but it's there if you need it. We also provide
 convenience methods that let you jump between synchronous and asynchronous

docs/releases/2.1.4.rst

@@ -8,7 +8,7 @@ Bugfixes & Small Changes
 ------------------------
 
 * Django middleware is now cached rather than instantiated per request
-  resulting in a sigificant speed improvement. Some middleware took seconds to
+  resulting in a significant speed improvement. Some middleware took seconds to
   load and as a result Channels was unusable for HTTP serving before.
 
 * ChannelServerLiveTestCase now serves static files again.

docs/support.rst

@@ -32,7 +32,7 @@ environments.
 First off, try changing your production environment to see if that helps - for example, if you have Nginx/Apache/etc.
 between browsers and Channels, try going direct to the Python server and see if that fixes things. Turn SSL off if you
 have it on. Try from different browsers and internet connections. WebSockets are notoriously hard to debug already,
-and so you should expect some level of akwardness from any project involving them.
+and so you should expect some level of awkwardness from any project involving them.
 
 Next, check package versions between your local and remote environments. You'd be surprised how easy it is to forget
 to upgrade something!

docs/topics/routing.rst

@@ -130,5 +130,5 @@ applications that serve them::
 
     ChannelNameRouter({
         "thumbnails-generate": some_app,
-        "thunbnails-delete": some_other_app,
+        "thumbnails-delete": some_other_app,
     })