rename byte:: to bytes::

p4raw-id: //depot/perl@5133

4 files changed, 9 insertions, 9 deletions

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 3a2c296c91..9e0d0c3f7e 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -380,8 +380,8 @@ building and installing from source, the defaults should be fine.
 =head2 Unicode and UTF-8 support
 
 Perl can optionally use UTF-8 as its internal representation for character
-strings.  The C<utf8> and C<byte> pragmas are used to control this support
-in the current lexical scope.  See L<perlunicode>, L<utf8> and L<byte> for
+strings.  The C<utf8> and C<bytes> pragmas are used to control this support
+in the current lexical scope.  See L<perlunicode>, L<utf8> and L<bytes> for
 more information.
 
 =head2 Interpreter cloning, threads, and concurrency
diff --git a/pod/perltoc.pod b/pod/perltoc.pod
index 2f8f3a27af..461982a1fe 100644
--- a/pod/perltoc.pod
+++ b/pod/perltoc.pod
@@ -3878,7 +3878,7 @@ method, locked
 
 =back
 
-=head2 byte - Perl pragma to turn force treating strings as bytes not
+=head2 bytes - Perl pragma to turn force treating strings as bytes not
 UNICODE
 
 =over
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index bc880364d3..c5ffbaf0e4 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -36,8 +36,8 @@ global flag is set to C<1>), all system calls will use the
 corresponding wide character APIs.  This is currently only implemented
 on Windows.
 
-Regardless of the above, the C<byte> pragma can always be used to force
-byte semantics in a particular lexical scope.  See L<byte>.
+Regardless of the above, the C<bytes> pragma can always be used to force
+byte semantics in a particular lexical scope.  See L<bytes>.
 
 The C<utf8> pragma is primarily a compatibility device that enables
 recognition of UTF-8 in literals encountered by the parser.  It is also
@@ -53,7 +53,7 @@ the input data came from a Unicode source (for example, by adding a
 character encoding discipline to the filehandle whence it came, or a
 literal UTF-8 string constant in the program), character semantics
 apply; otherwise, byte semantics are in effect.  To force byte semantics
-on Unicode data, the C<byte> pragma should be used.
+on Unicode data, the C<bytes> pragma should be used.
 
 Under character semantics, many operations that formerly operated on
 bytes change to operating on characters.  For ASCII data this makes
@@ -227,6 +227,6 @@ tend to run slower.  Avoidance of locales is strongly encouraged.
 
 =head1 SEE ALSO
 
-L<byte>, L<utf8>, L<perlvar/"${^WIDE_SYSTEM_CALLS}">
+L<bytes>, L<utf8>, L<perlvar/"${^WIDE_SYSTEM_CALLS}">
 
 =cut
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index f8b9c26323..7c499bc7db 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -924,8 +924,8 @@ The initial value is typically C<0> for compatibility with Perl versions
 earlier than 5.6, but may be automatically set to C<1> by Perl if the system
 provides a user-settable default (e.g., C<$ENV{LC_CTYPE}>).
 
-The C<byte> pragma always overrides the effect of this flag in the current
-lexical scope.  See L<byte>.
+The C<bytes> pragma always overrides the effect of this flag in the current
+lexical scope.  See L<bytes>.
 
 =item $EXECUTABLE_NAME