diff --git a/README.md b/README.md
index 2a5ab3a..2c62937 100644
--- a/README.md
+++ b/README.md
@@ -36,23 +36,24 @@ subdirectory](https://github.com/gorilla/websocket/tree/master/examples/autobahn
RFC 6455 Features |
Passes Autobahn Test Suite | Yes | No |
-Receive fragmented message | Yes | No |
+Receive fragmented message | Yes | No, see note 1 |
Send close message | Yes | No |
Send pings and receive pongs | Yes | No |
Get the type of a received data message | Yes | Yes, see note 2 |
Other Features |
Limit size of received message | Yes | No |
-Read message using io.Reader | Yes | No, see note 1 |
-Write message using io.WriteCloser | Yes | No, see note 1 |
-Encode, decode JSON message | Yes | Yes |
+Read message using io.Reader | Yes | No, see note 3 |
+Write message using io.WriteCloser | Yes | No, see note 3 |
Notes:
-1. The go.net io.Reader and io.Writer operate across WebSocket frame boundaries.
- Read returns when the input buffer is full or a frame boundary is
- encountered, Each call to Write sends a single frame message. The Gorilla
- io.Reader and io.WriteCloser operate on a single WebSocket message.
+1. Chrome's [new WebSocket implementation](http://www.ietf.org/mail-archive/web/hybi/current/msg10503.html) fragments large messages.
2. The application can get the type of a received data message by implementing
a [Codec marshal](http://godoc.org/code.google.com/p/go.net/websocket#Codec.Marshal)
function.
+3. The go.net io.Reader and io.Writer operate across WebSocket frame boundaries.
+ Read returns when the input buffer is full or a frame boundary is
+ encountered, Each call to Write sends a single frame message. The Gorilla
+ io.Reader and io.WriteCloser operate on a single WebSocket message.
+