From eede60f16ac11ce899f42159f6a2bf86ecc6b477 Mon Sep 17 00:00:00 2001
From: Bronson Zgeb <bronson.zgeb@gmail.com>
Date: Wed, 18 Jul 2012 17:16:33 -0400
Subject: [PATCH] fixed typos

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 7d2a66f..9951209 100644
--- a/README.md
+++ b/README.md
@@ -170,7 +170,7 @@ message exchange (protocol security, namespace, protocol version, transport, etc
 
 Messages can be sent and received by following this convention. **How** the messages
 are encoded and framed depends on each transport, but generally boils down to
-whether the transport has built-in framing (unidiretionally and/or bidirectionally).
+whether the transport has built-in framing (unidirectionally and/or bidirectionally).
 
 ### Unidirectional transports
 
@@ -190,7 +190,7 @@ For `xhr-multipart`, the built-in MIME framing is used for the sake of consisten
 When no built-in lightweight framing is available, and multiple messages need to be
 delivered (i.e: buffered messages), the following is used:
 
-    `\ufffd` [message lenth] `\ufffd`
+    `\ufffd` [message length] `\ufffd`
 
 Transports where the framing overhead is expensive (ie: when the xhr-polling
 transport tries to send data to the server).
@@ -249,7 +249,7 @@ the server might want to respond with a error packet.
 Sends a heartbeat. Heartbeats must be sent within the interval negotiated with
 the server. It's up to the client to decide the padding (for example, if the
 heartbeat timeout negotiated with the server is 20s, the client might want to
-send a heartbeat evert 15s).
+send a heartbeat every 15s).
 
 ### (`3`) Message