summaryrefslogtreecommitdiff
path: root/pod/perlguts.pod
diff options
context:
space:
mode:
authorPiotr Fusik <pfusik@op.pl>2005-07-30 23:54:19 +0200
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2005-08-01 08:13:10 +0000
commitd7f8936a2fe7fc93635b0b501d1f941d30d3399f (patch)
tree9ec130d79fad2c450541f9ea56801a6ecd17f962 /pod/perlguts.pod
parent0d65d7d555c9e685ae54e22c9f9eb33ec635ea81 (diff)
downloadperl-d7f8936a2fe7fc93635b0b501d1f941d30d3399f.tar.gz
POD typos
From: "Piotr Fusik" <pfusik@op.pl> Message-ID: <00ef01c59542$3198ba00$26d34dd5@piec> p4raw-id: //depot/perl@25253
Diffstat (limited to 'pod/perlguts.pod')
-rw-r--r--pod/perlguts.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 65b3d81fd8..0d9e2efce6 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -304,7 +304,7 @@ The are various ways in which the private and public flags may differ.
For example, a tied SV may have a valid underlying value in the IV slot
(so SvIOKp is true), but the data should be accessed via the FETCH
routine rather than directly, so SvIOK is false. Another is when
-numeric conversion has occured and precision has been lost: only the
+numeric conversion has occurred and precision has been lost: only the
private flag is set on 'lossy' values. So when an NV is converted to an
IV with loss, SvIOKp, SvNOKp and SvNOK will be set, while SvIOK wont be.
@@ -2298,7 +2298,7 @@ be able to use these macros:
You can use these macros if you call code that may croak, but you need
to do some cleanup before giving control back to Perl. For example:
- dXCPT; /* set up neccessary variables */
+ dXCPT; /* set up necessary variables */
XCPT_TRY_START {
code_that_may_croak();