Fix type formatting for several files.

(and some very minor textual cleanups)

Author: coke

doc/Language/5to6-perlfunc.rakudoc

@@ -115,7 +115,7 @@ much as possible.
 
 C<accept> is a method you can call on a server, e. g.
 C<$server.accept()>. Instead of returning a packed address, it returns a
-socket, most likely an IO::Socket object of some sort.
+socket, most likely an L<C<IO::Socket>|/type/IO:Socket> object of some sort.
 
 =head2 X<alarm|Other languages,alarm - perlfunc>
 
@@ -324,8 +324,8 @@ as much as possible.
 
 =item connect SOCKET, NAME
 
-Use L<connect|/routine/connect> from L<IO::Socket::Async|/type/IO::Socket::Async> for
-an asynchronous socket or create a L<IO::Socket::INET|/type/IO::Socket::INET> socket
+Use L<connect|/routine/connect> from L<C<IO::Socket::Async>|/type/IO::Socket::Async> for
+an asynchronous socket or create a L<C<IO::Socket::INET>|/type/IO::Socket::INET> socket
 for a synchronous one.
 
 =head2 X<continue|Other languages,continue - perlfunc>
@@ -378,7 +378,7 @@ implementation may be premature).
 
 Probably does what you expect, but technically it returns C<False> on
 the type object, and C<True> otherwise. This may make more sense when
-you realize that C<$num.raku> is the type C<Any> if you haven't assigned
+you realize that C<$num.raku> is the type L<C<Any>|/type/Any> if you haven't assigned
 anything to it, and the assigned value if you have. It can be
 used as a method: C<$num.defined>.  And any newly created class can have
 its own C<.defined> method, thereby deciding how and when it should be
@@ -562,7 +562,7 @@ much as possible.
 
 =item fileno FILEHANDLE
 
-The C<native-descriptor> method on C<IO::Handle> returns the equivalent of
+The C<native-descriptor> method on L<C<IO::Handle>|/type/IO::Handle> returns the equivalent of
 C<fileno>.
 
 The Raku ecosystem has a module L<C<P5fileno>|https://raku.land/zef:lizmat/P5fileno>
@@ -743,7 +743,7 @@ by roles like User, Group, etc.
 =item getsockopt SOCKET, LEVEL, OPTNAME
 
 [NEEDS FURTHER RESEARCH] These are likely implemented by some kind of
-IO::Socket object, but details are unclear.
+L<C<IO::Socket>|/type/IO:Socket> object, but details are unclear.
 
 =head2 X<glob|Other languages,glob - perlfunc>
 
@@ -894,7 +894,7 @@ L<NativeCall|/language/nativecall>:
     sub kill(int32, int32) is native {*};
     kill $*PID, 9; # OUTPUT: «Killed␤»
 
-To kill processes that were started by creating a L<Proc::Async|/type/Proc::Async>, use
+To kill processes that were started by creating a L<C<Proc::Async>|/type/Proc::Async>, use
 L«C<Proc::Async.kill> method|/type/Proc::Async#method_kill».
 
 =head2 X<last|Other languages,last - perlfunc>
@@ -960,7 +960,7 @@ See L<link|/routine/link>
 =item listen SOCKET, QUEUESIZE
 
 Not clearly documented, but it appears that C<listen> will be a method
-you would call on some variety of IO::Socket object.
+you would call on some variety of L<C<IO::Socket>|/type/IO:Socket> object.
 
 =head2 X<local|Other languages,local - perlfunc>
 
@@ -1005,7 +1005,7 @@ Perl behavior as much as possible.
 
 =item lock THING
 
-There currently is no equivalent for this In Raku.  There is a C<Lock>
+There currently is no equivalent for this In Raku.  There is a L<C<Lock>|/type/Lock>
 class for creating a Lock object, that can be locked/unlocked as needed.
 But such a lock does not refer to any external objects.
 
@@ -1388,7 +1388,7 @@ much as possible.
 
 =item read FILEHANDLE, SCALAR, LENGTH, OFFSET
 
-C<read> is found in C<IO::Handle> and C<IO::Socket> in Raku. It reads
+C<read> is found in L<C<IO::Handle>|/type/IO::Handle> and L<C<IO::Socket>|/type/IO:Socket> in Raku. It reads
 the specified number of bytes (rather than characters) from the relevant
 handle or socket. The use of an offset available in Perl is not
 documented to exist at this time.
