Fix typos.

Author: Util

doc/Language/5to6-nutshell.pod

@@ -756,7 +756,7 @@ loop using the C<.lines> method.
 Note first this common misunderstanding about the C<for> and C<foreach>
 keywords. Many programmers think that they distinguish between the C-style
 three-expression form and the list-iterator form; they do not! In fact,
-they keywords are interchangeable; the Perl 5 compiler looks for the
+the keywords are interchangeable; the Perl 5 compiler looks for the
 semi-colons within the parens to determine which type of loop to parse.
 
 The C-style three-factor form now uses the C<loop> keyword, and is

doc/Language/glossary.pod

@@ -467,7 +467,7 @@ Don't Repeat Yourself
 
 =head2 DWIM
 
-Do What I Mean.  A programmng language designer motto.
+Do What I Mean.  A programming language designer motto.
 
 =head2 flap
 

doc/Language/list.pod

@@ -406,7 +406,7 @@ eye sore than a benefit to the user.  Basically, when you see a square bracket,
 remember the invisible dollar signs.
 
 Second, remember that these invisible dollar signs also protect against
-flattenning, so you cannot really flatten the elements inside of an Array
+flattening, so you cannot really flatten the elements inside of an Array
 with a normal call to C<flat> or C<.flat>.
 
     ((1,2),$(3,4)).flat.perl.say; # (1, 2, $(3, 4)).Seq

doc/Language/nativecall.pod

@@ -392,7 +392,7 @@ keep the value it acquires when the module gets precompiled.
 
 =head2 ABI/API Version
 
-If you write C<native('foo')> NativeCall will search libfoo.so under Unix like system (libfoo.dynlib on Os X, foo.dll on win32).
+If you write C<native('foo')> NativeCall will search libfoo.so under Unix like system (libfoo.dynlib on OS X, foo.dll on win32).
 In most modern system it will require you or the user of your module to install
 the development package because it's recommended to always provide an API/ABI version to a
 shared library, so libfoo.so ends often being a symbolic link provided only by a devel package.

doc/Type/Callable.pod

@@ -12,7 +12,7 @@ L<Routine>, L<Sub>, L<Method>, L<Submethod> and L<Macro> types.
 Callables can be stored in C<&>-sigiled containers, the default type constraint
 of such a container is C<Callable>. A signature object can be used to
 force a check against the signature of the Callable to be stored into the
-congtainer.
+container.
 
 	my &a = {};
 	my &b = -> {};

doc/Type/IO.pod

@@ -45,7 +45,7 @@ outputs
 
 =head2 sub say
 
-Print the given text in human readable form, followed by a C<$*OUT.nl-out> (platform dependent newline) on C<$*OUT> (standard output). Long output may be truncted. For machine readable output use C<put>.
+Print the given text in human readable form, followed by a C<$*OUT.nl-out> (platform dependent newline) on C<$*OUT> (standard output). Long output may be truncated. For machine readable output use C<put>.
 
 With C<say>, the example code as mentioned in the C<print> section will be
 displayed as the user likely intended: