--- AnyEvent-MP/MP.pm	2012/03/21 23:48:39	1.137
+++ AnyEvent-MP/MP.pm	2012/03/22 00:48:29	1.138
@@ -1319,11 +1319,12 @@
 except when you need the lower latency of an already established
 connection. To ensure a node establishes a connection to another node,
 you can monitor the node port (C<mon $node, ...>), which will attempt to
-create the connection (And notify you when the connection fails).
+create the connection (and notify you when the connection fails).
 
-=item Listener-less nodes are gone.
+=item Listener-less nodes (nodes without binds) are gone.
 
-And are not coming back, at least not in their old form.
+And are not coming back, at least not in their old form. If no C<binds>
+are specified for a node, AnyEvent::MP now assumes a default of C<*:*>.
 
 There are vague plans to implement some form of routing domains, which
 might or might not bring back listener-less nodes, but don't count on it.
@@ -1333,6 +1334,18 @@
 problems, as long as it isn't a global node and only reaches out to other
 nodes (as opposed to being contacted from other nodes).
 
+=item $AnyEvent::MP::Kernel::WARN has gone.
+
+AnyEvent has acquired a logging framework (L<AnyEvent::Log>), and AEMP now
+uses this, and so should your programs.
+
+Every module now documents what kinds of messages it generates, with
+AnyEvent::MP acting as a catch all.
+
+On the positive side, this means that instead of setting
+C<PERL_ANYEVENT_MP_WARNLEVEL>, you can get away by setting C<AE_VERBOSE>,
+much less to type.
+
 =back
 
 =head1 SEE ALSO