@@ -1436,7 +1436,7 @@ be lurking around in some class that isn't obvious.
 
 =item recv SOCKET, SCALAR, LENGTH, FLAGS
 
-Appears to be in IO::Socket. Not extensively documented at this time.
+Appears to be in L<C<IO::Socket>|/type/IO:Socket>. Not extensively documented at this time.
 
 =head2 X<redo|Other languages,redo - perlfunc>
 
@@ -1584,7 +1584,7 @@ the function is required.
 =item seek FILEHANDLE, POSITION, WHENCE
 
 Not documented in any real way yet, but listed as a method of the
-C<IO::Handle> class.
+L<C<IO::Handle>|/type/IO::Handle> class.
 
 The Raku ecosystem has a module L<C<P5seek>|https://raku.land/zef:lizmat/P5seek>
 which exports a C<seek> function that mimics the original Perl behavior
@@ -1630,7 +1630,7 @@ No longer in core.
 
 =item send SOCKET, MSG, FLAGS, TO
 
-Can be found in the C<IO::Socket> class.
+Can be found in the L<C<IO::Socket>|/type/IO:Socket> class.
 
 =head2 X<setpgrp|Other languages,setpgrp - perlfunc>
 
@@ -1704,7 +1704,7 @@ Gone from the core. May turn up in a module somewhere.
 
 =item shutdown SOCKET, HOW
 
-Not documented, but likely moved into C<IO::Socket>.
+Not documented, but likely moved into L<C<IO::Socket>|/type/IO:Socket>.
 
 =head2 X<sin|Other languages,sin - perlfunc>
 
@@ -1744,7 +1744,7 @@ as much as possible.
 
 =item socketpair SOCKET1, SOCKET2, DOMAIN, TYPE, PROTOCOL
 
-Not currently documented, but will likely wind up in C<IO::Socket>.
+Not currently documented, but will likely wind up in L<C<IO::Socket>|/type/IO:Socket>.
 
 =head2 X<sort|Other languages,sort - perlfunc>
 
@@ -1927,7 +1927,7 @@ L<functions|/language/functions>.
 =item __SUB__
 
 Replaced by C<&?ROUTINE> which is slightly different from C<__SUB__> in
-that it is the actual C<Sub> (or C<Method>) object.  You should call the
+that it is the actual L<C<Sub>|/type/Sub> (or L<C<Method>|/type/Method>) object.  You should call the
 C<.name> method on it to get a string.
 
 The Raku ecosystem has a module L<C<P5__FILE__>|https://raku.land/zef:lizmat/P5__FILE__>
@@ -2012,7 +2012,7 @@ As with C<sysopen> and friends, this has moved into the C<IO> classes.
 
 =item tell FILEHANDLE
 
-As a method on C<IO::Handle>.
+As a method on L<C<IO::Handle>|/type/IO::Handle>.
 
 =head2 X<telldir|Other languages,telldir - perlfunc>
 
@@ -2058,7 +2058,7 @@ behavior as much as possible.
 
 =item time
 
-Number of seconds since epoch (as an C<Int>), same as in Perl.
+Number of seconds since epoch (as an L<C<Int>|/type/Int>), same as in Perl.
 
 =head2 X<times|Other languages,times - perlfunc>
 
@@ -2123,7 +2123,7 @@ C<ucfirst> function that mimics the original Perl behavior as much as possible.
 =item undef EXPR
 
 There is no C<undef> in Raku. You can't undefine a function, and the closest
-equivalent value is probably C<Nil>, but you'll likely have no use for that.
+equivalent value is probably L<C<Nil>|/type/Nil>, but you'll likely have no use for that.
 
 If you were using something like C<(undef, $file, $line) = caller;>, you would
 just get the filename and line number directly in Raku instead of discarding
@@ -2244,8 +2244,8 @@ and shaped array (aka matrix) forms.
 =item wait
 
 [NEEDS FURTHER RESEARCH] Unclear where this has gone. There's a C<wait>
