ExtUtils::CBuilder - Fix link() on Windows, broken in version 0.280226

[perl5.git] / pod / perlre.pod

diff --git a/pod/perlre.pod b/pod/perlre.pod
index 3c90252..9cab16e 100644 (file)
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -69,7 +69,7 @@ meaning described in this document.  A sequence of non-metacharacters
 matches the same sequence in the target string, as we saw above with
 C<m/abc/>.
 
-Only a few characters (all or them being ASCII punctuation characters)
+Only a few characters (all of them being ASCII punctuation characters)
 are metacharacters.  The most commonly used one is a dot C<".">, which
 normally matches almost any character (including a dot itself).
 
@@ -505,7 +505,7 @@ a C<\Q...\E> stays unaffected by C</x>.  And note that C</x> doesn't affect
 space interpretation within a single multi-character construct.  For
 example in C<\x{...}>, regardless of the C</x> modifier, there can be no
 spaces.  Same for a L<quantifier|/Quantifiers> such as C<{3}> or
-C<{5,}>.  Similarly, C<(?:...)> can't have a space between the C<"{">,
+C<{5,}>.  Similarly, C<(?:...)> can't have a space between the C<"(">,
 C<"?">, and C<":">.  Within any delimiters for such a
 construct, allowed spaces are not affected by C</x>, and depend on the
 construct.  For example, C<\x{...}> can't have spaces because hexadecimal
@@ -2495,7 +2495,8 @@ at each matching starting point like so:
 
 Any number of C<(*PRUNE)> assertions may be used in a pattern.
 
-See also C<< (?>pattern) >> and possessive quantifiers for other ways to
+See also C<<< L<< /(?>pattern) >> >>> and possessive quantifiers for
+other ways to
 control backtracking. In some cases, the use of C<(*PRUNE)> can be
 replaced with a C<< (?>pattern) >> with no functional difference; however,
 C<(*PRUNE)> can be used to handle cases that cannot be expressed using a