bpo-41672: Fix type mismatches in imaplib docs (GH-22207) (#22218)

(cherry picked from commit c75330605d4795850ec74fdc4d69aa5d92f76c00)

Co-authored-by: Norbert Cyran <cyran.norbert97@gmail.com>
Co-authored-by: Norbert Cyran <cyran.norbert97@gmail.com>

diff --git a/Doc/library/imaplib.rst b/Doc/library/imaplib.rst
index df63d820cfe043797578b646cb4a87ac33564f9a..b3d533728df6d1d0d2ff1df49c4b753d5efa95de 100644 (file)
--- a/Doc/library/imaplib.rst
+++ b/Doc/library/imaplib.rst
@@ -132,7 +132,7 @@ The following utility functions are defined:
 
 .. function:: Int2AP(num)
 
-   Converts an integer into a string representation using characters from the set
+   Converts an integer into a bytes representation using characters from the set
    [``A`` .. ``P``].
 
 
@@ -186,7 +186,7 @@ you want to avoid having an argument string quoted (eg: the *flags* argument to
 
 Each command returns a tuple: ``(type, [data, ...])`` where *type* is usually
 ``'OK'`` or ``'NO'``, and *data* is either the text from the command response,
-or mandated results from the command. Each *data* is either a string, or a
+or mandated results from the command. Each *data* is either a ``bytes``, or a
 tuple. If a tuple, then the first part is the header of the response, and the
 second part contains the data (ie: 'literal' value).