Fix xref links

Author: stoned

doc/Language/compilation.pod6

@@ -29,7 +29,7 @@ top level programs run quickly.
 One of the great strengths of the C<Perl> family of languages was the ability to integrate a whole ecosystem of modules
 written by competent programmers into a small program. This strength was widely copied and is now the norm for all
 languages. C<Raku> takes integration even further, making it relatively easy for C<Raku> programs to incorporate system
-libraries written in other languages into C<Raku> programs, see L<Native Call|Language/nativecall>.
+libraries written in other languages into C<Raku> programs, see L<Native Call|/language/nativecall>.
 
 The experience from C<Perl> and other languages is that the distributive nature of Modules generate several practical difficulties:
 =item a popular module may go through several iterations as the API gets improved, without a guarantee that there is
@@ -46,7 +46,7 @@ So it is not possible simply to have only one version of a module with a single
 
 C<Raku> enables all of these possibilities, allowing for multiple versions, multiple authorities, and multiple APIs to be present,
 installed, and available locally. The way classes and modules can be accessed with specific attributes
-is explained L<elsewhere|Language/typesystem#Versioning_and_authorship>. This tutorial is about how C<Raku> handles these
+is explained L<elsewhere|/language/typesystem#Versioning_and_authorship>. This tutorial is about how C<Raku> handles these
 possibilities.
 
 =head1 Introduction