--- AnyEvent-MP/MP.pm	2009/09/07 18:42:09	1.82
+++ AnyEvent-MP/MP.pm	2009/09/09 01:47:01	1.86
@@ -85,7 +85,7 @@
 (no listening ports). Private nodes cannot talk to other private nodes
 currently.
 
-=item node ID - C<[a-za-Z0-9_\-.:]+>
+=item node ID - C<[A-Z_][a-zA-Z0-9_\-.:]*>
 
 A node ID is a string that uniquely identifies the node within a
 network. Depending on the configuration used, node IDs can look like a
@@ -99,20 +99,33 @@
 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 an AnyEvent::MP network.
+
+Seed nodes are expected to be long-running, and at least one seed node
+should always be available. They should also be relatively responsive - a
+seed node that blocks for long periods will slow down everybody else.
+
+=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