Issue #27036: Fixed formatting references to "bytes-like object" in plural.

diff --git a/Doc/library/array.rst b/Doc/library/array.rst
index 419d584ac840fbf81c7df96d53aefbfa8cf07aef..00406e016ed9d0549922c23f75df00b9feb58948 100644 (file)
--- a/Doc/library/array.rst
+++ b/Doc/library/array.rst
@@ -91,7 +91,7 @@ Array objects support the ordinary sequence operations of indexing, slicing,
 concatenation, and multiplication.  When using slice assignment, the assigned
 value must be an array object with the same type code; in all other cases,
 :exc:`TypeError` is raised. Array objects also implement the buffer interface,
-and may be used wherever :term:`bytes-like object`\ s are supported.
+and may be used wherever :term:`bytes-like objects <bytes-like object>` are supported.
 
 The following data items and methods are also supported:
 

diff --git a/Doc/library/audioop.rst b/Doc/library/audioop.rst
index e850c3f94ab86d90b586fb15e60c32f2c5a152e4..08d5f8101681125bfd3e2fb8d12104a544ef7ef8 100644 (file)
--- a/Doc/library/audioop.rst
+++ b/Doc/library/audioop.rst
@@ -7,7 +7,7 @@
 
 The :mod:`audioop` module contains some useful operations on sound fragments.
 It operates on sound fragments consisting of signed integer samples 8, 16, 24
-or 32 bits wide, stored in :term:`bytes-like object`\ s.  All scalar items are
+or 32 bits wide, stored in :term:`bytes-like objects <bytes-like object>`.  All scalar items are
 integers, unless specified otherwise.
 
 .. versionchanged:: 3.4

diff --git a/Doc/library/base64.rst b/Doc/library/base64.rst
index 6e88a7651859de2e51f65b56328898db11c80e06..4b28b4ef0d2575ed69a2bbb48fde07df1fc43700 100644 (file)
--- a/Doc/library/base64.rst
+++ b/Doc/library/base64.rst
@@ -40,7 +40,7 @@ package instead.
    the modern interface.
 
 .. versionchanged:: 3.4
-   Any :term:`bytes-like object`\ s are now accepted by all
+   Any :term:`bytes-like objects <bytes-like object>` are now accepted by all
    encoding and decoding functions in this module.  Ascii85/Base85 support added.
 
 The modern interface provides:

diff --git a/Doc/library/binascii.rst b/Doc/library/binascii.rst
index ff2bddaf9d7f2aed03c50e3119ed6998984810da..259680f2206bd97098440c45c419795f8984629e 100644 (file)
--- a/Doc/library/binascii.rst
+++ b/Doc/library/binascii.rst
@@ -21,7 +21,7 @@ higher-level modules.
 .. note::
 
    ``a2b_*`` functions accept Unicode strings containing only ASCII characters.
-   Other functions only accept :term:`bytes-like object`\ s (such as
+   Other functions only accept :term:`bytes-like objects <bytes-like object>` (such as
    :class:`bytes`, :class:`bytearray` and other objects that support the buffer
    protocol).
 

diff --git a/Doc/library/hashlib.rst b/Doc/library/hashlib.rst
index 8eb3fd53633110dfb449652b833122ad537dcc55..900764b47f027a1df1627f137ab5a532e97af0fd 100644 (file)
--- a/Doc/library/hashlib.rst
+++ b/Doc/library/hashlib.rst
@@ -41,7 +41,7 @@ Hash algorithms
 There is one constructor method named for each type of :dfn:`hash`.  All return
 a hash object with the same simple interface. For example: use :func:`sha1` to
 create a SHA1 hash object. You can now feed this object with :term:`bytes-like
-object`\ s (normally :class:`bytes`) using the :meth:`update` method.
+objects <bytes-like object>` (normally :class:`bytes`) using the :meth:`update` method.
 At any point you can ask it for the :dfn:`digest` of the
 concatenation of the data fed to it so far using the :meth:`digest` or
 :meth:`hexdigest` methods.

diff --git a/Doc/library/io.rst b/Doc/library/io.rst
index cb3e9edf11dd4f8ad3c5a6c1e2020509d2503d20..cd81cf9c36bdcb457117ffa8ceb18f84ede4e504 100644 (file)
--- a/Doc/library/io.rst
+++ b/Doc/library/io.rst
@@ -130,7 +130,7 @@ High-level Module Interface
 In-memory streams
 ^^^^^^^^^^^^^^^^^
 
-It is also possible to use a :class:`str` or :class:`bytes`-like object as a
+It is also possible to use a :class:`str` or :term:`bytes-like object` as a
 file for both reading and writing.  For strings :class:`StringIO` can be used
 like a file opened in text mode.  :class:`BytesIO` can be used like a file
 opened in binary mode.  Both provide full read-write capabilities with random