--- AnyEvent-MP/MP.pm	2012/10/02 13:58:07	1.145
+++ AnyEvent-MP/MP.pm	2016/06/20 08:19:19	1.146
@@ -120,7 +120,7 @@
 
 Currently, only standard C<ip:port> specifications can be used, which
 specify TCP ports to listen on. So a bind is basically just a tcp socket
-in listening mode thta accepts conenctions form other nodes.
+in listening mode that accepts conenctions form other nodes.
 
 =item seed nodes
 
@@ -130,7 +130,7 @@
 
 Seed nodes themselves are not special - they are seed nodes only because
 some other node I<uses> them as such, but any node can be used as seed
-node for other nodes, and eahc node cna use a different set of seed nodes.
+node for other nodes, and eahc node can use a different set of seed nodes.
 
 In addition to discovering the network, seed nodes are also used to
 maintain the network - all nodes using the same seed node form are part of
@@ -170,7 +170,7 @@
 node and tries to keep connections to all other nodes. So while it can
 make sense to make every node "global" in small networks, it usually makes
 sense to only make seed nodes into global nodes in large networks (nodes
-keep connections to seed nodes and global nodes, so makign them the same
+keep connections to seed nodes and global nodes, so making them the same
 reduces overhead).
 
 =back
@@ -1059,8 +1059,8 @@
 
 =item $guard = db_mon $family => $cb->(\%familyhash, \@added, \@changed, \@deleted)
 
-Creates a monitor on the given database family. Each time a key is set
-or or is deleted the callback is called with a hash containing the
+Creates a monitor on the given database family. Each time a key is
+set or is deleted the callback is called with a hash containing the
 database family and three lists of added, changed and deleted subkeys,
 respectively. If no keys have changed then the array reference might be
 C<undef> or even missing.
@@ -1098,9 +1098,9 @@
       print "My::Module::workers now nonempty\n";
    };
 
-Example: print all changes to the family "AnyRvent::Fantasy::Module".
+Example: print all changes to the family "AnyEvent::Fantasy::Module".
 
-   my $guard = db_mon AnyRvent::Fantasy::Module => sub {
+   my $guard = db_mon AnyEvent::Fantasy::Module => sub {
       my ($family, $a, $c, $d) = @_;
 
       print "+$_=$family->{$_}\n" for @$a;
@@ -1161,7 +1161,7 @@
 This is not a philosophical difference, but simply stems from AnyEvent::MP
 being event-based, while Erlang is process-based.
 
-You cna have a look at L<Coro::MP> for a more Erlang-like process model on
+You can have a look at L<Coro::MP> for a more Erlang-like process model on
 top of AEMP and Coro threads.
 
 =item * Erlang sends are synchronous, AEMP sends are asynchronous.
@@ -1379,7 +1379,7 @@
 
 =head1 LOGGING
 
-AnyEvent::MP does not normally log anything by itself, but sinc eit is the
+AnyEvent::MP does not normally log anything by itself, but since it is the
 root of the contetx hierarchy for AnyEvent::MP modules, it will receive
 all log messages by submodules.