diff options
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perl56delta.pod | 2 | ||||
| -rw-r--r-- | pod/perldebguts.pod | 4 | ||||
| -rw-r--r-- | pod/perlfaq5.pod | 2 | ||||
| -rw-r--r-- | pod/perlfork.pod | 2 | ||||
| -rw-r--r-- | pod/perlfunc.pod | 6 | ||||
| -rw-r--r-- | pod/perlipc.pod | 2 | ||||
| -rw-r--r-- | pod/perllexwarn.pod | 4 | ||||
| -rw-r--r-- | pod/perllocale.pod | 2 | ||||
| -rw-r--r-- | pod/perlmodlib.pod | 2 | ||||
| -rw-r--r-- | pod/perlnumber.pod | 2 | ||||
| -rw-r--r-- | pod/perlopentut.pod | 2 | ||||
| -rw-r--r-- | pod/perltodo.pod | 2 | ||||
| -rw-r--r-- | pod/perltootc.pod | 2 |
13 files changed, 17 insertions, 17 deletions
diff --git a/pod/perl56delta.pod b/pod/perl56delta.pod index 1ca4d7eab2..2117c702d3 100644 --- a/pod/perl56delta.pod +++ b/pod/perl56delta.pod @@ -1539,7 +1539,7 @@ Rhapsody/Darwin is now supported. =item * -EPOC is is now supported (on Psion 5). +EPOC is now supported (on Psion 5). =item * diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod index 2bf6ea40de..45c33c7ec4 100644 --- a/pod/perldebguts.pod +++ b/pod/perldebguts.pod @@ -19,7 +19,7 @@ F<INSTALL> podpage in the Perl source tree. For example, whenever you call Perl's built-in C<caller> function from the package DB, the arguments that the corresponding stack -frame was called with are copied to the the @DB::args array. The +frame was called with are copied to the @DB::args array. The general mechanisms is enabled by calling Perl with the B<-d> switch, the following additional features are enabled (cf. L<perlvar/$^P>): @@ -154,7 +154,7 @@ L<perldebug/"Options"> for description of options parsed by C<DB::parse_options(string)>. The function C<DB::dump_trace(skip[, count])> skips the specified number of frames and returns a list containing information about the calling frames (all of them, if -C<count> is missing). Each entry is reference to a a hash with +C<count> is missing). Each entry is reference to a hash with keys C<context> (either C<.>, C<$>, or C<@>), C<sub> (subroutine name, or info about C<eval>), C<args> (C<undef> or a reference to an array), C<file>, and C<line>. diff --git a/pod/perlfaq5.pod b/pod/perlfaq5.pod index 6ae7755f8b..feb66a45cd 100644 --- a/pod/perlfaq5.pod +++ b/pod/perlfaq5.pod @@ -841,7 +841,7 @@ you see someone do this: You should think long and hard about why you need everything loaded at once. It's just not a scalable solution. You might also find it -more fun to use the the standard DB_File module's $DB_RECNO bindings, +more fun to use the standard DB_File module's $DB_RECNO bindings, which allow you to tie an array to a file so that accessing an element the array actually accesses the corresponding line in the file. diff --git a/pod/perlfork.pod b/pod/perlfork.pod index a3dbf08a71..82ac6891db 100644 --- a/pod/perlfork.pod +++ b/pod/perlfork.pod @@ -11,7 +11,7 @@ call is available, Perl's fork() simply calls it. On some platforms such as Windows where the fork() system call is not available, Perl can be built to emulate fork() at the interpreter level. While the emulation is designed to be as compatible as possible with the -real fork() at the the level of the Perl program, there are certain +real fork() at the level of the Perl program, there are certain important differences that stem from the fact that all the pseudo child "processes" created this way live in the same real process as far as the operating system is concerned. diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 6521f6e65a..17af812526 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1863,7 +1863,7 @@ The exact meaning of the $gcos field varies but it usually contains the real name of the user (as opposed to the login name) and other information pertaining to the user. Beware, however, that in many system users are able to change this information and therefore it -cannot be trusted and therefore the $gcos is is tainted (see +cannot be trusted and therefore the $gcos is tainted (see L<perlsec>). The $passwd and $shell, user's encrypted password and login shell, are also tainted, because of the same reason. @@ -2810,7 +2810,7 @@ otherwise it's necessary to protect any leading and trailing whitespace: open(FOO, "< $file\0"); (this may not work on some bizzare filesystems). One should -conscientiously choose between the the I<magic> and 3-arguments form +conscientiously choose between the I<magic> and 3-arguments form of open(): open IN, $ARGV[0]; @@ -3927,7 +3927,7 @@ GETALL, then ARG must be a variable which will hold the returned semid_ds structure or semaphore value array. Returns like C<ioctl>: the undefined value for error, "C<0 but true>" for zero, or the actual return value otherwise. The ARG must consist of a vector of native -short integers, which may may be created with C<pack("s!",(0)x$nsem)>. +short integers, which may be created with C<pack("s!",(0)x$nsem)>. See also C<IPC::SysV> and C<IPC::Semaphore> documentation. =item semget KEY,NSEMS,FLAGS diff --git a/pod/perlipc.pod b/pod/perlipc.pod index 5b12fbe5e7..9a7fbeda72 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -922,7 +922,7 @@ For those preferring a higher-level interface to socket programming, the IO::Socket module provides an object-oriented approach. IO::Socket is included as part of the standard Perl distribution as of the 5.004 release. If you're running an earlier version of Perl, just fetch -IO::Socket from CPAN, where you'll also find find modules providing easy +IO::Socket from CPAN, where you'll also find modules providing easy interfaces to the following systems: DNS, FTP, Ident (RFC 931), NIS and NISPlus, NNTP, Ping, POP3, SMTP, SNMP, SSLeay, Telnet, and Time--just to name a few. diff --git a/pod/perllexwarn.pod b/pod/perllexwarn.pod index cee1687537..0052d33ff2 100644 --- a/pod/perllexwarn.pod +++ b/pod/perllexwarn.pod @@ -9,7 +9,7 @@ flag B<-w> and the equivalent Perl variable, C<$^W>. The pragma works just like the existing "strict" pragma. This means that the scope of the warning pragma is limited to the -enclosing block. It also means that that the pragma setting will not +enclosing block. It also means that the pragma setting will not leak across files (via C<use>, C<require> or C<do>). This allows authors to independently define the degree of warning checks that will be applied to their module. @@ -195,7 +195,7 @@ or B<-X> command line flags. =back -The combined effect of 3 & 4 is that it will will allow code which uses +The combined effect of 3 & 4 is that it will allow code which uses the C<warnings> pragma to control the warning behavior of $^W-type code (using a C<local $^W=0>) if it really wants to, but not vice-versa. diff --git a/pod/perllocale.pod b/pod/perllocale.pod index be3738573c..55ccf441fd 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -289,7 +289,7 @@ than the PERL_BADLANG approach, but setting LC_ALL (or other locale variables) may affect other programs as well, not just Perl. In particular, external programs run from within Perl will see these changes. If you make the new settings permanent (read on), all -programs you run see the changes. See L<ENVIRONMENT> for for +programs you run see the changes. See L<ENVIRONMENT> for the full list of relevant environment variables and L<USING LOCALES> for their effects in Perl. Effects in other programs are easily deducible. For example, the variable LC_COLLATE may well affect diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod index b42a2d881c..164cb643f7 100644 --- a/pod/perlmodlib.pod +++ b/pod/perlmodlib.pod @@ -823,7 +823,7 @@ to fix your manpath. See L<perl> for details. Extension modules are written in C (or a mix of Perl and C). They are usually dynamically loaded into Perl if and when you need them, -but may also be be linked in statically. Supported extension modules +but may also be linked in statically. Supported extension modules include Socket, Fcntl, and POSIX. Many popular C extension modules do not come bundled (at least, not diff --git a/pod/perlnumber.pod b/pod/perlnumber.pod index 498d962e6c..d179d8c74a 100644 --- a/pod/perlnumber.pod +++ b/pod/perlnumber.pod @@ -59,7 +59,7 @@ finite decimal expansion. Being strings, and thus of arbitrary length, there is no practical limit for the exponent or number of decimal digits for these numbers. (But realize that what we are discussing the rules for just the I<storage> of these numbers. The fact that you can store such "large" numbers -does not mean that that the I<operations> over these numbers will use all +does not mean that the I<operations> over these numbers will use all of the significant digits. See L<"Numeric operators and numeric conversions"> for details.) diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod index 9cb9f6738a..5d2d48e7f1 100644 --- a/pod/perlopentut.pod +++ b/pod/perlopentut.pod @@ -309,7 +309,7 @@ C<O_DEFER>, C<O_SYNC>, C<O_ASYNC>, C<O_DSYNC>, C<O_RSYNC>, C<O_NOCTTY>, C<O_NDELAY> and C<O_LARGEFILE>. Consult your open(2) manpage or its local equivalent for details. (Note: starting from Perl release 5.6 the O_LARGEFILE flag, if available, is automatically -added to the sysopen() flags because large files are the the default.) +added to the sysopen() flags because large files are the default.) Here's how to use C<sysopen> to emulate the simple C<open> calls we had before. We'll omit the C<|| die $!> checks for clarity, but make sure diff --git a/pod/perltodo.pod b/pod/perltodo.pod index 47febc80c2..f12b10f4b9 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -863,7 +863,7 @@ See Time::HiRes. =head2 autocroak? -This is the Fatal.pm module, so any builtin that that does +This is the Fatal.pm module, so any builtin that does not return success automatically die()s. If you're feeling brave, tie this in with the unified exceptions scheme. diff --git a/pod/perltootc.pod b/pod/perltootc.pod index 64f8233fdb..0bcb638a50 100644 --- a/pod/perltootc.pod +++ b/pod/perltootc.pod @@ -184,7 +184,7 @@ to which beginning Perl programmers attempt to put symbolic references, we have much better approaches, like nested hashes or hashes of arrays. But there's nothing wrong with using symbolic references to manipulate something that is meaningful only from the perspective of the package -symbol symbol table, like method names or package variables. In other +symbol table, like method names or package variables. In other words, when you want to refer to the symbol table, use symbol references. Clustering all the class attributes in one place has several advantages. |