From: Hugo van der Sanden <hv@crypt.org>
Date: Mon, 27 Jul 1998 13:34:45 +0000 (+0200)
Subject: perlcall.pod
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=268118b230b225b283ec54291ec9a46f100cfddc;p=p5sagit%2Fp5-mst-13.2.git

perlcall.pod

	Message-Id: <199807271134.NAA24475@dorlas.elsevier.nl>

p4raw-id: //depot/maint-5.005/perl@1680
---

diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 7c94d37..c239cfe 100644
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -279,8 +279,8 @@ belongs to C<joe>.
 
 It is possible for the Perl subroutine you are calling to terminate
 abnormally, e.g., by calling I<die> explicitly or by not actually
-existing.  By default, when either of these of events occurs, the
-process will terminate immediately.  If though, you want to trap this
+existing.  By default, when either of these events occurs, the
+process will terminate immediately.  If you want to trap this
 type of event, specify the G_EVAL flag.  It will put an I<eval { }>
 around the subroutine call.