Fix some links

Part of #4476

Author: coke

doc/Language/operators.rakudoc

@@ -2348,7 +2348,7 @@ say infix:<eqv>(False); # OUTPUT: «True␤»
 
     sub infix:<===>(Any, Any)
 
-The ASCII equivalent of L<C<⩶>|#infix_⩶>, the value identity oprator
+The ASCII equivalent of L<C<⩶>|#infix_⩶>, the value identity operator.
 
 Before Rakudo version 2021.07, the ASCII variant was the I<only> variant.
 

doc/Language/variables.rakudoc

@@ -25,7 +25,7 @@ L<positional-sigil|/language/containers#Flattening,_items_and_containers>
 and the
 L<associative-sigil|/language/containers#Flattening,_items_and_containers>
 provide type constraint that enforce base type
-L<subscripts|/language/subscripts#TOC_Title> required to know what
+L<subscripts|/language/subscripts> required to know what
 methods to dispatch to. The
 L<callable-sigil|/language/containers#Callable_containers> does the same
 for function calls. The latter also tells the compiler where parentheses
@@ -456,7 +456,7 @@ the fact that they create blocks.
 
 Just like the C<^>twigil, the C<:> twigil can be combined with any sigil; using
 C<:> with a sigil will create a formal named parameter with that sigil (applying
-the L<semantics of that sigil|#Sigil>).  Thus C<@:array>, C<%:hash>, and
+the L<semantics of that sigil|#Sigils>).  Thus C<@:array>, C<%:hash>, and
 C<&:fun> are all valid, and each creates a formal named parameter with the
 specified sigil.
 
@@ -599,7 +599,7 @@ new-location; # OUTPUT: «outside␤»
 =end code
 
 To make C<new-location()> print C<nowhere>, make C<$location> a dynamic variable
-using L<the * twigil|#The_*_Twigil>. This twigil makes the compiler look up the
+using L<the * twigil|#The_*_twigil>. This twigil makes the compiler look up the
 symbol in the calling scope instead of the outer scope after trying the local
 scope.
 
@@ -1077,7 +1077,7 @@ re-applied by assigning L<C<Nil>|/type/Nil> to it:
 =head2 Default defined variables pragma
 
 To force all variables to have a
-L<definiteness|/language/mop#index-entry-syntax_DEFINITE-DEFINITE> constraint,
+L<definiteness|/language/mop#DEFINITE> constraint,
 use the pragma C<use variables :D>. The pragma is lexically scoped and can be
 switched off with C<use variables :_>.
 
@@ -1300,7 +1300,7 @@ they do to C<$/>.
 X<|Language,cursor variable>
 =head3 The C<$¢> variable
 
-See the description in L<C<Match>|/type/Match#index-entry-$%C2%A2-$%C2%A2>.
+See the description in L<C<Match>|/type/Match>.
 
 X<|Variables,$?FILE>X<|Variables,$?LINE>X<|Variables,::?CLASS>
 
@@ -1447,7 +1447,7 @@ sub do-work {
 do-work;
 =end code
 
-Note that, in a L<C«multi»|/language/functions#index-entry-declarator_multi-Multi-dispatch>,
+Note that, in a L<C«multi»|/language/functions#Multi-dispatch>,
 C<&?ROUTINE> refers to the current candidate, I<not> the C<multi>
 as a whole.
 

doc/Type/Any.rakudoc

@@ -639,7 +639,7 @@ don't really have keys.
 
     method flatmap(&block, :$label)
 
-Convenience method, analogous to L<C<.map(&block)>|#method_map>L<C<.flat>|#method_flat>.
+Convenience method, analogous to L<C<.map(&block)>|#routine_map>L<C<.flat>|#method_flat>.
 
 =head2 method roll
 
@@ -1470,7 +1470,7 @@ Non-L<C<Int>|/type/Int> values of C<$batch> will be coerced to Int:
 
     say (3..9).rotor(3+⅓); # OUTPUT: «((3 4 5) (6 7 8))␤»
 
-Please see also L<C<list.rotor>|/type/List#method_rotor> for examples applied to
+Please see also L<C<list.rotor>|/type/List#routine_rotor> for examples applied to
 lists.
 
 =head2 method sum
@@ -1493,7 +1493,7 @@ It will fail if any of the elements cannot be converted to a number.
 Available as of the 2021.02 release of the Rakudo compiler.
 
 Converts the invocant to a L<C<Seq>|/type/Seq> and then calls the
-L<slice method|/type/Seq#method_slice> on it.
+L<slice method|/type/Seq#multi_method_slice> on it.
 
     say (1..10).slice(0, 3..6, 8);  # OUTPUT: «(1 4 5 6 7 9)␤»
 

doc/Type/List.rakudoc

@@ -24,7 +24,7 @@ nor the elements themselves can be changed. Thus, it is not possible to use
 operations that change the list structure itself such as L<shift|/routine/shift>,
 L<unshift|/routine/unshift>, L<push|/routine/push>, L<pop|/routine/pop>,
 L<splice|/routine/splice>
-and L<binding|/language/operators#index-entry-Binding_operator>.
+and L<binding|/language/operators#Operators>.
 
 =begin code
 (1, 2, 3).shift;      # Error Cannot call 'shift' on an immutable 'List'
@@ -403,7 +403,7 @@ be handled in the context of that L<C<Routine>|/type/Routine>.
 
     method flatmap(List:D: &code --> Seq:D)
 
-Convenience method, analogous to L<C<.map(&block)>|#method_map>L<C<.flat>|#method_flat>.
+Convenience method, analogous to L<C<.map(&block)>|#routine_map>L<C<.flat>|/type/Iterable#method_flat>.
 
 =head2 method gist
 
@@ -583,7 +583,7 @@ that as the number of elements in the output L<C<Seq>|/type/Seq>.
     multi        categorize($test, +items, *%named )
 
 These methods are directly inherited from L<C<Any>|/type/Any>; see
-L<C<Any.list>|/routine/categorize#(Any)_method_categorize> for more examples.
+L<C<Any.list>|/type/Any#routine_categorize> for more examples.
 
 This routine transforms a list of values into a hash representing the
 categorizations of those values according to C<$test>, which is called once for
@@ -982,7 +982,7 @@ depends on the operator. In the functional programming world, this operation is
 generally called a L<fold|https://en.wikipedia.org/wiki/Fold_%28higher-order_function%29#Folds_on_lists>.
 With a right-associative operator it is a I<right fold>, otherwise (and usually)
 it is a I<left fold>. In Raku, you can specify the associativity of an operator
-with the L<C«is assoc»|/language/functions#index-entry-is_assoc_(trait)>.
+with the L<C«is assoc»|/language/functions#index-entry-is_assoc> trait.
 
     sub infix:<foo>($a, $b) is assoc<right> { "($a, $b)" }
     say [foo] 1, 2, 3, 4; # OUTPUT: «(1, (2, (3, 4)))␤»