-method in C<Supply>, and an C<await> method in both C<Channel> and
-C<Promise>. Which, if any or all, of these is a direct equivalent of
+method in L<C<Supply>|/type/Supply>, and an C<await> method in both L<C<Channel>|/type/Channel> and
+L<C<Promise>|/type/Promise>. Which, if any or all, of these is a direct equivalent of
 Perl's C<wait> is unclear.
 
 =head2 X<waitpid|Other languages,waitpid - perlfunc>

doc/Language/5to6-perlop.rakudoc

@@ -49,7 +49,7 @@ probably less useful as a dereferencing operator. If you do need to
 dereference something, however, the arrow is the dot. It is also the dot
 for method calls. So, Perl's C«$arrayref->[7]» becomes
 C<$arrayref.[7]> in Raku and, similarly, C«$user->name» becomes
-C<$user.name>. The C«=>» arrow is used for constructing Pairs, see
+C<$user.name>. The C«=>» arrow is used for constructing L<C<Pair>|/type/Pair>s, see
 L<Pair term documentation|/language/terms#Pair>.
 
 =head2 Auto-increment and auto-decrement
@@ -72,7 +72,7 @@ rather than "(-2)**4)") is also true for Raku.
 As in Perl, unary C<!> and C<-> do logical and arithmetic negation,
 respectively. C<?^> is used for bitwise logical negation, which the
 documentation indicates is equivalent to C<!>. It may be relevant to
-note that these coerce their arguments to C<Bool> and C<Numeric>,
+note that these coerce their arguments to L<C<Bool>|/type/Bool> and L<C<Numeric>|/type/Numeric>,
 respectively.
 
 Unary C<~> is the string context operator in Raku, so use prefix C<+^>
@@ -138,7 +138,7 @@ C<==> and C<!=> both work as in Perl.
 C«<=>» and C<cmp> have different behavior in Raku. C«<=>»
 does a numeric comparison, but returns C<Order::Less>, C<Order::Same>,
 or C<Order::More> instead of Perl's C<-1>, C<0>, or C<1>. To get the
