Grammatical correction only.

Sentences ending with a parenthetical phrase that ends
with an abbreviation such as 'etc.' still require a period
outside of the parentheses.

See https://english.stackexchange.com/a/23025/306017

For: RT 133820.  Christopher Chavez is now a Perl author.

diff --git a/AUTHORS b/AUTHORS
index a752a5e..20ce586 100644 (file)
--- a/AUTHORS
+++ b/AUTHORS
@@ -246,6 +246,7 @@ Christian Millour           <cm.perl@abtela.com>
 Christian Winter               <bitpoet@linux-config.de>
 Christoph Lamprecht            <ch.l.ngre@online.de>
 Christophe Grosjean            <christophe.grosjean@gmail.com>
+Christopher Chavez             <chrischavez@gmx.us>
 Christopher Chan-Nui           <channui@austin.ibm.com>
 Christopher Davis              <ckd@loiosh.kei.com>
 Christopher J. Madsen          <perl@cjmweb.net>

diff --git a/Porting/todo.pod b/Porting/todo.pod
index 6493d48..4905e23 100644 (file)
--- a/Porting/todo.pod
+++ b/Porting/todo.pod
@@ -1050,7 +1050,7 @@ The old perltodo notes "Look at the "reification" code in C<av.c>".
 Implement a set of "vtables" that virtualizes operating system access
 (chdir(), chmod(), dbmopen(), getenv(), glob(), link(), mkdir(), open(),
 opendir(), readdir(), rename(), rmdir(), stat(), sysopen(), uname(),
-unlink(), etc.)  At the very least these interfaces should take SVs as
+unlink(), etc.).  At the very least these interfaces should take SVs as
 "name" arguments instead of bare char pointers; probably the most
 flexible and extensible way would be for the Perl-facing interfaces to
 accept HVs.  The system needs to be per-operating-system and

diff --git a/dist/Locale-Maketext/lib/Locale/Maketext/TPJ13.pod b/dist/Locale-Maketext/lib/Locale/Maketext/TPJ13.pod
index 8d3eae6..7025b7f 100644 (file)
--- a/dist/Locale-Maketext/lib/Locale/Maketext/TPJ13.pod
+++ b/dist/Locale-Maketext/lib/Locale/Maketext/TPJ13.pod
@@ -303,7 +303,7 @@ like "How do I get to the marketplace?" that don't have any blanks to
 fill in, and ones like "How much do these ___ cost?", where there's
 one or more blanks to fill in (and these are usually linked to a
 list of words that you can put in that blank: "fish", "potatoes",
-"tomatoes", etc.)  The ones with no blanks are no problem, but the
+"tomatoes", etc.).  The ones with no blanks are no problem, but the
 fill-in-the-blank ones may not be really straightforward. If it's a
 Swahili phrasebook, for example, the authors probably didn't bother to
 tell you the complicated ways that the verb "cost" changes its

diff --git a/pod/perlop.pod b/pod/perlop.pod
index d05155d..af695b6 100644 (file)
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -593,7 +593,7 @@ type information to select a suitable comparison mechanism.
 
 The C<~~> operator compares its operands "polymorphically", determining how
 to compare them according to their actual types (numeric, string, array,
-hash, etc.)  Like the equality operators with which it shares the same
+hash, etc.).  Like the equality operators with which it shares the same
 precedence, C<~~> returns 1 for true and C<""> for false.  It is often best
 read aloud as "in", "inside of", or "is contained in", because the left
 operand is often looked for I<inside> the right operand.  That makes the