--- AnyEvent-MP/MP.pm	2009/08/30 18:51:49	1.69
+++ AnyEvent-MP/MP.pm	2009/08/30 19:49:47	1.70
@@ -180,12 +180,12 @@
 The function first looks up the profile in the aemp configuration (see the
 L<aemp> commandline utility). the profile is calculated as follows:
 
-First, all remaining key => value pairs will be used. Then they will be
-overwritten by any values specified in the global default configuration
-(see the F<aemp> utility), then the chain of profiles selected, if
-any. That means that the values specified in the profile have highest
-priority and the values specified via C<initialise_node> have lowest
-priority.
+First, all remaining key => value pairs (all of which are conviniently
+undocumented at the moment) will be used. Then they will be overwritten by
+any values specified in the global default configuration (see the F<aemp>
+utility), then the chain of profiles selected, if any. That means that
+the values specified in the profile have highest priority and the values
+specified via C<initialise_node> have lowest priority.
 
 If the profile specifies a node ID, then this will become the node ID of
 this process. If not, then the profile name will be used as node ID. The
@@ -197,9 +197,8 @@
 outside. This means the node cannot talk to other nodes that also have no
 binds, but it can still talk to all "normal" nodes).
 
-If the profile does not specify a binds list, then the node ID will be
-treated as if it were of the form C<host:port>, which will be resolved and
-used as binds list.
+If the profile does not specify a binds list, then a default of C<*> is
+used.
 
 Lastly, the seeds list from the profile is passed to the
 L<AnyEvent::MP::Global> module, which will then use it to keep