summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
Diffstat (limited to 'pod')
-rw-r--r--pod/perlfunc.pod6
-rw-r--r--pod/perlintern.pod8
-rw-r--r--pod/perlthrtut.pod2
-rw-r--r--pod/pod2latex.PL2
4 files changed, 9 insertions, 9 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 7fed9c0239..a6f5771878 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -849,7 +849,7 @@ extirpated as a potential munition). This can prove useful for checking
the password file for lousy passwords, amongst other things. Only the
guys wearing white hats should do this.
-Note that C<crypt> is intended to be a one-way function, much like
+Note that L<crypt|/crypt> is intended to be a one-way function, much like
breaking eggs to make an omelette. There is no (known) corresponding
decrypt function (in other words, the crypt() is a one-way hash
function). As a result, this function isn't all that useful for
@@ -893,7 +893,7 @@ their own password:
Of course, typing in your own password to whoever asks you
for it is unwise.
-The L<crypt> function is unsuitable for encrypting large quantities
+The C<crypt> function is unsuitable for encrypting large quantities
of data, not least of all because you can't get the information
back. Look at the F<by-module/Crypt> and F<by-module/PGP> directories
on your favorite CPAN mirror for a slew of potentially useful
@@ -2715,7 +2715,7 @@ C<redo> work.
=item no Module
-See the L</use> function, which C<no> is the opposite of.
+See the C<use> function, which C<no> is the opposite of.
=item oct EXPR
diff --git a/pod/perlintern.pod b/pod/perlintern.pod
index d6cd33340e..c4bb1d5a01 100644
--- a/pod/perlintern.pod
+++ b/pod/perlintern.pod
@@ -447,9 +447,9 @@ The 0'th slot of a frame AV is an AV which is @_.
other entries are storage for variables and op targets.
During compilation:
-C<PL_comppad_name> is set the the the names AV.
-C<PL_comppad> is set the the frame AV for the frame CvDEPTH == 1.
-C<PL_curpad> is set the body of the frame AV (i.e. AvARRAY(PL_comppad)).
+C<PL_comppad_name> is set to the names AV.
+C<PL_comppad> is set to the frame AV for the frame CvDEPTH == 1.
+C<PL_curpad> is set to the body of the frame AV (i.e. AvARRAY(PL_comppad)).
During execution, C<PL_comppad> and C<PL_curpad> refer to the live
frame of the currently executing sub.
@@ -479,7 +479,7 @@ a REFCNT'ed references to a lexical from "outside". In this case,
the name SV does not have a cop_seq range, since it is in scope
throughout.
-If the 'name' is '&' the the corresponding entry in frame AV
+If the 'name' is '&' the corresponding entry in frame AV
is a CV representing a possible closure.
(SvFAKE and name of '&' is not a meaningful combination currently but could
become so if C<my sub foo {}> is implemented.)
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod
index 575ec27c52..27ad46e264 100644
--- a/pod/perlthrtut.pod
+++ b/pod/perlthrtut.pod
@@ -542,7 +542,7 @@ techniques such as queues, which remove some of the hard work involved.
=head2 Controlling access: lock()
The lock() function takes a shared variable and puts a lock on it.
-No other thread may lock the variable until the the variable is unlocked
+No other thread may lock the variable until the variable is unlocked
by the thread holding the lock. Unlocking happens automatically
when the locking thread exits the outermost block that contains
C<lock()> function. Using lock() is straightforward: this example has
diff --git a/pod/pod2latex.PL b/pod/pod2latex.PL
index 002f06dca1..be8da92a23 100644
--- a/pod/pod2latex.PL
+++ b/pod/pod2latex.PL
@@ -260,7 +260,7 @@ combined output file.
=head1 OPTIONS AND ARGUMENTS
-This section describes the supported command line options. Minium
+This section describes the supported command line options. Minimum
matching is supported.
=over 4