Merge pull request #254 from orn688/patch-1

Fix typos in README.md

README.md

@@ -29,15 +29,15 @@ New in 0.4.5
 Features
 --------
 * Largely scalable for Django applications with many hundreds of open websocket connections.
-* Runs a seperate Django main loop in a cooperative concurrency model using [gevent](http://www.gevent.org/),
+* Runs a separate Django main loop in a cooperative concurrency model using [gevent](http://www.gevent.org/),
   thus only one thread/process is required to control *all* open websockets simultaneously.
-* Full control over this seperate main loop during development, so **Django** can be started as usual with
+* Full control over this separate main loop during development, so **Django** can be started as usual with
   ``./manage.py runserver``.
 * No dependency to any other asynchronous event driven framework, such as Tornado, Twisted or
   Socket.io/Node.js.
-* Normal Django requests communicate with this seperate main loop through **Redis** which, by the way is a good
+* Normal Django requests communicate with this separate main loop through **Redis** which, by the way is a good
   replacement for memcached.
-* Optionally persiting messages, allowing server reboots and client reconnections.
+* Optionally persisting messages, allowing server reboots and client reconnections.
 
 If unsure, if this proposed architecture is the correct approach on how to integrate Websockets with Django, then
 please read Roberto De Ioris (BDFL of uWSGI) article about