-Perl behavior (with the change that it returns the C<Order> objects,
+Perl behavior (with the change that it returns the L<C<Order>|/type/Order> objects,
 rather than integers) of C<cmp>, you would use the C<leg> operator.
 
 C<cmp> does either C«<=>» or C<leg>, depending on the existing type
@@ -296,8 +296,8 @@ interpolate. E.g. C«@a = <1 2 3>; say qq/@a[] example@example.com/;»
 results in "1 2 3 example@example.com". Hashes interpolate in the same
 manner: C«%a = 1 => 2, 3 => 4;say "%a{}";» results in a space
 separating the pairs and tabs separating the key from the value in each
-pair (because that's the standard stringification of C<Pair>s, and a hash
-acts as list of C<Pair>s when stringified). You can also interpolate Raku
+pair (because that's the standard stringification of L<C<Pair>|/type/Pair>s, and a hash
+acts as list of L<C<Pair>|/type/Pair>s when stringified). You can also interpolate Raku
 code in strings using curly braces. For all the details, see
 L<Interpolation|/language/quoting#Interpolation%3A_qq>.
 

doc/Language/5to6-perlvar.rakudoc

@@ -64,7 +64,7 @@ regexp match (i. e. capture variables now start from C<$0> rather than C<$1>).
 =head3 $REAL_GROUP_ID, $GID, $(
 
 In Raku the group information is handled by C<$*GROUP>,
-which holds an object of type L<IntStr|/type/IntStr>
+which holds an object of type L<C<IntStr>|/type/IntStr>
 and therefore can be used either within a string
 or a numeric context.
 The group id is therefore obtained via C<+$*GROUP>, while the
@@ -77,7 +77,7 @@ The effective group id does not appear to be currently provided by Raku.
 =head3 $REAL_USER_ID, $UID, $<
 
 In Raku the user information is handled by C<$*USER>,
-which holds an object of type L<IntStr|/type/IntStr>
+which holds an object of type L<C<IntStr>|/type/IntStr>
 and therefore can be used either within a string
 or a numeric context (this is similar to how the group
 information is handled by the C<$*GROUP> object).
@@ -222,7 +222,7 @@ exact running instance, for more information use C<.^methods> to introspect all
 
 No equivalent variable. To have your code executed on the reception of a
 signal, you can call the L<signal|/routine/signal#(Supply)_sub_signal>
-subroutine, which returns a C<Supply> that can be tapped.
+subroutine, which returns a L<C<Supply>|/type/Supply> that can be tapped.
 
 =for code :lang<perl>
 $SIG{"INT"} = sub { say "bye"; exit }
@@ -247,7 +247,7 @@ react {
 =head3 $BASETIME, $^T
 
 Replaced in Raku by C<$*INIT-INSTANT>. Unlike in Perl, this is not in
-seconds since epoch, but an L<Instant|/type/Instant> object, which is measured in atomic
+seconds since epoch, but an L<C<Instant>|/type/Instant> object, which is measured in atomic
 seconds, with fractions.
 
 =head3 $PERL_VERSION, $^V
@@ -261,7 +261,7 @@ There is no analog to this in Raku.
 =head3 $EXECUTABLE_NAME, $^X
 
 This has been replaced by C<$*EXECUTABLE-NAME>.
-Note that there is also C<$*EXECUTABLE>, which is an C<IO> object in Raku.
+Note that there is also C<$*EXECUTABLE>, which is an L<C<IO>|/type/IO> object in Raku.
 
 =head2 Variables related to regular expressions
 
@@ -280,7 +280,7 @@ to C<$/[0]>, C<$1> is equivalent to C<$/[1]>, etc.
 
 =head3 $MATCH, $&
 
-C<$/> now contains the L<match|/type/Match> object, so the Perl behavior of C<$&> can
+C<$/> now contains the L<C<Match>|/type/Match> object, so the Perl behavior of C<$&> can
 be obtained by stringifying it, i. e. C<~$/>.
 
 Please note that while C<$/.Str> should also work,
@@ -316,7 +316,7 @@ Does not exist in Raku, but you can get the same information using C<$/[*-
 
 If you want to I<understand> why that works, you can look at these documents:
 
-L<[ ] routine|/routine/[ ]>, L<Whatever|/type/Whatever>,
+L<[ ] routine|/routine/[ ]>, L<C<Whatever>|/type/Whatever>,
 and the L<historical design document|https://design.raku.org/S02.html#line_1126>
 
 =head3 $LAST_SUBMATCH_RESULT, $^N
@@ -392,7 +392,7 @@ Currently no obvious equivalent.
 
 No direct replacement exists.
 
-When iterating using L<lines|/routine/lines> method from L<IO::Path|/type/IO::Path> or L<IO::Handle|/type/IO::Handle> types,
+When iterating using L<lines|/routine/lines> method from L<C<IO::Path>|/type/IO::Path> or L<C<IO::Handle>|/type/IO::Handle> types,
 you can call the C<.kv> method on it to get an interleaved list of indexes and values (then iterate by 2 each loop):
 
 =begin code
@@ -406,7 +406,7 @@ for "foo".IO.lines.kv -> $n, $line {
 # 4: d
 =end code
 
-For L<IO::CatHandle|/type/IO::CatHandle> types
+For L<C<IO::CatHandle>|/type/IO::CatHandle> types
 (of which L«C<$*ARGFILES>|/language/variables#index-entry-%24%2AARGFILES» is
 one), you can use L«C<on-switch>|/type/IO::CatHandle#method_on-switch» hook
 to reset line number on handle switch, and increment it manually.
@@ -428,7 +428,7 @@ C<$*OUT.nl-out>.
 
 No global alternative available. TTY handles are unbuffered by default, for
 others, set L<out-buffer|/routine/out-buffer> to zero or use C<:!out-buffer> with L<open|/routine/open> on a
-specific L<IO::Handle|/type/IO::Handle>.
+specific L<C<IO::Handle>|/type/IO::Handle>.
 
 =head3 ${^LAST_FH}
 
@@ -446,9 +446,9 @@ here individually.
 To quote the Raku L<docs|/language/variables#index-entry-%24!>, "$! is the error variable." That's it.
 All the error variables appear to have been eaten by $!. As with the rest of
 Raku, it's an object that will return various things depending on the type of error
-or L<exception|/type/Exception>.
+or L<C<Exception>|/type/Exception>.
 
-In particular, when dealing with L<exceptions|/type/Exception> the C<$!> provides information
+In particular, when dealing with L<C<Exception>|/type/Exception>s the C<$!> provides information
 about the thrown exception, assuming the program has not halted:
 
 =begin code