perlpodspec corrections

1 files changed, 4 insertions, 4 deletions

diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index 1edd1ba7ad..8973a7080c 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -189,7 +189,7 @@ is a verbatim paragraph, because its first line starts with a literal
 whitespace character (and there's no "=begin"..."=end" region around).
 
 The "=begin I<identifier>" ... "=end I<identifier>" commands stop
-paragraphs that they surround from being parsed as data or verbatim
+paragraphs that they surround from being parsed as ordinary or verbatim
 paragraphs, if I<identifier> doesn't begin with a colon.  This
 is discussed in detail in the section
 L</About Data Paragraphs and "=beginE<sol>=end" Regions>.
@@ -337,7 +337,7 @@ paragraph.
 This command, which should occur early in the document (at least
 before any non-US-ASCII data!), declares that this document is
 encoded in the encoding I<encodingname>, which must be
-an encoding name that L<Encoding> recognizes.  (Encoding's list
+an encoding name that L<Encode> recognizes.  (Encode's list
 of supported encodings, in L<Encode::Supported>, is useful here.)
 If the Pod parser cannot decode the declared encoding, it 
 should emit a warning and may abort parsing the document
@@ -346,8 +346,8 @@ altogether.
 A document having more than one "=encoding" line should be
 considered an error.  Pod processors may silently tolerate this if
 the not-first "=encoding" lines are just duplicates of the
-first one (e.g., if there's a "=use utf8" line, and later on
-another "=use utf8" line).  But Pod processors should complain if
+first one (e.g., if there's a "=encoding utf8" line, and later on
+another "=encoding utf8" line).  But Pod processors should complain if
 there are contradictory "=encoding" lines in the same document
 (e.g., if there is a "=encoding utf8" early in the document and
 "=encoding big5" later).  Pod processors that recognize BOMs