Another Pod fix

lib/POE/Component/IRC/Plugin/DCC.pm

@@ -325,12 +325,9 @@ sub _event_dcc_close {
         return;
     }
 
+    # pending data, wait till it has been flushed
     if ($self->{dcc}->{$id}->{wheel}->get_driver_out_octets()) {
-        $kernel->delay_set(
-            '_event_dcc_close',
-            2,
-            $id,
-        );
+        $kernel->delay_set(_event_dcc_close => 2, $id);
         return;
     }
 
@@ -686,8 +683,9 @@ is the request timeout value in seconds (default: 300).
 
 Incidentally, you can send other weird nonstandard kinds of DCCs too;
 just put something besides 'SEND' or 'CHAT' (say, 'FOO') in the type
-field, and you'll get back C<irc_dcc_foo> events when activity happens
-on its DCC connection.
+field, and you'll get back C<irc_dcc_foo> events (with same arguments as
+L<C<irc_dcc_chat>|/"irc_dcc_chat"> when activity happens on its DCC
+connection.
 
 If you are behind a firewall or Network Address Translation, you may want to
 consult L<POE::Component::IRC|POE::Component::IRC>'s

lib/POE/Component/IRC/Plugin/Logger.pm

@@ -414,8 +414,8 @@ logs public and private messages to disk
 =head1 DESCRIPTION
 
 POE::Component::IRC::Plugin::Logger is a L<POE::Component::IRC|POE::Component::IRC>
-plugin. It logs messages and CTCP ACTIONs to either C<#some_channel.log> or
-C<some_nickname.log> in the supplied path. In the case of DCC chats, a '=' is 
+plugin. It logs messages and CTCP ACTIONs to either F<#some_channel.log> or
+F<some_nickname.log> in the supplied path. In the case of DCC chats, a '=' is 
 prepended to the nickname (like in irssi).
 
 The plugin tries to detect UTF-8 encoding of every message or else falls back