Minor README tweaks

TooTallNate · TooTallNate · commit eaba3cf0ebdd · 2010-08-01T11:19:04.000-07:00
diff --git a/README.markdown b/README.markdown
@@ -2,7 +2,7 @@ Java WebSockets
 ===============
 
 This repository contains a barebones WebSocket server and client implementation
-written 100% in in Java. The implementation supports both the older draft 75,
+written in 100% Java. The implementation supports both the older draft 75,
 and current draft 76. The underlying classes use the Java
 `ServerSocketChannel` and `SocketChannel` classes, which allows for a
 non-blocking event-driven model (similar to the
@@ -15,15 +15,16 @@ There's a simple chat server and client example located in the `example`
 folder. First, compile the example classes and JAR file:
     ant
 
-Then, start the chat server (a WebSocketServer subclass):
+Then, start the chat server (a `WebSocketServer` subclass):
     java -cp example:dist/WebSocket.jar ChatServer
 
 Now that the server is started, we need to connect some clients. Run the
-Java chat client (a WebSocketClient subclass):
+Java chat client (a `WebSocketClient` subclass):
     java -cp example:dist/WebSocket.jar ChatClient
 
-The chat client is a simple Swing GUI that allows you to send messages to
-all other connected clients, and receive messages from others in a text box.
+The chat client is a simple Swing GUI application that allows you to send
+messages to all other connected clients, and receive messages from others in a
+text box.
 
 There's also a simple HTML file chat client `chat.html`, which can be opened
 by any browser. If the browser natively supports the WebSocket API, then it's
@@ -33,7 +34,7 @@ implementation will be used, otherwise it will fall back to a
 Writing your own WebSocket Server
 ---------------------------------
 
-The `net.tootallnate.websocket.WebSocketServer` class implements the
+The `net.tootallnate.websocket.WebSocketServer` abstract class implements the
 server-side of the
 [WebSocket Protocol](<http://www.whatwg.org/specs/web-socket-protocol/>).
 A WebSocket server by itself doesn't do anything except establish socket
@@ -42,10 +43,11 @@ connections though HTTP. After that it's up to **your** subclass to add purpose.
 Writing your own WebSocket Client
 ---------------------------------
 
-The `net.tootallnate.websocket.WebSocketClient` class can connect to valid
-WebSocket servers. The constructor expects a valid `ws://` URI to connect to.
-Important events `onOpen`, `onClose`, and `onMessage` get fired throughout the
-life of the WebSocketClient, and must be implemented in your subclass.
+The `net.tootallnate.websocket.WebSocketClient` abstract class can connect to
+valid WebSocket servers. The constructor expects a valid `ws://` URI to
+connect to. Important events `onOpen`, `onClose`, and `onMessage` get fired
+throughout the life of the WebSocketClient, and must be implemented in **your**
+subclass.
 
 License
 -------
