Integrate with Sarathy. perl.h and util.c required manual resolving.

[perl5.git] / pod / perldebug.pod

diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index 7a6e814..5699732 100644 (file)
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -557,7 +557,7 @@ Quit.  ("quit" doesn't work for this.)  This is the only supported way
 to exit the debugger, though typing C<exit> twice may do it too.
 
 Set an C<O>ption C<inhibit_exit> to 0 if you want to be able to I<step
-off> the end the script.  You may also need to set C<$finished> to 0 at
+off> the end the script.  You may also need to set $finished to 0 at
 some moment if you want to step through global destruction.
 
 =item R
@@ -754,8 +754,8 @@ for different values of C<n>:
   in  @=Config::myconfig() from /dev/nul:0
    in  $=Config::FETCH(ref(Config), 'package') from lib/Config.pm:574
    in  $=Config::FETCH(ref(Config), 'baserev') from lib/Config.pm:574
-   in  $=Config::FETCH(ref(Config), 'PATCHLEVEL') from lib/Config.pm:574
-   in  $=Config::FETCH(ref(Config), 'SUBVERSION') from lib/Config.pm:574
+   in  $=Config::FETCH(ref(Config), 'PERL_VERSION') from lib/Config.pm:574
+   in  $=Config::FETCH(ref(Config), 'PERL_SUBVERSION') from lib/Config.pm:574
    in  $=Config::FETCH(ref(Config), 'osname') from lib/Config.pm:574
    in  $=Config::FETCH(ref(Config), 'osvers') from lib/Config.pm:574
 
@@ -779,9 +779,9 @@ for different values of C<n>:
    out $=Config::FETCH(ref(Config), 'package') from lib/Config.pm:574
    in  $=Config::FETCH(ref(Config), 'baserev') from lib/Config.pm:574
    out $=Config::FETCH(ref(Config), 'baserev') from lib/Config.pm:574
-   in  $=Config::FETCH(ref(Config), 'PATCHLEVEL') from lib/Config.pm:574
-   out $=Config::FETCH(ref(Config), 'PATCHLEVEL') from lib/Config.pm:574
-   in  $=Config::FETCH(ref(Config), 'SUBVERSION') from lib/Config.pm:574
+   in  $=Config::FETCH(ref(Config), 'PERL_VERSION') from lib/Config.pm:574
+   out $=Config::FETCH(ref(Config), 'PERL_VERSION') from lib/Config.pm:574
+   in  $=Config::FETCH(ref(Config), 'PERL_SUBVERSION') from lib/Config.pm:574
 
 =item 14
 
@@ -968,7 +968,7 @@ application.
 
 The array C<@{"_E<lt>$filename"}> is the line-by-line contents of
 $filename for all the compiled files.  Same for C<eval>ed strings which
-contain subroutines, or which are currently executed.  The C<$filename>
+contain subroutines, or which are currently executed.  The $filename
 for C<eval>ed strings looks like C<(eval 34)>.
 
 =item *
@@ -1109,7 +1109,7 @@ or B<pop>, the stack backtrace will not show the original values.
 
 Perl is I<very> frivolous with memory.  There is a saying that to
 estimate memory usage of Perl, assume a reasonable algorithm of
-allocation, and multiply your estimages by 10.  This is not absolutely
+allocation, and multiply your estimates by 10.  This is not absolutely
 true, but may give you a good grasp of what happens.
 
 Say, an integer cannot take less than 20 bytes of memory, a float
@@ -1161,7 +1161,7 @@ in the following example:
   Total sbrk(): 215040/47:145. Odd ends: pad+heads+chain+tail: 0+2192+0+6144.
 
 It is possible to ask for such a statistic at arbitrary moment by
-usind Devel::Peek::mstats() (module Devel::Peek is available on CPAN).
+using Devel::Peek::mstats() (module Devel::Peek is available on CPAN).
 
 Here is the explanation of different parts of the format:
 
@@ -1195,7 +1195,7 @@ memory footprints of the buckets are between memory footprints of two
 buckets "above".  
 
 Say, with the above example the memory footprints are (with current
-algorith)
+algorithm)
 
      free:    8     16    32    64    128  256 512 1024 2048 4096 8192
           4     12    24    48    80
@@ -1328,7 +1328,7 @@ though the subroutine itself is not defined yet).
 
 It also creates C arrays to keep data for the stash (this is one HV,
 but it grows, thus there are 4 big allocations: the big chunks are not
-freeed, but are kept as additional arenas for C<SV> allocations).
+freed, but are kept as additional arenas for C<SV> allocations).
 
 =item C<054>