--- cvsroot/AnyEvent-Porttracker/Porttracker.pm	2010/11/16 02:07:31	1.10
+++ cvsroot/AnyEvent-Porttracker/Porttracker.pm	2010/11/16 02:09:00	1.11
@@ -165,8 +165,8 @@
 
 =item on_XYZ => $coderef
 
-You can specify event callbacks either by subclassing and overriding the
-respective methods or by specifying coderefs as key-value pairs when
+You can specify event callbacks either by sub-classing and overriding the
+respective methods or by specifying code-refs as key-value pairs when
 constructing the object. You add or remove event handlers at any time with
 the C<event> method.
 
@@ -180,7 +180,7 @@
    my $self = bless {
       id    => "a",
       ids   => [],
-      queue => [], # ininitially queue everything
+      queue => [], # initially queue everything
       @_,
    }, $class;
 
@@ -467,12 +467,12 @@
 
 =head1 EVENTS
 
-AnyEvent::Porttracker conenctions are fully event-driven, and naturally
+AnyEvent::Porttracker connections are fully event-driven, and naturally
 there are a number of events that can occur. All these events have a name
 starting with C<on_> (example: C<on_login_failure>).
 
 Programs can catch these events in two ways: either by providing
-constructor arguments with the event name as key and a coderef as value:
+constructor arguments with the event name as key and a code-ref as value:
 
    my $api = new AnyEvent::Porttracker
       host => ...,
@@ -484,7 +484,7 @@
       },
    ;
 
-Or by subclassing C<AnyEvent::Porttracker> and overriding methods of the
+Or by sub-classing C<AnyEvent::Porttracker> and overriding methods of the
 same name:
 
    package MyClass;
@@ -542,7 +542,7 @@
 
 Called when the server wants to start TLS negotiation. This is used
 internally and - while it is possible to override it - should not be
-overriden.
+overridden.
 
 =item on_event_notify $api, $eventname, @args