Merge pull request #3076 from tusindfryd/master

Fix broken links

Author: JJ

doc/Language/control.pod6

@@ -188,7 +188,7 @@ is the only thing to do asynchronously.
     say $promise.result; # OUTPUT: «42␤»
 
 Note that code executed this way does not have access to the special
-variables L«C<$!>|/syntax/$!» and L«C<$/>|/syntax/$/» of its outer
+variables L«C<$!>|/syntax/$!» and L«C<$/>|/syntax/$$SOLIDUS» of its outer
 block, but receives new ones, so every asynchronous task has its
 per-task state.
 

doc/Language/create-cli.pod6

@@ -12,7 +12,7 @@ The default command line interface of Raku scripts consists of three parts:
 =head2 Parsing the command line parameters into a L<capture|/type/Capture>
 
 This looks at the values in L<@*ARGS|/language/variables#index-entry-@*ARGS>,
-interprets these according to some policy, and creates a L<Capture/type/Capture>
+interprets these according to some policy, and creates a L<Capture|/type/Capture>
 object out of that. An alternative way of parsing may be provided by the developer
 or installed using a module.
 

doc/Language/modules.pod6

@@ -806,7 +806,7 @@ which was used to indicate the kind of source control system, generally C<git>,
 which can be used to download the module. However, this field is nowadays
 ignored by C<zef> and the rest of the tools.>
 
-The L<C<Test::META>> module | https://github.com/jonathanstowe/Test-META/> can
+The L<C<Test::META> module | https://github.com/jonathanstowe/Test-META/> can
 help
 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.

doc/Language/operators.pod6

@@ -1889,7 +1889,7 @@ is smaller than or equal to the second.
 
 Numeric less than or equal to operator.
 
-Equivalent to L«<=|routine/<=», at codepoint U+2264 (LESS-THAN OR EQUAL TO).
+Equivalent to L«<=|/routine/<=», at codepoint U+2264 (LESS-THAN OR EQUAL TO).
 
 =head2 infix C«>»
 
@@ -2588,7 +2588,7 @@ A comparison:
     say $_ if /A/ ff /C/ for @list;    # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ ^ff /C/ for @list;   # OUTPUT: «B␤C␤»
 
-The sed-like version can be found in L<C<^fff>|/routine/^fff>.
+The sed-like version can be found in L<C<^fff>|/routine/$CIRCUMFLEX_ACCENTfff>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 
@@ -2603,7 +2603,7 @@ stop condition (including items that first matched the start condition).
     say $_ if /A/ ff /C/ for @list;    # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ ff^ /C/ for @list;   # OUTPUT: «A␤B␤»
 
-The sed-like version can be found in L<fff^|/routine/fff^>.
+The sed-like version can be found in L<fff^|/routine/fff$CIRCUMFLEX_ACCENT>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 
@@ -2618,7 +2618,7 @@ the stop or start condition (or both).
     say $_ if /A/ ff /C/ for @list;    # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ ^ff^ /C/ for @list;  # OUTPUT: «B␤»
 
-The sed-like version can be found in L<C<^fff^>|/routine/^fff^>.
+The sed-like version can be found in L<C<^fff^>|/routine/$CIRCUMFLEX_ACCENTfff$CIRCUMFLEX_ACCENT>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 
@@ -2654,7 +2654,7 @@ Like L<fff|/routine/fff>, except it does not return true for matches to the left
     say $_ if /A/ fff /C/ for @list;   # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ ^fff /C/ for @list;  # OUTPUT: «B␤C␤»
 
-For the non-sed version, see L<C<^ff>|/routine/^ff>.
+For the non-sed version, see L<C<^ff>|/routine/$CIRCUMFLEX_ACCENTff>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 
@@ -2669,7 +2669,7 @@ argument.
     say $_ if /A/ fff /C/ for @list;   # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ fff^ /C/ for @list;  # OUTPUT: «A␤B␤»
 
-For the non-sed version, see L<ff^|/routine/ff^>.
+For the non-sed version, see L<ff^|/routine/ff$CIRCUMFLEX_ACCENT>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 
@@ -2684,7 +2684,7 @@ right argument.
     say $_ if /A/ fff /C/ for @list;   # OUTPUT: «A␤B␤C␤»
     say $_ if /A/ ^fff^ /C/ for @list; # OUTPUT: «B␤»
 
-For the non-sed version, see L<C<^ff^>|/routine/^ff^>.
+For the non-sed version, see L<C<^ff^>|/routine/$CIRCUMFLEX_ACCENTff$CIRCUMFLEX_ACCENT>.
 
 This operator cannot be overloaded, as it's handled specially by the compiler.
 

doc/Language/regexes.pod6

@@ -269,7 +269,7 @@ matching a string against a regex, this powerful regex-based text destructuring
 tool can't be left out from this overview of common pattern matching methods.
 
 If you feel that your needs exceed what simple regexes have to offer, check out this
-L<grammar tutorial>|/language/grammar_tutorial> to take regexes to the next level.
+L<grammar tutorial|/language/grammar_tutorial> to take regexes to the next level.
 =end item
 
 

doc/Language/traps.pod6

@@ -155,7 +155,7 @@ instead:
 
 =head2 Using set subroutines on C<Associative> when the value is falsy
 
-Using L<(cont)|/routine/(cont) , infix  ∋>, L<∋|/routine/(cont), infix ∋>, L<∌|/routine/∌>,
+Using L<(cont)|/routine/(cont) , infix  ∋>, L<∋|/routine/(cont),%20infix%20∋>, L<∌|/routine/∌>,
 L<(elem)|/routine/(elem), infix ∈>, L<∈|/routine/(elem), infix ∈>, or L<∉|/routine/∉> on classes
 implementing L<Associative|/type/Associative> will return C<False> if the value
 of the key is falsy:

doc/Type/BagHash.pod6

@@ -12,7 +12,7 @@ them signifying how many copies of that element are considered "in the bag".
 (For I<immutable> bags, see L<Bag|/type/Bag> instead.)
 
 Objects/values of any type are allowed as bag elements.  Within a C<BagHash>,
-items that would compare positively with the L<===|/routine/===/> operator are considered the
+items that would compare positively with the L<===|/routine/===> operator are considered the
 same element, with the number of how many there were as its weight.  But of
 course you can also easily get back the expanded list of items (without the
 order):

doc/Type/independent-routines.pod6

@@ -523,7 +523,7 @@ L<run|/routine/run> in non-sink context:
 If you want to capture standard output or error instead of having it printed
 directly you can use the C<:out> or C<:err> arguments, which will make them
 available using their respective methods: L<C<Proc.out>|/type/Proc> and
-L<C<Proc.err>|/type/Proc/>.
+L<C<Proc.err>|/type/Proc>.
 
     my $proc = run 'echo', 'Raku is Great!', :out, :err;
     $proc.out.slurp(:close).say; # OUTPUT: «Raku is Great!␤»