whitespace

doc/Language/5to6-perlfunc.pod6

@@ -90,8 +90,8 @@ There is more information on reading and writing files at
 L<io|/language/io>. Also, the section on C<open()>
 below may be helpful.
 
-The Perl 6 ecosystem has a module C<P5-X> that mimics the original Perl 5
-behaviour as much as possible in Perl 6.
+The Perl 6 ecosystem has a module C<P5-X> that mimics the original Perl 5
+behaviour as much as possible in Perl 6.
 
 =head2 abs
 
@@ -201,8 +201,8 @@ L«C<&?BLOCK>|/language/variables#Compile-time_variables», L«C<$?PACKAGE>|/lan
 L«C<$?FILE>|/language/variables#Compile-time_variables», and L«C<$?LINE>|/language/variables#Compile-time_variables».
 For many purposes, L<Backtrace> may provide an easier way to browse through the call stack.
 
-The Perl 6 ecosystem has a module C<P5caller> which exports a C<caller>
-function that mimics the original Perl 5 behaviour as much as possible.
+The Perl 6 ecosystem has a module C<P5caller> which exports a C<caller>
+function that mimics the original Perl 5 behaviour as much as possible.
 
 =head2 chdir
 
@@ -211,18 +211,18 @@ function that mimics the original Perl 5 behaviour as much as possible.
 Works as it does in Perl 5 but B<must> take an argument.  The behaviour
 of C<chdir()> (with regards to looking at HOME and LOGDIR) is not supported.
 
-In Perl 6, L<chdir> only changes the C<$*CWD> dynamic variable.  It does
+In Perl 6, L<chdir> only changes the C<$*CWD> dynamic variable.  It does
 B<not> actually change the default directory from the OS's point of view; the
 special dynamic-variable routine L«C<&*chdir>|/routine/&*chdir» can be used
 for that, if needed.
 
 This is done this way, because there is no concept of a "default directory
-per OS thread".  And since Perl 6 does not fork, but only does threading,
+per OS thread".  And since Perl 6 does not fork, but only does threading,
 it was felt that the "current directory" concept should be in the C<$*CWD>
 dynamic variable, which can be lexically scoped, and thus can be thread-safe.
 
-The Perl 6 ecosystem has a module C<P5chdir> which exports a C<chdir>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5chdir> which exports a C<chdir>
+function that mimics the original Perl 5 behaviour as much as possible,
 including looking at HOME and LOGDIR.
 
 =head2 chmod
@@ -245,10 +245,10 @@ method, e.g. C<$y = $x.chomp>. As with many other methods, also works
 with assignment to modify the target in place, e.g. C<$x.=chomp> results
 in C<$x> containing "howdy".
 
-Note that C<chomp()> (without arguments) is not supported in Perl 6.
+Note that C<chomp()> (without arguments) is not supported in Perl 6.
 
-The Perl 6 ecosystem has a module C<P5chomp> which exports a C<chomp>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5chomp> which exports a C<chomp>
+function that mimics the original Perl 5 behaviour as much as possible,
 
 =head2 chop
 
@@ -258,10 +258,10 @@ As with C<chomp>, in Perl 6, this returns the chopped string, rather than
 chopping in place. I. e. C<$x = "howdy";$y = chop($x);> results in C<$x>
 being "howdy" and C<$y> being "howd". Also works as a method: C<$y = $x.chop>.
 
-Note that C<chop()> (without arguments) is not supported in Perl 6.
+Note that C<chop()> (without arguments) is not supported in Perl 6.
 
-The Perl 6 ecosystem has a module C<P5chomp> which exports a C<chop>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5chomp> which exports a C<chop>
+function that mimics the original Perl 5 behaviour as much as possible,
 
 =head2 chown
 
@@ -280,10 +280,10 @@ function and a method:
     chr(65); # "A"
     65.chr;  # "A"
 
-Note that C<chr()> (without arguments) is not supported in Perl 6.
+Note that C<chr()> (without arguments) is not supported in Perl 6.
 
-The Perl 6 ecosystem has a module C<P5chr> which exports a C<chr>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5chr> which exports a C<chr>
+function that mimics the original Perl 5 behaviour as much as possible,
 
 =head2 chroot
 
@@ -298,7 +298,7 @@ Apparently this is not in Perl 6.
 As in Perl 5, closes a filehandle. Returns a boolean value. Both C<close
 $fh> and C<$fh.close> will work.
 
-Note that C<close()> (without arguments) is not supported in Perl 6.
+Note that C<close()> (without arguments) is not supported in Perl 6.
 
 =head2 closedir
 
@@ -360,10 +360,10 @@ 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
 considered undefined.
 
-Note that C<defined()> (without arguments) is not supported in Perl 6.
+Note that C<defined()> (without arguments) is not supported in Perl 6.
 
-The Perl 6 ecosystem has a module C<P5defined> which exports a C<defined>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5defined> which exports a C<defined>
+function that mimics the original Perl 5 behaviour as much as possible,
 
 =head2 delete
 
@@ -418,8 +418,8 @@ help here, as well as the design document at
 L<https://design.perl6.org/S06.html#%22Pointy_blocks%22>. There is also
 some information at L<https://en.wikibooks.org/wiki/Perl_6_Programming/Blocks_and_Closures#Pointy_Blocks>
 
-The Perl 6 ecosystem has a module C<P5each> which exports an C<each>
-function that mimics the original Perl 5 behaviour as much as possible,
+The Perl 6 ecosystem has a module C<P5each> which exports an C<each>
+function that mimics the original Perl 5 behaviour as much as possible,
 
 =head2 eof