Fix a bunch of repeated-word typos

Mostly in comments and docs, but some in diagnostic messages and one
case of 'or die die'.

7 files changed, 10 insertions, 10 deletions

diff --git a/pod/perldeprecation.pod b/pod/perldeprecation.pod
index 250e2c9578..95a94cd403 100644
--- a/pod/perldeprecation.pod
+++ b/pod/perldeprecation.pod
@@ -101,7 +101,7 @@ also be escaped to avoid confusing the parser, for example,
 
 Forcing literal C<{> characters to be escaped will enable the Perl
 language to be extended in various ways in future releases.  To avoid
-needlessly breaking existing code, the restriction is is not enforced in
+needlessly breaking existing code, the restriction is not enforced in
 contexts where there are unlikely to ever be extensions that could
 conflict with the use there of C<{> as a literal.  A non-deprecation
 warning that the left brace is being taken literally is raised in
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index a31adb90fd..2b2df17a1f 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -6479,7 +6479,7 @@ also be escaped to avoid confusing the parser, for example,
 
 Forcing literal C<"{"> characters to be escaped enables the Perl
 language to be extended in various ways in future releases.  To avoid
-needlessly breaking existing code, the restriction is is not enforced in
+needlessly breaking existing code, the restriction is not enforced in
 contexts where there are unlikely to ever be extensions that could
 conflict with the use there of C<"{"> as a literal.  Those that are
 not potentially ambiguous do not warn; those that are do raise a
@@ -6533,7 +6533,7 @@ also be escaped to avoid confusing the parser, for example,
 
 Forcing literal C<"{"> characters to be escaped enables the Perl
 language to be extended in various ways in future releases.  To avoid
-needlessly breaking existing code, the restriction is is not enforced in
+needlessly breaking existing code, the restriction is not enforced in
 contexts where there are unlikely to ever be extensions that could
 conflict with the use there of C<"{"> as a literal.  Those that are
 not potentially ambiguous do not warn; those that are raise this
diff --git a/pod/perlgit.pod b/pod/perlgit.pod
index 67aa0b4038..6ec1f1ea76 100644
--- a/pod/perlgit.pod
+++ b/pod/perlgit.pod
@@ -770,7 +770,7 @@ seen on github.com it must be a local branch whose first name
 component is precisely C<smoke-me>.
 
 The procedure for doing this is roughly as follows (using the example of
-of tonyc's smoke-me branch called win32stat):
+tonyc's smoke-me branch called win32stat):
 
 First, make a local branch and switch to it:
 
diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 2a4959d79b..1d9f18aa20 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -3730,7 +3730,7 @@ Here is a typical example of context popping, as found in C<pp_leavesub>
 
 The steps above are in a very specific order, designed to be the reverse
 order of when the context was pushed. The first thing to do is to copy
-and/or protect any any return arguments and free any temps in the current
+and/or protect any return arguments and free any temps in the current
 scope. Scope exits like an rvalue sub normally return a mortal copy of
 their return args (as opposed to lvalue subs). It is important to make
 this copy before the save stack is popped or variables are restored, or
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index b4122e3940..ba5725992d 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -812,7 +812,7 @@ code point.  This function returns C<"\xC2\xA0"> on an ASCII platform, and
 C<"\x80\x41"> on an EBCDIC 1047 one.
 
 But easiest is, if the character is specifiable as a literal, like
-C<"A"> or C<"%">, to use that; if not so specificable, you can use use
+C<"A"> or C<"%">, to use that; if not so specificable, you can use
 C<\N{}> , if the side effects aren't troublesome.  Simply specify all
 your characters in hex, using C<\N{U+ZZ}> instead of C<\xZZ>.  C<\N{}>
 is the Unicode name, and so it
diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index 5ddb920e86..e03dc84371 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -1025,7 +1025,7 @@ should use C<\w> with the C</a> regular expression modifier.  See L</"SECURITY">
 
 =head2 Category C<LC_NUMERIC>: Numeric Formatting
 
-After a proper C<POSIX::setlocale()> call, and within the scope of
+After a proper C<POSIX::setlocale()> call, and within the scope
 of a C<use locale> form that includes numerics, Perl obeys the
 C<LC_NUMERIC> locale information, which controls an application's idea
 of how numbers should be formatted for human readability.
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index fa1710dfd3..2fdb8e1809 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -979,7 +979,7 @@ C<\p{...}> property.
 
 =head2 Wildcards in Property Values
 
-Starting in Perl 5.30, it is possible to do do something like this:
+Starting in Perl 5.30, it is possible to do something like this:
 
  qr!\p{numeric_value=/\A[0-5]\z/}!
 
@@ -1013,7 +1013,7 @@ delimits the end of the enclosing C<\p{}>.  Like any pattern, certain
 other delimiters are terminated by their mirror images.  These are
 C<"(">, C<"[>", and C<"E<lt>">.  If the delimiter is any of C<"-">,
 C<"_">, C<"+">, or C<"\">, or is the same delimiter as is used for the
-enclosing pattern, it must be be preceded by a backslash escape, both
+enclosing pattern, it must be preceded by a backslash escape, both
 fore and aft.
 
 Beware of using C<"$"> to indicate to match the end of the string.  It
@@ -2068,7 +2068,7 @@ In L<< C<split>'s special-case whitespace splitting|perlfunc/split >>.
 
 Starting in Perl 5.28.0, the C<split> function with a pattern specified as
 a string containing a single space handles whitespace characters consistently
-within the scope of of C<unicode_strings>. Prior to that, or outside its scope,
+within the scope of C<unicode_strings>. Prior to that, or outside its scope,
 characters that are whitespace according to Unicode rules but not according to
 ASCII rules were treated as field contents rather than field separators when
 they appear in byte-encoded strings.