fix some broken links #4476

Author: coke

doc/Language/modules.rakudoc

@@ -1028,7 +1028,7 @@ zef install ./your-module-folder
 
 Note that doing so precompiles and installs your module. If you make changes to
 the source, you'll need to re-install the module.
-(See C<use lib> L<pragma|/language/pragmas#index-entry-lib__pragma>, C<-I>
+(See C<use lib> L<pragma|/language/pragmas#lib>, C<-I>
 command line switch, or C<RAKULIB> environment variable, to include a path to your
 module source while developing it, so you don't have to install it at all).
 

doc/Language/regexes.rakudoc

@@ -546,7 +546,7 @@ you:
      say "u\x[0308]" ~~ /\c[LATIN SMALL LETTER U]/;    # OUTPUT: «Nil␤»
 
 To match the unmodified character, you can use the
-L<C<:ignoremark>|#regex_adverb,:ignoremark> adverb.
+L<C<:ignoremark>|#Ignoremark> adverb.
 
 =head3 X<C<\x> and C<\X>|Regexes,\x;Regexes,\X>
 

doc/Language/subscripts.rakudoc

@@ -825,7 +825,7 @@ implementation provided by L<C<Any>|/type/Any> (which is involved in auto-vivifi
 =head2 Methods to implement for positional subscripting
 
 In order to make index-based subscripting via L<C<postcircumfix [ ]>|
-/routine/[ ]#postcircumfix_[_]> work for your custom type, you should
+/language/operators#postcircumfix_[_]> work for your custom type, you should
 implement at least C<elems>, C<AT-POS> and C<EXISTS-POS> - and optionally
 others as detailed below.
 
@@ -835,7 +835,7 @@ others as detailed below.
 
 Expected to return a number indicating how many subscriptable elements
 there are in the object. May be called by users directly, and is also
-called by L<C<postcircumfix [ ]>|/routine/[ ]#postcircumfix_[_]> when
+called by L<C<postcircumfix [ ]>|/language/operators#postcircumfix_[_]> when
 indexing elements from the end, as in C<@foo[*-1]>.
 
 If not implemented, your type will inherit the default implementation from
@@ -855,7 +855,7 @@ to avoid silently doing the wrong thing.
                methods below), after jnthn's ongoing refactor is finished.
 
 Expected to return the element at position C<$index>. This is what
-L<C<postcircumfix [ ]>|/routine/[ ]#postcircumfix_[_]> normally calls.
+L<C<postcircumfix [ ]>|/language/operators#postcircumfix_[_]> normally calls.
 
 If you want an element to be mutable (like they are for the built-in
 L<C<Array>|/type/Array> type), you'll have to make sure to return it in the form of
@@ -872,7 +872,7 @@ to make that work; see the L<example|/language/subscripts#Custom_type_example>.
 
 Expected to return a Bool indicating whether or not there is an element at
 position C<$index>. This is what L<C<postcircumfix [ ]>|
-/routine/[ ]#postcircumfix_[_]> calls when invoked like C<@foo[42]:exists>.
+/language/operators#postcircumfix_[_]> calls when invoked like C<@foo[42]:exists>.
 
 What "existence" of an element means, is up to your type.
 
@@ -890,7 +890,7 @@ L<die|/routine/die>s, to avoid silently doing the wrong thing.
     multi method DELETE-POS (::?CLASS:D: $index)
 
 Expected to delete the element at position C<$index>, and return the value
-it had. This is what L<C<postcircumfix [ ]>|/routine/[ ]#postcircumfix_[_]>
+it had. This is what L<C<postcircumfix [ ]>|/language/operators#postcircumfix_[_]>
 calls when invoked like C<@foo[42]:delete>.
 
 What "deleting" an element means, is up to your type.
@@ -1022,7 +1022,7 @@ say @a;        # OUTPUT: «[1,2,3,4]␤»
 =head2 Methods to implement for associative subscripting
 
 In order to make key-based subscripting via L<C<postcircumfix { }>|
-/routine/{ }#postcircumfix_{_}> work for your custom type, you should
+/language/operators#postcircumfix_{_}> work for your custom type, you should
 implement at least C<AT-KEY> and C<EXISTS-KEY> - and optionally
 others as detailed below.
 
@@ -1034,7 +1034,7 @@ others as detailed below.
     multi method AT-KEY (::?CLASS:D: $key)
 
 Expected to return the element associated with C<$key>. This is what
-L<C<postcircumfix { }>|/routine/{ }#postcircumfix_{_}> normally calls.
+L<C<postcircumfix { }>|/language/operators#postcircumfix_{_}> normally calls.
 
 If you want an element to be mutable (like they are for the built-in
 L<C<Hash>|/type/Hash> type), you'll have to make sure to return it in the form of
@@ -1053,7 +1053,7 @@ to return non-container values directly.
     multi method EXISTS-KEY (::?CLASS:D: $key)
 
 Expected to return a Bool indicating whether or not there is an element
-associated with C<$key>. This is what L<C<postcircumfix { }>|/routine/{ }#postcircumfix_{_}>
+associated with C<$key>. This is what L<C<postcircumfix { }>|/language/operators#postcircumfix_{_}>
 calls when invoked like C<<%foo<aa>:exists>>.
 
 What "existence" of an element means, is up to your type.
@@ -1072,7 +1072,7 @@ silently doing the wrong thing.
     multi method DELETE-KEY (::?CLASS:D: $key)
 
 Expected to delete the element associated with C<$key>, and return the
-value it had. This is what L<C<postcircumfix { }>|/routine/{ }#postcircumfix_{_}> calls when invoked like
+value it had. This is what L<C<postcircumfix { }>|/language/operators#postcircumfix_{_}> calls when invoked like
 C<<%foo<aa>:delete>>.
 
 What "deleting" an element means, is up to your type - though it should

doc/Language/typesystem.rakudoc

@@ -40,7 +40,7 @@ To test if an object is a type object, use
 L<smartmatch|/language/operators#index-entry-smartmatch_operator>
 against a type constrained with a
 L<type smiley|/language/signatures#Constraining_argument_definiteness> or
-L«C<.DEFINITE>|/language/mop#index-entry-syntax_DEFINITE-DEFINITE» method:
+L«C<.DEFINITE>|/language/mop#DEFINITE» method:
 
 =begin code :ok-test<WHAT>
 my $a = Int;
@@ -130,7 +130,7 @@ automatically if no such scope exists already.
 
 X«|Syntax,... (forward declaration)»
 X«Forward declarations|Language,Forward declarations» can be provided with a block containing only C<...>,
-the L<"stub" operator|/language/operators#index-entry-..._operators>. The
+the L<"stub" operator|/language/operators#listop_...>. The
 compiler will check at the end of the current scope if the type is defined.
 
     class C {...}