--- cvsroot/AnyEvent-MP/MP.pm	2009/08/14 15:13:20	1.52
+++ cvsroot/AnyEvent-MP/MP.pm	2009/08/14 15:31:21	1.53
@@ -25,7 +25,7 @@
    snd @msg_with_first_element_being_a_port;
 
    # creating/using ports, the simple way
-   my $somple_port = port { my @msg = @_; 0 };
+   my $simple_port = port { my @msg = @_; 0 };
 
    # creating/using ports, tagged message matching
    my $port = port;
@@ -71,22 +71,21 @@
 
 A port is something you can send messages to (with the C<snd> function).
 
-Some ports allow you to register C<rcv> handlers that can match specific
-messages. All C<rcv> handlers will receive messages they match, messages
-will not be queued.
+Ports allow you to register C<rcv> handlers that can match all or just
+some messages. Messages will not be queued.
 
 =item port id - C<noderef#portname>
 
-A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as
+A port ID is the concatenation of a noderef, a hash-mark (C<#>) as
 separator, and a port name (a printable string of unspecified format). An
 exception is the the node port, whose ID is identical to its node
 reference.
 
 =item node
 
-A node is a single process containing at least one port - the node
-port. You can send messages to node ports to find existing ports or to
-create new ports, among other things.
+A node is a single process containing at least one port - the node port,
+which provides nodes to manage each other remotely, and to create new
+ports.
 
 Nodes are either private (single-process only), slaves (connected to a
 master node only) or public nodes (connectable from unrelated nodes).