Further C< trailing space > changes.

doc/Language/regexes-best-practices.rakudoc

@@ -191,7 +191,7 @@ Besides putting all regexes into a grammar and turning them into tokens
         token ws { <!ww> \h* }
 
 which gets called for implicit whitespace parsing. It matches when it's not
-between two word characters (C<< <!ww> >>, negated "within word" assertion),
+between two word characters (C«<!ww>», negated "within word" assertion),
 and zero or more horizontal space characters. The limitation to horizontal
 whitespace is important, because newlines (which are vertical whitespace)
 delimit records and shouldn't be matched implicitly.

doc/Language/regexes.rakudoc

@@ -1772,7 +1772,7 @@ you can reformat the time from C<HH:MM> to C<h:MM {AM,PM}> like so:
     .say;                                 # OUTPUT: «6:38 PM␤»
 
 Using the modulo C<%> operator above keeps the sample code under 80 characters,
-but is otherwise the same as C« $0 < 12 ?? $0 !! $0 - 12 ». When combined with
+but is otherwise the same as C«$0 < 12 ?? $0 !! $0 - 12». When combined with
 the power of the Parser Expression Grammars that B<really> underlies what
 you're seeing here, you can use "regular expressions" to parse pretty much any
 text out there.
@@ -2388,8 +2388,8 @@ C«<.ws>» subrule calls depending on where it occurs in the regex.
     =end code
 
 C<m:s/ photo shop /> acts the same as
-C<m/ photo <.ws> shop <.ws> />. By default, C<< <.ws> >> makes sure that
-words are separated, so C<a    b> and C<^&> will match C<< <.ws> >> in the
+C<m/ photo <.ws> shop <.ws> />. By default, C«<.ws>» makes sure that
+words are separated, so C<a    b> and C<^&> will match C«<.ws>» in the
 middle, but C<ab> won't:
 
     =begin code :allow<B>

doc/Type/Mix.rakudoc

@@ -30,7 +30,7 @@ say $recipe.total;      # OUTPUT: «0.615␤»
 C<Mix>es can be treated as object hashes using the
 L«C<{ }> postcircumfix operator|/language/operators#postcircumfix_{_}»,
 or the
-L«C< < > > postcircumfix operator|/language/operators#postcircumfix_<_>»
+L«C«< >» postcircumfix operator|/language/operators#postcircumfix_<_>»
 for literal string keys, which
 returns the corresponding numeric weight for keys that
 are elements of the mix, and C<0> for keys that aren't:

doc/Type/MixHash.rakudoc

@@ -27,7 +27,7 @@ say $recipe.total;      # OUTPUT: «0.615␤»
 C<MixHash>es can be treated as object hashes using the
 L«C<{ }> postcircumfix operator|/language/operators#postcircumfix_{_}»,
 or the
-L«C< < > > postcircumfix operator|/language/operators#postcircumfix_<_>»
+L«C«< >» postcircumfix operator|/language/operators#postcircumfix_<_>»
 for literal string keys, which
 returns the corresponding numeric weight for keys that are
 elements of the mix, and C<0> for keys that aren't. It can also be used to modify

doc/Type/Positional.rakudoc

@@ -7,7 +7,7 @@
     role Positional[::T = Mu] { ... }
 
 Role for objects which support indexing them using the
-L«C< [ ] > postcircumfix operator|/language/operators#postcircumfix_[_]»
+L«C<[ ]> postcircumfix operator|/language/operators#postcircumfix_[_]»
 (usually list-like objects). Example types with Positional role
 include L<List|/type/List>, L<Array|/type/Array>, L<Range|/type/Range>,
 and L<Buf|/type/Buf>.

doc/Type/Range.rakudoc

@@ -482,7 +482,7 @@ point of a L<Range|/type/Range> to be compared with the other operand.
 A L«C<Positional>|/type/Positional» operand will be compared with the
 list returned by the L«C<.list> method|/type/Range#method_list»
 applied to the other operand.
-See L«C<< List infix:<cmp> >>|/type/List#infix_cmp»
+See L«C«List infix:<cmp>»|/type/List#infix_cmp»
 
     say (1..2) cmp (1..2); # OUTPUT: «Same␤»
     say (1..2) cmp (1..3); # OUTPUT: «Less␤»

doc/Type/Str.rakudoc

@@ -1201,7 +1201,7 @@ changes:
 
 In this case, neither origin nor target in the C<Pair> are C<Str>; the method
 with the C<Pair> signature then calls the second, making this call above
-equivalent to C«"abcd".trans: ["a"] => ["zz"], » (with the comma behind, making
+equivalent to C«"abcd".trans: ["a"] => ["zz"],» (with the comma behind, making
 it a C<Positional>, instead of a C<Pair>), resulting in the behavior shown as
 output.
 

doc/Type/X/Syntax/Number/RadixOutOfRange.rakudoc

@@ -7,7 +7,7 @@
     class X::Syntax::Number::RadixOutOfRange does X::Syntax { }
 
 Syntax error that is thrown when the radix of a radix number is
-not allowed, like C<< :1<1> >> or C<< :42<ouch> >>.
+not allowed, like C«:1<1>» or C«:42<ouch>».
 
 =head1 Methods
 

doc/Type/X/Syntax/Variable/Match.rakudoc

@@ -6,7 +6,7 @@
 
     class X::Syntax::Variable::Match does X::Syntax { }
 
-Syntax error thrown when a match variable like C<< $<thing> >> was declared.
+Syntax error thrown when a match variable like C«$<thing>» was declared.
 
 For example
 

doc/Type/independent-routines.rakudoc

@@ -432,8 +432,8 @@ note 'foo'; # STDERR OUTPUT: «foo␤»
 note 1..*;  # STDERR OUTPUT: «1..Inf␤»
 =end code
 
-This command will also autothread on C<Junction>s, and is guaranteed to call C<
-gist> on the object if it's a subclass of C<Str>.
+This command will also autothread on C<Junction>s, and is guaranteed to call
+C<gist> on the object if it's a subclass of C<Str>.
 
 =head2 sub prompt