--- AnyEvent-MP/MP.pm	2009/09/07 18:33:44	1.81
+++ AnyEvent-MP/MP.pm	2009/09/08 01:38:16	1.83
@@ -99,20 +99,32 @@
 endpoints - binds. Currently, only standard C<ip:port> specifications can
 be used, which specify TCP ports to listen on.
 
-=item seeds - C<host:port>
+=item seed nodes
 
 When a node starts, it knows nothing about the network. To teach the node
 about the network it first has to contact some other node within the
 network. This node is called a seed.
 
-Seeds are transport endpoint(s) of as many nodes as one wants. Those nodes
-are expected to be long-running, and at least one of those should always
-be available. When nodes run out of connections (e.g. due to a network
-error), they try to re-establish connections to some seednodes again to
-join the network.
+Apart from the fact that other nodes know them as seed nodes and they have
+to have fixed listening addresses, seed nodes are perfectly normal nodes -
+any node can function as a seed node for others.
+
+In addition to discovering the network, seed nodes are also used to
+maintain the network and to connect nodes that otherwise would have
+trouble connecting. They form the backbone of the AnyEvent::MP network.
+
+Seed nodes are expected to be long-running, and at least one seed node
+should always be available.
+
+=item seeds - C<host:port>
+
+Seeds are transport endpoint(s) (usually a hostname/IP address and a
+TCP port) of nodes thta should be used as seed nodes.
 
-Apart from being sued for seeding, seednodes are not special in any way -
-every public node can be a seednode.
+The nodes listening on those endpoints are expected to be long-running,
+and at least one of those should always be available. When nodes run out
+of connections (e.g. due to a network error), they try to re-establish
+connections to some seednodes again to join the network.
 
 =back
 
@@ -623,7 +635,9 @@
 exists or it runs out of package names.
 
 The init function is then called with the newly-created port as context
-object (C<$SELF>) and the C<@initdata> values as arguments.
+object (C<$SELF>) and the C<@initdata> values as arguments. It I<must>
+call one of the C<rcv> functions to set callbacks on C<$SELF>, otherwise
+the port might not get created.
 
 A common idiom is to pass a local port, immediately monitor the spawned
 port, and in the remote init function, immediately monitor the passed
@@ -657,6 +671,7 @@
    my $port = shift;
    my $init = shift;
 
+   # rcv will create the actual port
    local $SELF = "$NODE#$port";
    eval {
       &{ load_func $init }