summaryrefslogtreecommitdiff
path: root/pod/perldebtut.pod
diff options
context:
space:
mode:
authorMarcel Grunauer <marcel@codewerk.com>2000-08-29 03:19:59 +0200
committerJarkko Hietaniemi <jhi@iki.fi>2000-08-28 23:33:39 +0000
commita31a806a8f483dfa4e00e0ac91d9875a8d724cff (patch)
tree43a8fa1b770bda3450ea8206c1fba741b17fea18 /pod/perldebtut.pod
parentf8f1ea7c161635bf46b2716d915374193f8dd590 (diff)
downloadperl-a31a806a8f483dfa4e00e0ac91d9875a8d724cff.tar.gz
spellings
Message-Id: <200008282319.BAA29862@gandalf.local> p4raw-id: //depot/perl@6872
Diffstat (limited to 'pod/perldebtut.pod')
-rw-r--r--pod/perldebtut.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perldebtut.pod b/pod/perldebtut.pod
index 93fa69da13..28ced7d1ec 100644
--- a/pod/perldebtut.pod
+++ b/pod/perldebtut.pod
@@ -327,7 +327,7 @@ our expected output:
While we're here, take a closer look at the 'B<x>' command, it's really useful
and will merrily dump out nested references, complete objects, partial objects
-- justabout whatever you throw at it:
+- just about whatever you throw at it:
Let's make a quick object and x-plode it, first we'll start the the debugger:
it wants some form of input from STDIN, so we give it something non-commital,
@@ -452,7 +452,7 @@ expected output. This is what it does:
Not very consistent! We'll set a breakpoint in the code manually and run it
under the debugger to see what's going on. A breakpoint is a flag, to which
-the debugger will run without interuption, when it reaches the breakpoint, it
+the debugger will run without interruption, when it reaches the breakpoint, it
will stop execution and offer a prompt for further interaction. In normal
use, these debugger commands are completely ignored, and they are safe - if a
little messy, to leave in production code.