Merge pull request #30 from sikanderiqbal/patch-1

Minor typos fix

Author: nekudo

README.md

@@ -63,13 +63,13 @@ $server->registerApplication('chat', \Bloatless\WebSocket\Examples\Application\C
 $server->run();
 ```
 
-Assuming this code is in a file called `server.php` you can than start your server with the following command:
+Assuming this code is in a file called `server.php` you can then start your server with the following command:
 
 ```shell
 php server.php
 ```
 
-The websocket server will than listen for new connection on the provided host and port. By default, this will be
+The websocket server will then listen for new connections on the provided host and port. By default, this will be
 `localhost:8000`.
 
 This repositoy also includes a working example in [examples/server.php](examples/server.php)
@@ -94,15 +94,15 @@ interface ApplicationInterface
 }
 ```
 
-`onConnet` and `onDisconnect` can be used to keep track of all the clients connected to your application. `onData` will
-be called whenever the websocket server receives new data from one of the clients connect to the application. 
+`onConnect` and `onDisconnect` can be used to keep track of all the clients connected to your application. `onData` will
+be called whenever the websocket server receives new data from one of the clients connected to the application. 
 `onIPCData` will be called if data is provided by another process on your machine. (See [Push-Client (IPC)](#push-client-ipc))
 
 A working example of an application can be found in [examples/Application/Chat.php](examples/Application/Chat.php)
 
 ### Timers
 
-A common requirement to long-running processes such as a websocket server is to execute tasks periodically. This can
+A common requirement for long-running processes such as a websocket server is to execute tasks periodically. This can
 be done using timers. Timers can execute methods within your server or application periodically. Here is an example:
 
 ```php
@@ -119,12 +119,12 @@ This example would call the method `someMethod` within your chat application eve
 ### Push-Client (IPC)
 
 It is often required to push data into the websocket-server process from another application. Let's assume you run a
-website containg a chat and an area containing news or a blog. Now every time a new article is published in your blog
+website containing a chat and an area containing news or a blog. Now every time a new article is published in your blog
 you want to notify all users currently in your chat. To achieve this you somehow need to push data from your blog
 logic into the websocket server. This is where the Push-Client comes into play.
 
 When starting the websocket server, it opens a unix-domain-socket and listens for new messages. The Push-Client can
-than be used to send these messages. Here is an example:
+then be used to send these messages. Here is an example:
 
 ```php
 $pushClient = new \Bloatless\WebSocket\PushClient('//tmp/phpwss.sock');
@@ -134,17 +134,16 @@ $pushClient->sendToApplication('chat', [
 ]);
 ```
 
-This code pushes data into your running websocket-server process. In this case the `echo` Method within the
-chat-application is called and sends the provided message to all connected clients.
+This code pushes data into your running websocket-server process. In this case the `echo` method within the
+chat-application is called and it sends the provided message to all connected clients.
 
 You can find the full working example in: [examples/push.php](examples/push.php)
 
-**Important Hint:** Push messages can be not larger than 64kb!
+**Important Hint:** Push messages cannot be larger than 64kb!
 
 ### Client (Browser/JS)
 
-Everything above this point was related to the server-side of things. But how to connect to the server from your
-browser?
+Everything above this point was related to the server-side of things. But how to connect to the server from your browser?
 
 Here is a simple example:
 
@@ -168,8 +167,8 @@ A better example of the chat client can be found in: [examples/public/chat.html]
 
 ## Intended use and limitations
 
-This project was mainly build for educational purposes. The code is relatively simple and easy to understand. This
-server was **not tested in production**, so I strongly recommand to not use it on a live project. It should be totally
+This project was mainly built for educational purposes. The code is relatively simple and easy to understand. This
+server was **not tested in production**, so I strongly recommend not to use it in a live project. It should be totally
 fine for small educational projects or internal tools, but most probably will not handle huge amounts of traffic or
 connections very well.