Improved code formatting

Author: Jan-Olof Hendig

doc/Language/testing.pod6

@@ -121,15 +121,15 @@ project's base directory.
 A typical test file looks something like this:
 
 =begin code :skip-test
-    use v6.c;
-    use Test;      # a Standard module included with Rakudo
-    use lib 'lib';
+use v6.c;
+use Test;      # a Standard module included with Rakudo
+use lib 'lib';
 
-    plan $num-tests;
+plan $num-tests;
 
-    # .... tests
+# .... tests
 
-    done-testing;  # optional with 'plan'
+done-testing;  # optional with 'plan'
 =end code
 
 We ensure that we're using Perl 6, via the C<use v6.c> pragma, then we load
@@ -156,19 +156,19 @@ Tests can be run individually by specifying the test filename on the
 command line:
 
 =for code :lang<shell>
-    $ perl6 t/test-filename.t
+$ perl6 t/test-filename.t
 
 Or via the L<prove|http://perldoc.perl.org/prove.html> command from Perl 5,
 where C<perl6> is specified as the executable that runs the tests:
 
 =for code :lang<shell>
-    $ prove --exec perl6 -r t
+$ prove --exec perl6 -r t
 
 To abort the test suite upon first failure, set the
 C<PERL6_TEST_DIE_ON_FAIL> environmental variable:
 
 =for code :lang<shell>
-    $ PERL6_TEST_DIE_ON_FAIL=1 perl6 t/test-filename.t
+$ PERL6_TEST_DIE_ON_FAIL=1 perl6 t/test-filename.t
 
 The same variable can be used within the test file. Set it before loading
 the C<Test> module:
@@ -404,7 +404,7 @@ and the test will fail if C<rel-diff> is higher than C<$rel-tol>.
 =head3 Both Absolute and Relative Tolerance Specified
 
 =for code :skip-test
-    is-approx $value, $expected, :rel-tol<.5>, :abs-tol<10>;
+is-approx $value, $expected, :rel-tol<.5>, :abs-tol<10>;
 
 When both absolute and relative tolerances are specified, each will be
 tested independently, and the C<is-approx> test will succeed only if both pass.
@@ -704,12 +704,12 @@ only one test will be marked TODO.
 The result from the test code above will be something like:
 
 =begin code :lang<TAP>
-    not ok 1 - my-custom-pi# TODO not yet precise enough
+not ok 1 - my-custom-pi# TODO not yet precise enough
 
-    # Failed test 'my-custom-pi'
-    # at test-todo.t line 7
-    # expected: '3.14159265358979'
-    #      got: '3'
+# Failed test 'my-custom-pi'
+# at test-todo.t line 7
+# expected: '3.14159265358979'
+#      got: '3'
 =end code
 
 Note that if you C<todo> a C<subtest>, all of the failing tests inside of it will be
@@ -770,9 +770,9 @@ If you already know the tests will fail, you can bail out of the test run
 using C<bail-out()>:
 
 =begin code
-    my $has-db-connection;
-    ...
-    $has-db-connection  or bail-out 'Must have database connection for testing';
+my $has-db-connection;
+...
+$has-db-connection  or bail-out 'Must have database connection for testing';
 =end code
 
 The function aborts the current test run, signaling failure to the harness.