From: Father Chrysostomos <sprout@cpan.org>
Date: Sat, 19 Nov 2011 01:57:11 +0000 (-0800)
Subject: Tweaks to find_uninit_var docs
X-Git-Tag: accepted/trunk/20130322.191538~2093
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2836693588eb28b4707239cc6f6c72b3c54749ad;p=platform%2Fupstream%2Fperl.git

Tweaks to find_uninit_var docs

• Typos
• Double space after fullstop, as that is how nroff renders
  a fullstop at the end of a line in mid-paragraph.
---

diff --git a/sv.c b/sv.c
index 3bbf5db..7cfa300 100644
--- a/sv.c
+++ b/sv.c
@@ -13833,12 +13833,12 @@ S_varname(pTHX_ const GV *const gv, const char gvtype, PADOFFSET targ,
 /*
 =for apidoc find_uninit_var
 
-Find the name of the undefined variable (if any) that caused the operator o
+Find the name of the undefined variable (if any) that caused the operator
 to issue a "Use of uninitialized value" warning.
-If match is true, only return a name if it's value matches uninit_sv.
+If match is true, only return a name if its value matches uninit_sv.
 So roughly speaking, if a unary operator (such as OP_COS) generates a
 warning, then following the direct child of the op may yield an
-OP_PADSV or OP_GV that gives the name of the undefined variable. On the
+OP_PADSV or OP_GV that gives the name of the undefined variable.  On the
 other hand, with OP_ADD there are two branches to follow, so we only print
 the variable name if we get an exact match.