summaryrefslogtreecommitdiff
path: root/pod/perldebguts.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-05-28 08:31:20 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-05-28 08:31:20 +0000
commitb9449ee00d2461c5a220b8b0cd7ee22c0d775f7c (patch)
tree2b79914b6a33b8a2ae55536a7fc9e17d51e6e0af /pod/perldebguts.pod
parent0a931e4af3dba6f23d436823d4526d6b7bdc2249 (diff)
downloadperl-b9449ee00d2461c5a220b8b0cd7ee22c0d775f7c.tar.gz
random pod typos (from Peter Scott <Peter@PSDT.com>)
p4raw-id: //depot/perl@6136
Diffstat (limited to 'pod/perldebguts.pod')
-rw-r--r--pod/perldebguts.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod
index 45c33c7ec4..5812a40fcb 100644
--- a/pod/perldebguts.pod
+++ b/pod/perldebguts.pod
@@ -639,7 +639,7 @@ than 32 bytes (all these examples assume 32-bit architectures, the
result are quite a bit worse on 64-bit architectures). If a variable
is accessed in two of three different ways (which require an integer,
a float, or a string), the memory footprint may increase yet another
-20 bytes. A sloppy malloc(3) implementation can make inflate these
+20 bytes. A sloppy malloc(3) implementation can inflate these
numbers dramatically.
On the opposite end of the scale, a declaration like
@@ -686,7 +686,7 @@ 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 points in
-your execution using the mstats() function out of the standard
+your execution using the mstat() function out of the standard
Devel::Peek module.
Here is some explanation of that format: