It's UTF-8, not UTF8. (Note: not s/UTF-8/UTF8/,

since that would break a lot of code.)  Also few
stray UTF16s, UTF32s, and "encoded in Unicode".

p4raw-id: //depot/perl@21198

1 files changed, 4 insertions, 4 deletions

diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index 0b35663d20..e42bd4f8be 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -335,7 +335,7 @@ paragraph.
 =item "=encoding encodingname"
 
 This command, which should occur early in the document (at least
-before any non-USASCII data!), declares that this document is
+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
 of supported encodings, in L<Encoding::Supported>, is useful here.)
@@ -352,8 +352,8 @@ 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
 may also complain if they see an "=encoding" line
-that contradicts the BOM (e.g., if a document with a UTF16LE BOM
-has an "=encoding shiftjis" line).
+that contradicts the BOM (e.g., if a document with a UTF-16LE
+BOM has an "=encoding shiftjis" line).
 
 =back
 
@@ -612,7 +612,7 @@ UTF-16.  If the file begins with the three literal byte values
  0xEF 0xBB 0xBF
 
 =for comment
- If toke.c is modified to support UTF32, add mention of those here.
+ If toke.c is modified to support UTF-32, add mention of those here.
 
 =item *