whitespace

doc/Language/5to6-perlfunc.pod6

@@ -353,7 +353,7 @@ much as possible.
 
 =item crypt PLAINTEXT, SALT
 
-Not available in Perl 6.
+Not available in Perl 6.
 
 The Perl 6 ecosystem has a module L<C<P5math>|https://modules.perl6.org/dist/P5math>
 which exports a C<crypt> function that mimics the original Perl 5 behaviour as
@@ -1002,7 +1002,7 @@ But such a lock does not refer to any external objects.
 
 =item log EXPR
 
-Same as in Perl 5.
+Same as in Perl 5.
 
 C<log> also operates on C<$_> in the absence of a value, but not as a
 function, and as a method you need to call it as C<.log> rather than simply
@@ -1703,7 +1703,7 @@ Not documented, but likely moved into C<IO::Socket>.
 
 =item sin EXPR
 
-Same as in Perl 5.
+Same as in Perl 5.
 
 C<sin> also operates on C<$_> in the absence of a value, but not as a
 function, and as a method you need to call it as C<.sin> rather than simply
@@ -1845,7 +1845,7 @@ semantics aren't settled:
 
 =item sqrt EXPR
 
-Same as in Perl 5.
+Same as in Perl 5.
 
 C<sqrt> also operates on C<$_> in the absence of a value, but not as a
 function, and as a method you need to call it as C<.sqrt> rather than simply

doc/Language/containers.pod6

@@ -4,7 +4,7 @@
 
 =SUBTITLE A low-level explanation of Perl 6 containers
 
-This section explains the levels of indirection involved in dealing with variables and container elements. The difference types of containers used in Perl 6 are explained and the actions applicable to them like assigning, binding and flattening. More advanced topics like self-referencial data, type contraints and custom containers are discussed at the end.
+This section explains the levels of indirection involved in dealing with variables and container elements. The difference types of containers used in Perl 6 are explained and the actions applicable to them like assigning, binding and flattening. More advanced topics like self-referencial data, type contraints and custom containers are discussed at the end.
 
 =head1 What is a variable?
 

doc/Language/glossary.pod6

@@ -1051,7 +1051,7 @@ Classes doing the roles L<Numeric|/type/Numeric> and L<Stringy|/type/Stringy> ar
 
 A value type is created by ensuring that an instance of the value type is immutable (i.e., its attributes cannot be modified after construction) and that its L«C<WHICH>|/routine/WHICH» method returns the same thing every time an instance with the same value is constructed (and conversely returns a different thing every time an instance with a different value is constructed).
 
-The language is free to optimize based on the assumption that equivalent instances of value types are interchangeable, but you should not depend on any such optimization. For instance, if you want L«C<clone>|/routine/clone» to return an instance of C<self>, 
+The language is free to optimize based on the assumption that equivalent instances of value types are interchangeable, but you should not depend on any such optimization. For instance, if you want L«C<clone>|/routine/clone» to return an instance of C<self>,
 or you want instance construction to be L<memoized|https://en.wikipedia.org/wiki/Memoization> so that re-construction of a previously-constructed value always returns the same instance, you currently must override this behavior yourself.
 
 (The same would hold true of object finalization, but if your instances need special destruction behavior, you almost certainly do not actually have a value type. Values should be thought of as "timeless" and existing in some ideal form outside of your program's memory, like natural values are.)