From d56cb60935dabb51028e6a9ba562c465735bcf85 Mon Sep 17 00:00:00 2001 From: Nick Date: Wed, 5 Mar 2014 12:16:55 -0500 Subject: [PATCH] spelling and flow --- README.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 08c90a7..a1c3f68 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,3 @@ - WebSocket-multiplex =================== @@ -76,7 +75,7 @@ directory. Protocol -------- -The underlying protocol is quite simple. Each message consists of +The underlying protocol is quite simple. Each message is a string consisting of three comma separated parts: _type_, _topic_ and _payload_. There are three valid message types: @@ -87,11 +86,11 @@ three valid message types: Invalid messages like wrong unsubscriptions or publishes to a _topic_ to which a client was not subscribed to are simply ignored. -This protocol assumes that both parties are genrally willing to -copperate and no party can express any kind of errors. All invalid +This protocol assumes that both parties are generally willing to +cooperate and that no party makes errors. All invalid messages should be ignored. It's important to notice that the namespace is shared between both -parties and it is not a good idea to use the same topic names on the -client and on the server side. Both parties may express a will to -unsubscribe itself or other party from a topic. +parties. It is not a good idea to use the same topic names on the +client and on the server side because both parties may unsubscribe +the other from a topic.