Even more formatting fixes

Author: Jan-Olof Hendig

doc/Language/traps.pod6

@@ -80,11 +80,11 @@ method is automatically generated.
 Thus the correct way to write method C<double> is
 
 =for code :skip-test
-    method double {
-        $!x *= 2;
-        $!y *= 2;
-        self;
-    }
+method double {
+    $!x *= 2;
+    $!y *= 2;
+    self;
+}
 
 which operates on the attributes directly.
 
@@ -116,17 +116,17 @@ since release 2016.11.
 One possible remedy is to explicitly initialize the attribute in C<BUILD>:
 
 =for code :skip-test
-    submethod BUILD(:$x) {
-        $!y = 18;
-        $!x := $x;
-    }
+submethod BUILD(:$x) {
+    $!y = 18;
+    $!x := $x;
+}
 
 which can be shortened to:
 
 =for code :skip-test
-    submethod BUILD(:$!x) {
-        $!y = 18;
-    }
+submethod BUILD(:$!x) {
+    $!y = 18;
+}
 
 Another, more general approach is to leave C<BUILD> alone, and hook into the
 C<BUILDALL> mechanism instead:
@@ -596,11 +596,11 @@ say %h.perl
 Sometimes you may need to match a generated string in a regex. The
 right way to do it is to use C<$(…)> or C«<{…}>» syntax.
 
-    =for code
-    my $x = ‘ailemac’;
-    say ‘I ♥ camelia’ ~~ / $($x.flip) /; # OUTPUT: «｢camelia｣␤»
-    my $x = ‘ailemac’;
-    say ‘I ♥ camelia’ ~~ / <{$x.flip}> /; # OUTPUT: «｢camelia｣␤»
+=for code
+my $x = ‘ailemac’;
+say ‘I ♥ camelia’ ~~ / $($x.flip) /; # OUTPUT: «｢camelia｣␤»
+my $x = ‘ailemac’;
+say ‘I ♥ camelia’ ~~ / <{$x.flip}> /; # OUTPUT: «｢camelia｣␤»
 
 However, there is a wrong way to write it, and the problem is that
 it works I<sometimes>.
@@ -609,21 +609,21 @@ Internally C«<{…}>» EVAL-s the given string inside an anonymous regex, while
 C<$(…)> lexically interpolates the given string. So C«<{…}>» immediately breaks
 with more complicated inputs. For example:
 
-    =for code :skip-test
-    my $x = ‘ailemac#’;
-    say ‘I ♥ #camelia’ ~~ / $($x.flip) /; # OUTPUT: «｢#camelia｣␤»
-    #                    ⚠ ↓↓ WRONG ↓↓ ⚠
-    say ‘I ♥ camelia’ ~~ / <{$x.flip}> /; # OUTPUT: «｢camelia｣␤»
-    # OUTPUT:
-    # ===SORRY!===
-    # Regex not terminated.
-    # at EVAL_0:1
-    # ------> anon regex { #camelia}⏏<EOL>
-    # Malformed regex
-    # at EVAL_0:1
-    # ------> anon regex { #camelia}⏏<EOL>
-    #     expecting any of:
-    #         infix stopper
+=for code :skip-test
+my $x = ‘ailemac#’;
+say ‘I ♥ #camelia’ ~~ / $($x.flip) /; # OUTPUT: «｢#camelia｣␤»
+#                    ⚠ ↓↓ WRONG ↓↓ ⚠
+say ‘I ♥ camelia’ ~~ / <{$x.flip}> /; # OUTPUT: «｢camelia｣␤»
+# OUTPUT:
+# ===SORRY!===
+# Regex not terminated.
+# at EVAL_0:1
+# ------> anon regex { #camelia}⏏<EOL>
+# Malformed regex
+# at EVAL_0:1
+# ------> anon regex { #camelia}⏏<EOL>
+#     expecting any of:
+#         infix stopper
 
 Therefore, try not to use C«<{}>» unless you really need EVAL.
 
@@ -1007,9 +1007,9 @@ can await on. The solution is even more beautiful if you are
 working in a L<react|/language/concurrency#index-entry-react> block:
 
 =begin code :skip-test
-    whenever $proc.print: “one\ntwo\nthree\nfour” {
-        $proc.close-stdin;
-    }
+whenever $proc.print: “one\ntwo\nthree\nfour” {
+    $proc.close-stdin;
+}
 =end code
 
 =head2 Using <.stdout> without <.lines>
@@ -1259,7 +1259,7 @@ The right way to do it is to I<always> check that whatever you use in
 your C<LEAVE> block is defined:
 
 =begin code :skip-test
-    LEAVE say .Int with $x
+LEAVE say .Int with $x
 =end code
 
 =head1 Unfortunate generalization