stab at UNITCHECK blocks

Message-ID: <20061019120412.GA12290@the.earth.li>

p4raw-id: //depot/perl@29053

1 files changed, 6 insertions, 6 deletions

diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index 2e21941db0..390eb96782 100644
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -956,12 +956,12 @@ for incredibly long examples of these.
 =head2 Debugging compile-time statements
 
 If you have compile-time executable statements (such as code within
-BEGIN and CHECK blocks or C<use> statements), these will I<not> be
-stopped by debugger, although C<require>s and INIT blocks will, and
-compile-time statements can be traced with C<AutoTrace> option set
-in C<PERLDB_OPTS>).  From your own Perl code, however, you can
-transfer control back to the debugger using the following statement,
-which is harmless if the debugger is not running:
+BEGIN, UNITCHECK and CHECK blocks or C<use> statements), these will
+I<not> be stopped by debugger, although C<require>s and INIT blocks
+will, and compile-time statements can be traced with C<AutoTrace>
+option set in C<PERLDB_OPTS>).  From your own Perl code, however, you
+can transfer control back to the debugger using the following
+statement, which is harmless if the debugger is not running:
 
     $DB::single = 1;