Merge pull request #2273 from MorayJ/anchor-case

Anchor case

Author: Altai-man

doc/Language/5to6-nutshell.pod6

@@ -621,7 +621,7 @@ of a list, or in passing arguments to a sub that expects a flat list of
 KEY, VALUE, KEY, VALUE, then continuing to use C«=>» may break your code.
 The easiest workaround is to change the fat comma to a regular comma, and
 manually add quotes to its left-hand side. Or, you can change the sub's API
-to L<slurp a hash|/type/Signature#Slurpy_(A.K.A._Variadic)_Parameters>.
+to L<slurp a hash|/type/Signature#Slurpy_(A.K.A._variadic)_parameters>.
 A better long-term solution is to change the sub's API to
 expect L<Pair|/type/Pair>s; however, this requires you to change
 all sub calls at once.

doc/Language/5to6-perlop.pod6

@@ -21,7 +21,7 @@ equivalents, please see the L<Perl 6 documentation|/language/operators>.
 The operator precedence table is somewhat different in Perl 6 than it is in
 Perl 5, so it will not be detail  here. If you need to know the precedence and
 associativity of a given operator in Perl 6, refer to
-L<Operator Precedence|/language/operators#Operator_Precedence>.
+L<Operator Precedence|/language/operators#Operator_precedence>.
 
 =head2 Terms and list operators
 

doc/Language/5to6-perlvar.pod6

@@ -377,7 +377,7 @@ Does not exist in Perl 6, but you can get the same information using C<$/[*-
 
 If you want to I<understand> why that works, you can look at these documents:
 
-=item L<[ ] routine|/routine/%5b%20%5d#language_documentation_operators>
+=item L<[ ] routine|/routine/%5b%20%5d#language_documentation_Operators>
 
 =item L<Whatever|/type/Whatever>
 

doc/Language/classtut.pod6

@@ -758,7 +758,7 @@ find out via introspection.
 
 Some classes might need its own version of C<gist>, which overrides the terse
 way it is printed when called to provide a default representation of the class.
-For instance, L<exceptions|/language/exceptions#Uncaught_Exceptions> might want
+For instance, L<exceptions|/language/exceptions#Uncaught_exceptions> might want
 to write just the C<payload> and not the full object so that it is clearer what
 has happened. But you can do that with every class:
 

doc/Language/containers.pod6

@@ -378,7 +378,7 @@ You'll also need to initialize the variable in the declaration, it can't be
 left undefined after all.
 
 It's also possible to have this constraint enforced in all variables declared
-in a scope with the L<default defined variables pragma|/language/variables#Default_Defined_Variables_Pragma>.
+in a scope with the L<default defined variables pragma|/language/variables#Default_defined_variables_pragma>.
 People coming from other languages where variables are always defined will
 want to have a look.
 

doc/Language/control.pod6

@@ -40,7 +40,7 @@ executed.
 Unless it stands alone as a statement, a block simply creates a closure.  The
 statements inside are not executed immediately.  Closures are another topic
 and how they are used is explained
-L<elsewhere|/language/functions#Blocks_and_Lambdas>.  For now it is just
+L<elsewhere|/language/functions#Blocks_and_lambdas>.  For now it is just
 important to understand when blocks run and when they do not:
 
 =for code
@@ -778,9 +778,9 @@ All these forms may produce a return value the same way C<loop> does.
 =head1 X<return|control flow, return>
 
 The sub C<return> will stop execution of a subroutine or method, run all
-relevant L<phasers|/language/phasers#Block_Phasers> and provide the given
+relevant L<phasers|/language/phasers#Block_phasers> and provide the given
 return value to the caller. The default return value is C<Nil>. If a return
-L<type constraint|/type/Signature#Constraining_Return_Types> is provided it
+L<type constraint|/type/Signature#Constraining_return_types> is provided it
 will be checked unless the return value is C<Nil>. If the type check fails the
 exception L<X::TypeCheck::Return|/type/X::TypeCheck::Return> is thrown. If it
 passes a control exception is raised and can be caught with
@@ -818,7 +818,7 @@ The same rules as for C<return> regarding phasers and control exceptions apply.
 Leaves the current routine and returns the provided
 L<Exception|/type/Exception> or C<Str> wrapped inside a
 L<Failure|/type/Failure>, after all relevant
-L<phasers|/language/phasers#Block_Phasers> are executed. If the caller
+L<phasers|/language/phasers#Block_phasers> are executed. If the caller
 activated fatal exceptions via the pragma C<use fatal;>, the exception is
 thrown instead of being returned as a C<Failure>.
 

doc/Language/exceptions.pod6

@@ -199,7 +199,7 @@ the C<die> statement, but not the C<E> exception. In the absence of a C<CATCH>
 block, all exceptions will be contained and dropped, as indicated above.
 C<resume> will resume execution right after the exception has been thrown; in
 this case, in the C<die> statement. Please consult the section on
-L<resuming of exceptions|/language/exceptions#Resuming_of_Exceptions>
+L<resuming of exceptions|/language/exceptions#Resuming_of_exceptions>
 for more information on this.
 
 A C<try>-block is a normal block and as such treats its last statement as the
@@ -372,7 +372,7 @@ printing a backtrace along with the message:
 
 Control exceptions are thrown by certain L<keywords|/language/phasers#CONTROL>
 and are handled either automatically or by the appropriate
-L<phaser|/language/phasers#Loop_Phasers>. Any unhandled control exception is
+L<phaser|/language/phasers#Loop_phasers>. Any unhandled control exception is
 converted to a normal exception.
 
     { return; CATCH { default { $*ERR.say: .^name, ': ',.Str } } }

doc/Language/functions.pod6

@@ -301,7 +301,7 @@ the call. Therefore a multi candidate with named parameters will be given
 precedence.
 
 For more information about type constraints see the documentation
-for the L<Signature|/type/Signature#Type_Constraints> class.
+for the L<Signature|/type/Signature#Type_constraints> class.
 
     multi as-json(Bool $d) { $d ?? 'true' !! 'false'; }
     multi as-json(Real $d) { ~$d }

doc/Language/grammars.pod6

@@ -89,7 +89,7 @@ L<Grammar|/type/Grammar> is the superclass that classes automatically get when
 they are declared with the C<grammar> keyword instead of C<class>. Grammars
 should only be used to parse text; if you wish to extract complex data, you can
 add actions within the grammar, or an
-L<action object|/language/grammars#Action_Objects> is recommended to be used in
+L<action object|/language/grammars#Action_objects> is recommended to be used in
 conjunction with the grammar. If action objects are not used, C<.parse> returns a L<Match> object and sets, by default, the
 L<default match object C<$/>|/syntax/$$SOLIDUS>, to the same value.
 

doc/Language/hashmap.pod6

@@ -286,7 +286,7 @@ then object hashes are what you are looking for.
 
 This example uses an object hash that only accepts keys of type L<Instant> to
 implement a rudimentary, yet type-safe, logging mechanism. We utilize a named
-L<state|/language/variables#The_state_Declarator> variable for keeping track of
+L<state|/language/variables#The_state_declarator> variable for keeping track of
 the previous C<Instant> so that we can provide an interval.
 
 The whole point of object hashes is to keep keys as objects-in-themselves.