In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/3ee1a09cee3f9a1b093b52ce2069c1d1c9b35637?hp=3916408ad57e7e4163e718920fc76f876294c442>

- Log -----------------------------------------------------------------
commit 3ee1a09cee3f9a1b093b52ce2069c1d1c9b35637
Author: SHIRAKATA Kentaro <[email protected]>
Date:   Sat Apr 18 13:46:39 2015 -0400

    Small typographical corrections to documentation.
    
    Commit modifies 4 of 5 files in patch submitted by author in RT #124335.
-----------------------------------------------------------------------

Summary of changes:
 dist/ExtUtils-ParseXS/lib/perlxstut.pod | 2 +-
 pod/perldiag.pod                        | 2 +-
 pod/perlguts.pod                        | 2 +-
 pod/perllocale.pod                      | 4 ++--
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/dist/ExtUtils-ParseXS/lib/perlxstut.pod 
b/dist/ExtUtils-ParseXS/lib/perlxstut.pod
index a254688..f8a74dd 100644
--- a/dist/ExtUtils-ParseXS/lib/perlxstut.pod
+++ b/dist/ExtUtils-ParseXS/lib/perlxstut.pod
@@ -966,7 +966,7 @@ to have write permission into the directories where Perl is 
installed,
 or ask your system administrator to run the make for you.
 
 Alternately, you can specify the exact directory to place the extension's
-files by placing a "PREFIX=/destination/directory" after the make install.
+files by placing a "PREFIX=/destination/directory" after the make install
 (or in between the make and install if you have a brain-dead version of make).
 This can be very useful if you are building an extension that will eventually
 be distributed to multiple systems.  You can then just archive the files in
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 14f1cac..3ef3ff5 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -1718,7 +1718,7 @@ workarounds.
 (F) The parser found inconsistencies either while attempting
 to define an overloaded constant, or when trying to find the
 character name specified in the C<\N{...}> escape.  Perhaps you
-forgot to load the corresponding L<overload> pragma?.
+forgot to load the corresponding L<overload> pragma?
 
 =item :const is experimental
 
diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 9761bad..5e38692 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -39,7 +39,7 @@ values that can be loaded: an integer value (IV), an unsigned 
integer
 value (UV), a double (NV), a string (PV), and another scalar (SV).
 ("PV" stands for "Pointer Value".  You might think that it is misnamed
 because it is described as pointing only to strings.  However, it is
-possible to have it point to other things  For example, it could point
+possible to have it point to other things.  For example, it could point
 to an array of UVs.  But,
 using it for non-strings requires care, as the underlying assumption of
 much of the internals is that PVs are just for strings.  Often, for
diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index 5482888..701b422 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -1251,7 +1251,7 @@ priority than C<LC_ALL>.  Moreover, it's not a single 
value but
 instead a "path" (":"-separated list) of I<languages> (not locales).
 See the GNU C<gettext> library documentation for more information.
 
-=item C<LC_CTYPE>.
+=item C<LC_CTYPE>
 
 In the absence of C<LC_ALL>, C<LC_CTYPE> chooses the character type
 locale.  In the absence of both C<LC_ALL> and C<LC_CTYPE>, C<LANG>
@@ -1285,7 +1285,7 @@ C<LANG> chooses the date and time formatting locale.
 
 C<LANG> is the "catch-all" locale environment variable. If it is set, it
 is used as the last resort after the overall C<LC_ALL> and the
-category-specific C<LC_I<foo>>
+category-specific C<LC_I<foo>>.
 
 =back
 

--
Perl5 Master Repository

Reply via email to