patches suggested by John Bley <jbb6@acpub.duke.edu> (with minor edits)

[perl5.git] / pod / perlvar.pod

diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 44124d6..38d6d32 100644 (file)
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -275,7 +275,7 @@ get the record back in pieces.
 On VMS, record reads are done with the equivalent of C<sysread>, so it's
 best not to mix record and non-record reads on the same file. (This is
 likely not a problem, as any file you'd want to read in record mode is
-proably usable in line mode) Non-VMS systems perform normal I/O, so
+probably usable in line mode) Non-VMS systems perform normal I/O, so
 it's safe to mix record and non-record reads of a file.
 
 =item autoflush HANDLE EXPR
@@ -771,7 +771,7 @@ Start with single-step on.
 
 =back
 
-Note that some bits may be relevent at compile-time only, some at
+Note that some bits may be relevant at compile-time only, some at
 run-time only. This is a new mechanism and the details may change.
 
 =item $^R
@@ -932,7 +932,7 @@ respect: they may be called to report (probable) errors found by the
 parser.  In such a case the parser may be in inconsistent state, so
 any attempt to evaluate Perl code from such a handler will probably
 result in a segfault.  This means that calls which result/may-result
-in parsing Perl should be used with extreme causion, like this:
+in parsing Perl should be used with extreme caution, like this:
 
     require Carp if defined $^S;
     Carp::confess("Something wrong") if defined &Carp::confess;