--- AnyEvent/lib/AnyEvent/Handle.pm	2011/08/25 03:08:48	1.222
+++ AnyEvent/lib/AnyEvent/Handle.pm	2011/09/01 04:07:18	1.223
@@ -1130,7 +1130,7 @@
 the handle object and the remaining arguments.
 
 The function is supposed to return a single octet string that will be
-appended to the write buffer, so you cna mentally treat this function as a
+appended to the write buffer, so you can mentally treat this function as a
 "arguments to on-the-wire-format" converter.
 
 Example: implement a custom write type C<join> that joins the remaining
@@ -2206,7 +2206,7 @@
 considered an error as you clearly expected some data.
 
 To avoid this, make sure you have an empty read queue whenever your handle
-is supposed to be "idle" (i.e. connection closes are O.K.). You cna set
+is supposed to be "idle" (i.e. connection closes are O.K.). You can set
 an C<on_read> handler that simply pushes the first read requests in the
 queue.
 
@@ -2247,7 +2247,7 @@
 
 The second variant is a protocol where the client can drop the connection
 at any time. For TCP, this means that the server machine may run out of
-sockets easier, and in general, it means you cnanot distinguish a protocl
+sockets easier, and in general, it means you cannot distinguish a protocl
 failure/client crash from a normal connection close. Nevertheless, these
 kinds of protocols are common (and sometimes even the best solution to the
 problem).