see issue #4540 remaing files (#4548)

[gist of report with link checks](https://gist.github.com/finanalyst/c676034b4f09b0f7621b9d4ee4848955#file-report-changes-with-internal-targets-md)
[gist of internal links that do not work](https://gist.github.com/finanalyst/8323598b46113a0c429bdf7cf0b41457#file-failing-internal-links-md)

doc/Language/5to6-nutshell.rakudoc

@@ -1430,7 +1430,7 @@ Removed.
 =item C<-P> C<-u> C<-U> C<-W> C<-X>
 
 Removed. See
-L<Removed Syntactic Features|https://design.raku.org/S19.html#Removed_Syntactic_Features>.
+L<Removed Syntactic Features|https://github.com/Raku/old-design-docs/blob/master/S19-commandline.pod#Removed_Syntactic_Features>.
 
 =item C<-w>
 

doc/Language/5to6-perlfunc.rakudoc

@@ -439,9 +439,9 @@ an entity, and C<%hash.antipairs> does the same with the keys and values reverse
 Incidentally, what we have there with the C«->» is called a pointy
 block and, though there are a number of examples in the documentation,
 there doesn't seem to be a really clear explanation of how they work.
-L<https://design.raku.org/S04.html#The_for_statement> may be of some
+L<https://github.com/Raku/old-design-docs/blob/master/S04-control.pod#The_for_statement> may be of some
 help here, as well as the design document at
-L<https://design.raku.org/S06.html#%22Pointy_blocks%22>. There is also
+L<https://github.com/Raku/old-design-docs/blob/master/S06-routines.pod#%22Pointy_blocks%22>. There is also
 some information at L<https://en.wikibooks.org/wiki/Perl_6_Programming/Blocks_and_Closures#Pointy_Blocks>
 
 The Raku ecosystem has a module L<C<P5each>|https://raku.land/zef:lizmat/P5each>
@@ -1359,7 +1359,7 @@ C<$foo> will treat C<$foo> as a literal string, and using C«<$foo>»
 will interpret the contents of C<$foo> as regex code. Note that the
 angle brackets are doing something different here than they do outside a
 regex. For more information on this, see
-L<https://design.raku.org/S05.html#Extensible_metasyntax_(%3C...%3E)>
+L<https://github.com/Raku/old-design-docs/blob/master/S05-regex.pod#Extensible_metasyntax_(%3C...%3E)>
 
 The Raku ecosystem has a module L<C<P5quotemeta>|https://raku.land/zef:lizmat/P5quotemeta>
 which exports a C<quotemeta> function that mimics the original Perl
@@ -1559,7 +1559,7 @@ C<say> can be used as a function, defaulting to standard out. To use
 C<say> as a function with a filehandle I<instead> of standard out, you
 need to put a colon after the filehandle. I. e. C<say $fh: "Howdy!">.
 The use of the colon as an "invocant marker" here is discussed at
-L<https://design.raku.org/S03.html#line_4019>. Alternately, you can use
+L<https://github.com/Raku/old-design-docs/blob/master/S03-operators.pod#line_4019>. Alternately, you can use
 a method call: C<$fh.say("howdy!")>
 
 The Raku ecosystem has a module L<C<P5print>|https://raku.land/zef:lizmat/P5print>

doc/Language/5to6-perlop.rakudoc

@@ -322,7 +322,7 @@ documented, called C<.trans>. C<.trans> uses a list of pairs, as
 follows: C«$x.trans(['a'..'c'] => ['A'..'C'], ['d'..'q'] =>
 ['D'..'Q'], ['r'..'z'] => ['R'..'Z']);». A much more extensive
 description of the uses of C<.trans> can be found at
-L<https://design.raku.org/S05.html#Transliteration>. The C<y///>
+L<https://github.com/Raku/old-design-docs/blob/master/S05-regex.pod#Transliteration>. The C<y///>
 equivalent has been done away with.
 
 Heredocs are specified differently in Raku. You use C<:to> with your quoting

doc/Language/5to6-perlsyn.rakudoc

@@ -170,14 +170,14 @@ for ^10 {
 # inner for
 =end code
 
-For what is planned for C<goto>, see L<https://design.raku.org/S04.html#The_goto_statement>.
+For what is planned for C<goto>, see L<https://github.com/Raku/old-design-docs/blob/master/S04-control.pod#The_goto_statement>.
 
 =head2 Ellipsis statement
 
 C<...> (along with C<!!!> and C<???>) are used to create stub
 declarations. This is a bit more complicated than the use of C<...> in
 Perl, so you'll probably want to look at
-L<https://design.raku.org/S06.html#Stub_declarations> for the gory
+L<https://github.com/Raku/old-design-docs/blob/master/S06-routines.pod#Stub_declarations> for the gory
 details. That said, there doesn't seem to be an I<obvious> reason why it
 shouldn't still fulfill the role it did in Perl, despite its role
 being expanded in Raku.

doc/Language/5to6-perlvar.rakudoc

@@ -316,7 +316,7 @@ Does not exist in Raku, but you can get the same information using C<$/[*-
 If you want to I<understand> why that works, you can look at these documents:
 
 L<[ ] routine|/routine/[ ]>, L<C<Whatever>|/type/Whatever>,
-and the L<historical design document|https://design.raku.org/S02.html#line_1126>
+and the L<historical design document|https://github.com/Raku/old-design-docs/blob/master/S02-bits.pod#line_1126>
 
 =head3 $LAST_SUBMATCH_RESULT, $^N
 

doc/Language/glossary.rakudoc

@@ -744,7 +744,7 @@ of an operator and operands that can be subexpressions or L<value|#value>s.
 Operators are an alternative syntax for a L<multi-method|#multi-method>. With that
 syntax, what would be the arguments of the function are named
 operands instead. Operators are classified into
-L<categories|https://design.raku.org/S02.html#Grammatical_Categories> of
+L<categories|https://github.com/Raku/old-design-docs/blob/master/S02-bits.pod#Grammatical_Categories> of
 categories. A category has a precedence, an arity, and can be L<fiddly|#fiddly>,
 L<iffy|#iffy>, L<diffy|#diffy>. Raku is very creative as to what is an operator, so
 there are many categories. Operators are made of many tokens, possibly with

doc/Language/haskell-to-p6.rakudoc

@@ -439,7 +439,7 @@ And in Raku:
     =end code
 
 See this design document for more information on what kinds of list comprehensions are possible
-in: L<https://design.raku.org/S04.html#The_do-once_loop>.
+in: L<https://github.com/Raku/old-design-docs/blob/master/S04-control.pod#The_do-once_loop>.
 
 As you can see, when you get into some more advanced Haskell list comprehensions, Raku
 does not translate exactly the same, but it's possible to do the same things, nonetheless.

doc/Language/list.rakudoc

@@ -174,7 +174,7 @@ my @a = 1,2; .say for $[@a, |@a ]; # OUTPUT: «[[1 2] 1 2]␤»
 
 In the second case, the single argument is a single element, since we have
 itemized the array. There's an exception to the single argument rule
-L<mentioned in the Synopsis|https://design.raku.org/S07.html#The_single_argument_rule>:
+L<mentioned in the Synopsis|https://github.com/Raku/old-design-docs/blob/master/S07-lists.pod#The_single_argument_rule>:
 list or arrays with a single element will be flattened:
 
 =for code

doc/Language/modules.rakudoc

@@ -47,7 +47,7 @@ have the same structure as any distribution in the Perl family of languages:
 there is a main project directory containing a C<README> and a C<LICENSE> file,
 a C<lib> directory for the source files, which may be individually referred to
 as modules and/or may themselves define modules with the C<module> keyword N<As
-L<synopsis S11|https://design.raku.org/S11.html#Units> says: Confusing? Yes it
+L<synopsis S11|https://github.com/Raku/old-design-docs/blob/master/S11-modules.pod#Units> says: Confusing? Yes it
 is.> , a C<t> directory for tests, and possibly a C<bin> directory for
 executable programs and scripts.
 
@@ -821,7 +821,7 @@ L<https://spdx.org/licenses/>. In the case of the B<Artistic 2.0> license, which
 
 =item If you can't find your license on C<spdx.org> or you use your own license,
 you should put the license's name in the license field. For more details see
-L<https://design.raku.org/S22.html#license>.
+L<https://github.com/Raku/old-design-docs/blob/master/S22-package-format.pod#license>.
 
 =item If you don't yet have any tests, you can leave out the C<t>
 directory and C<basic.rakutest> file for now. For more information on how to write
@@ -894,7 +894,7 @@ possibly displayed on the module page if it's published, but you have no
 obligation to use it.
 
 For choosing a version numbering scheme, try and use "major.minor.patch" (see
-L<the spec on versioning|https://design.raku.org/S11.html#Versioning> for
+L<the spec on versioning|https://github.com/Raku/old-design-docs/blob/master/S11-modules.pod#Versioning> for
 further details). This will go into the C<version> key of C<META6.json>. This
 field is optional, but used by installation to match against installed version,
 if one exists. The C<description> field is also mandatory, and includes a short
@@ -1007,7 +1007,7 @@ you check the correctness of the META6.json file; this module will check for all
 the mandatory fields and that the type used for all of them is correct.
 
 There are more fields described in the
-L<C<META> design documents|https://design.raku.org/S22.html#META6.json>,
+L<C<META> design documents|https://github.com/Raku/old-design-docs/blob/master/S22-package-format.pod#META6.json>,
 but not all of these are
 implemented by existing package managers. Hence you should stick to the fields
 described in the above example block to ensure compatibility with existing

doc/Language/performance.rakudoc

@@ -176,7 +176,7 @@ more efficient for that case.
 =head2 Speed up type-checks and call resolution
 
 Most L<C<where> clauses|/language/signatures#Type_constraints> – and thus most
-L<subsets|https://design.raku.org/S12.html#Types_and_Subtypes> – force dynamic
+L<subsets|https://github.com/Raku/old-design-docs/blob/master/S12-objects.pod#Types_and_Subtypes> – force dynamic
 (runtime) type checking and call resolution for any call it I<might> match.
 This is slower, or at least later, than compile-time.
 

doc/Language/rb-nutshell.rakudoc

@@ -495,7 +495,7 @@ Please note that, in this case, C<===> is not symmetric; in the first
 and last case, the variable has to be in the right-hand side. There is
 no equivalent to the signature class in Ruby, either.
 
-See L<S03/Smartmatching|https://design.raku.org/S03.html#Smart_matching> for more information on this feature.
+See L<S03/Smartmatching|https://github.com/Raku/old-design-docs/blob/master/S03-operators.pod#Smart_matching> for more information on this feature.
 
 =head2 C<& | ^> Numeric bitwise ops
 =head2 C<& | ^> Boolean ops
@@ -774,7 +774,7 @@ next if $line.match(/static/); # Raku
 
 Alternately, the C<.match> and C<.subst> methods can be used. Note that
 C<.subst> is non-mutating. See
-L<S05/Substitution|https://design.raku.org/S05.html#Substitution>.
+L<S05/Substitution|https://github.com/Raku/old-design-docs/blob/master/S05-regex.pod#Substitution>.
 
 =head2 C<.sub> and C<.sub!>
 

doc/Language/regexes.rakudoc

@@ -1000,7 +1000,7 @@ In short, in regex branches separated by C<|>, the longest token match wins,
 independent of the textual ordering in the regex. However, what C<|> really
 does is more than that.
 It does not decide which branch wins after finishing the whole match,
-but follows the L<longest-token matching (LTM) strategy|https://design.raku.org/S05.html#Longest-token_matching>.
+but follows the L<longest-token matching (LTM) strategy|https://github.com/Raku/old-design-docs/blob/master/S05-regex.pod#Longest-token_matching>.
 
 Briefly, what C<|> does is this:
 
@@ -1033,7 +1033,7 @@ If the tie breaker above doesn't work, then the textually earlier alternative
 takes precedence.
 
 For more details, see
-L<the LTM strategy|https://design.raku.org/S05.html#Longest-token_matching>.
+L<the LTM strategy|https://github.com/Raku/old-design-docs/blob/master/S05-regex.pod#Longest-token_matching>.
 
 =head2 Quoted lists are LTM matches
 

doc/Language/syntax.rakudoc

@@ -569,7 +569,7 @@ See L<quoting|/language/quoting> for many more options, including
 L<interpolation quoting C<qq>|/language/quoting#Interpolation:_qq>. Raku uses
 the standard escape characters in literals: C<\0 \a \b \t \n \f \r \e>,
 with the same meaning as the ASCII escape codes, specified in
-L<the design document|https://design.raku.org/S02.html#Backslash_sequences>.
+L<the design document|https://github.com/Raku/old-design-docs/blob/master/S02-bits.pod#Backslash_sequences>.
 
     say "🔔\a";  # OUTPUT: «🔔␇␤»