diff options
| -rw-r--r-- | pod/perldbmfilter.pod | 2 | ||||
| -rw-r--r-- | pod/perldebtut.pod | 2 | ||||
| -rw-r--r-- | pod/perldebug.pod | 2 | ||||
| -rw-r--r-- | pod/perldiag.pod | 2 | ||||
| -rw-r--r-- | pod/perlebcdic.pod | 2 | ||||
| -rw-r--r-- | pod/perlfunc.pod | 2 | ||||
| -rw-r--r-- | pod/perlguts.pod | 4 | ||||
| -rw-r--r-- | pod/perlhack.pod | 4 | ||||
| -rw-r--r-- | pod/perlmodlib.pod | 2 | ||||
| -rw-r--r-- | pod/perlnewmod.pod | 2 | ||||
| -rw-r--r-- | pod/perlport.pod | 2 | ||||
| -rw-r--r-- | pod/perltoc.pod | 4 |
12 files changed, 15 insertions, 15 deletions
diff --git a/pod/perldbmfilter.pod b/pod/perldbmfilter.pod index 3350596aab..8384999e6a 100644 --- a/pod/perldbmfilter.pod +++ b/pod/perldbmfilter.pod @@ -124,7 +124,7 @@ Here is another real-life example. By default, whenever Perl writes to a DBM database it always writes the key and value as strings. So when you use this: - $hash{12345} = "soemthing" ; + $hash{12345} = "something" ; the key 12345 will get stored in the DBM database as the 5 byte string "12345". If you actually want the key to be stored in the DBM database diff --git a/pod/perldebtut.pod b/pod/perldebtut.pod index 28ced7d1ec..2916897893 100644 --- a/pod/perldebtut.pod +++ b/pod/perldebtut.pod @@ -294,7 +294,7 @@ Well, this isn't very easy to read, and using the helpful manual (B<h h>), the 8 'this' 9 'that' -That's not much help, a couple of welcome's in there, but no indication of +That's not much help, a couple of welcomes in there, but no indication of which are keys, and which are values, it's just a listed array dump and, in this case, not particularly helpful. The trick here, is to use a B<reference> to the data structure: diff --git a/pod/perldebug.pod b/pod/perldebug.pod index bccdcf4f51..faff39b2ab 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -342,7 +342,7 @@ missing, all actions are wiped out! Adds an action (Perl command) to happen after the prompt when you've just given a command to return to executing the script. A multi-line -command may be entered by slackbashing the newlines. +command may be entered by backslashing the newlines. =item { ? diff --git a/pod/perldiag.pod b/pod/perldiag.pod index da03b91ee1..20cc02723e 100644 --- a/pod/perldiag.pod +++ b/pod/perldiag.pod @@ -2791,7 +2791,7 @@ Doing so has no effect. (W internal) The internal sv_replace() function was handed a new SV with a reference count of other than 1. -=item Reference to nonexistant group before << HERE in regex m/%s/ +=item Reference to nonexistent group before << HERE in regex m/%s/ (F) You used something like C<\7> in your regular expression, but there are not at least seven sets of capturing parentheses in the expression. If you diff --git a/pod/perlebcdic.pod b/pod/perlebcdic.pod index 1224dc2deb..cdf929e197 100644 --- a/pod/perlebcdic.pod +++ b/pod/perlebcdic.pod @@ -1006,7 +1006,7 @@ XXX. =head1 BUGS This pod document contains literal Latin 1 characters and may encounter -translation difficulties. In particular one populer nroff implementation +translation difficulties. In particular one popular nroff implementation was known to strip accented characters to their unaccented counterparts while attempting to view this document through the B<pod2man> program (for example, you may see a plain C<y> rather than one with a diaeresis diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 5f23b7ea3e..85be9a28bd 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -5482,7 +5482,7 @@ If BITS is 8, "elements" coincide with bytes of the input string. If BITS is 16 or more, bytes of the input string are grouped into chunks of size BITS/8, and each group is converted to a number as with -pack()/unpack() with big-endian formats C<n>/C<N> (and analoguously +pack()/unpack() with big-endian formats C<n>/C<N> (and analogously for BITS==64). See L<"pack"> for details. If bits is 4 or less, the string is broken into bytes, then the bits diff --git a/pod/perlguts.pod b/pod/perlguts.pod index bfdf9facad..2f75cff528 100644 --- a/pod/perlguts.pod +++ b/pod/perlguts.pod @@ -2106,12 +2106,12 @@ However, you must not do this, for example: sv_utf8_upgrade(left); If you do this in a binary operator, you will actually change one of the -strings that came into the operator, and, while it shouldn't be noticable +strings that came into the operator, and, while it shouldn't be noticeable by the end user, it can cause problems. Instead, C<bytes_to_utf8> will give you a UTF8-encoded B<copy> of its string argument. This is useful for having the data available for -comparisons and so on, without harming the orginal SV. There's also +comparisons and so on, without harming the original SV. There's also C<utf8_to_bytes> to go the other way, but naturally, this will fail if the string contains any characters above 255 that can't be represented in a single byte. diff --git a/pod/perlhack.pod b/pod/perlhack.pod index 4d2545d0e7..65188becf7 100644 --- a/pod/perlhack.pod +++ b/pod/perlhack.pod @@ -568,7 +568,7 @@ make sure that the SV B<has> a valid PV, by calling the C<SvPV_force> macro to force a PV. As a side effect, C<tlen> gets set to the current value of the PV, and the PV itself is returned to C<junk>. -In line 7, we make sure that the SV will have enough room to accomodate +In line 7, we make sure that the SV will have enough room to accommodate the old string, the new string and the null terminator. If C<LEN> isn't big enough, C<SvGROW> will reallocate space for us. @@ -1230,7 +1230,7 @@ the first active format: sprintf "%vd", pack("C0U*",1,20,300,4000); print "ok $test\n"; $test++; -Musn't forget to change the number of tests which appears at the top, or +Mustn't forget to change the number of tests which appears at the top, or else the automated tester will get confused: -print "1..156\n"; diff --git a/pod/perlmodlib.pod b/pod/perlmodlib.pod index 1c5808058e..f37279d90a 100644 --- a/pod/perlmodlib.pod +++ b/pod/perlmodlib.pod @@ -736,7 +736,7 @@ By-name interface to Perl's built-in getpw*() functions To find out I<all> modules installed on your system, including those without documentation or outside the standard release, -jus tdo this: +just do this: % find `perl -e 'print "@INC"'` -name '*.pm' -print diff --git a/pod/perlnewmod.pod b/pod/perlnewmod.pod index 1e4a9c3b29..ace8d85130 100644 --- a/pod/perlnewmod.pod +++ b/pod/perlnewmod.pod @@ -224,7 +224,7 @@ installs modules, and this produces a Makefile with a C<dist> target. Once you've ensured that your module passes its own tests - always a good thing to make sure - you can C<make dist>, and the Makefile will -hopefully produce you a nice tarball of your module, ready for upliad. +hopefully produce you a nice tarball of your module, ready for upload. =item Upload the tarball diff --git a/pod/perlport.pod b/pod/perlport.pod index ae9e0c2a10..70b95b05ab 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -1056,7 +1056,7 @@ general usage issues for all EBCDIC Perls. Send a message body of =item * AS/400 Perl information at -ttp://as400.rochester.ibm.com/ +http://as400.rochester.ibm.com/ as well as on CPAN in the F<ports/> directory. =back diff --git a/pod/perltoc.pod b/pod/perltoc.pod index 542df8b2a3..97975b3a0a 100644 --- a/pod/perltoc.pod +++ b/pod/perltoc.pod @@ -7682,7 +7682,7 @@ optionE<gt> [shift|pop]>, C<o conf E<lt>list optionE<gt> http firewall, ftp firewall, One way visibility, SOCKS, IP Masquerade -=item Configuring lynx or ncftp for going throught the firewall +=item Configuring lynx or ncftp for going through the firewall =back @@ -11002,7 +11002,7 @@ after =back =item Warnings -multiple occurence of link target I<name>, line containing nothing but +multiple occurrence of link target I<name>, line containing nothing but whitespace in paragraph, file does not start with =head, No numeric argument for =over, previous =item has no contents, preceding non-item paragraph(s), =item type mismatch (I<one> vs. I<two>), I<N> unescaped |