X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlapio.pod;h=5103504565689dac64c89a3d830f7bdbc4cc7579;hb=206947d2c0ace466f6b1e79f9bf44a86d72fb50d;hp=ad80a6c2e57d97b62cfae35ff5c6556fe4030cb3;hpb=06936a3ca90ea0922bedd964642e85df92d1986a;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perlapio.pod b/pod/perlapio.pod
index ad80a6c..5103504 100644
--- a/pod/perlapio.pod
+++ b/pod/perlapio.pod
@@ -104,7 +104,7 @@ above abstraction which allows perl more control over how IO is done
 as it decouples IO from the way the operating system and C library
 choose to do things. For USE_PERLIO PerlIO * has an extra layer of
 indirection - it is a pointer-to-a-pointer.  This allows the PerlIO *
-to remain with a known value while swapping the implementation arround
+to remain with a known value while swapping the implementation around
 underneath I<at run time>. In this case all the above are true (but
 very simple) functions which call the underlying implementation.
 
@@ -138,7 +138,7 @@ These correspond to fopen()/fdopen() and the arguments are the same.
 Return C<NULL> and set C<errno> if there is an error.  There may be an
 implementation limit on the number of open handles, which may be lower
 than the limit on the number of open files - C<errno> may not be set
-when C<NULL> is returned if this limnit is exceeded.
+when C<NULL> is returned if this limit is exceeded.
 
 =item B<PerlIO_reopen(path,mode,f)>
 
@@ -289,7 +289,7 @@ problem. However in other cases then mechanisms must exist to create a
 FILE * which can be passed to library code which is going to use stdio
 calls.
 
-The fisrt step is to add this line:
+The first step is to add this line:
 
    #define PERLIO_NOT_STDIO 0
 
@@ -432,7 +432,7 @@ case.
 =item PerlIO_binmode(f,ptype,imode,layers)
 
 The hook used by perl's C<binmode> operator.
-B<ptype> is perl's charcter for the kind of IO:
+B<ptype> is perl's character for the kind of IO:
 
 =over 8
 
@@ -472,13 +472,16 @@ problem.
 PerlIO_debug writes to the file named by $ENV{'PERLIO_DEBUG'} typical
 use might be
 
-  Bourne shells:
+  Bourne shells (sh, ksh, bash, zsh, ash, ...):
    PERLIO_DEBUG=/dev/tty ./perl somescript some args
 
-  Csh:
+  Csh/Tcsh:
    setenv PERLIO_DEBUG /dev/tty
    ./perl somescript some args
 
+  If you have the "env" utility:
+   env PERLIO_DEBUG=/dev/tty ./perl somescript some args
+
   Win32:
    set PERLIO_DEBUG=CON
    perl somescript some args