remove trailing ws in README

README

@@ -8,16 +8,16 @@ For more details, see the full text of the license in the file LICENSE.
 
 =head2 Build requirements
 
-For building Rakudo you need at least a C compiler, a C<make> utility, 
+For building Rakudo you need at least a C compiler, a C<make> utility,
 and Perl 5.8 or newer.  To automatically obtain and build Parrot
 or the spectest suite you may also need a subversion (svn) client.
 
 In order to fully support Unicode, you'll also want to have the
-ICU library installed (L<http://site.icu-project.org/>).  
-Rakudo can run without ICU, but some Unicode-related features 
+ICU library installed (L<http://site.icu-project.org/>).
+Rakudo can run without ICU, but some Unicode-related features
 may not work properly.
 
-As an example, on Debian GNU/Linux or Ubuntu Linux the necessary 
+As an example, on Debian GNU/Linux or Ubuntu Linux the necessary
 components for building Rakudo can be installed via the command
 
     aptitude install build-essential libicu-dev subversion
@@ -34,8 +34,8 @@ downloading Rakudo directly from github and building from there:
 
     $ git clone git://github.com/rakudo/rakudo.git
 
-If you don't have git installed, you can get a tarball or zip of Rakudo 
-from github by visiting http://github.com/rakudo/rakudo/tree/master 
+If you don't have git installed, you can get a tarball or zip of Rakudo
+from github by visiting http://github.com/rakudo/rakudo/tree/master
 and clicking "Download".  Then unpack the tarball or zip.
 
 Once you have a copy of Rakudo, build it as follows:
@@ -50,13 +50,13 @@ the build directory using a command like:
 
     $ ./perl6 hello.pl
 
-The C<--gen-parrot> above option tells Configure.pl to automatically 
-download and build the most appropriate version of Parrot into 
+The C<--gen-parrot> above option tells Configure.pl to automatically
+download and build the most appropriate version of Parrot into
 a local "parrot/" subdirectory, install that Parrot into
 the "parrot_install/" subdirectory, and use that for building
-Rakudo.  It's okay to use the C<--gen-parrot> option on later 
-invocations of Configure.pl; the configure system will re-build 
-Parrot only if a newer version is needed for whatever version 
+Rakudo.  It's okay to use the C<--gen-parrot> option on later
+invocations of Configure.pl; the configure system will re-build
+Parrot only if a newer version is needed for whatever version
 of Rakudo you're working with.
 
 You can use C<--parrot-config=/path/to/parrot_config> instead
@@ -66,34 +66,34 @@ environment; typically this is done via Parrot's C<make install-dev>
 target or by installing prebuilt C<parrot-devel> and/or C<libparrot-dev>
 packages.  The version of the already installed Parrot must satisfy a
 minimum specified by the Rakudo being built -- Configure.pl will
-verify this for you.  Released versions of Rakudo always build 
-against the latest release of Parrot; checkouts of the HEAD revision 
-from github often require a version of Parrot that is newer than 
+verify this for you.  Released versions of Rakudo always build
+against the latest release of Parrot; checkouts of the HEAD revision
+from github often require a version of Parrot that is newer than
 the most recent Parrot monthly release.
 
-Once built, Rakudo's C<make install> target will install Rakudo 
-and its libraries into the Parrot installation that was used to 
-create it.  Until this step is performed, the "perl6" executable 
+Once built, Rakudo's C<make install> target will install Rakudo
+and its libraries into the Parrot installation that was used to
+create it.  Until this step is performed, the "perl6" executable
 created by C<make> above can only be reliably run from the root of
 Rakudo's build directory.  After C<make install> is performed
-the executable can be run from any directory (as long as the 
+the executable can be run from any directory (as long as the
 Parrot installation that was used to create it remains intact).
 
 If the Rakudo compiler is invoked without an explicit script to
-run, it enters a small interactive mode that allows Perl 6 statements 
+run, it enters a small interactive mode that allows Perl 6 statements
 to be executed from the command line.  Each line entered is treated
 as a separate compilation unit, however (which means that subroutines
 are preserved after they are defined, but variables are not).
 
 =head2 Running the test suite
 
-Entering C<make test> will run a small test suite that comes 
+Entering C<make test> will run a small test suite that comes
 bundled with Rakudo.  This is a simple suite of tests, designed
 to make sure that the Rakudo compiler is basically working and that
 it's capable of running a simple test harness.
 
 Running C<make spectest> will import the official Perl 6 test suite
-from the Pugs repository L<http://svn.pugscode.org/pugs/t/spec/> 
+from the Pugs repository L<http://svn.pugscode.org/pugs/t/spec/>
 and run all of these tests that are currently known to pass.
 
 At present we do not have any plans to directly store the
@@ -103,7 +103,7 @@ but will continue to fetch it from the Pugs repository.
 You can also use "make" to run an individual test from the command line:
 
     $ make t/spec/S29-str/ucfirst.t
-    t/spec/S29-str/ucfirst.rakudo .. 
+    t/spec/S29-str/ucfirst.rakudo ..
     1..4
     ok 1 - simple
     ok 2 - empty string
@@ -154,7 +154,7 @@ Bug reports should be sent to C<rakudobug@perl.org> with the moniker
 it gets appropriately tagged in the RT system (https://rt.perl.org/rt3/).
 Please include or attach any sample source code that exhibits the
 bug, and include either the release name/date or the git commit
-identifier. You find that identifier in the first output line of 
+identifier. You find that identifier in the first output line of
 the C<git log> command.  There's no need to cc: the perl6-compiler
 mailing list, as the RT system will handle this on its own.