Issue #17193: Use binary prefixes (KiB, MiB, GiB) for memory units.

1 files changed, 4 insertions, 4 deletions

diff --git a/Doc/library/_thread.rst b/Doc/library/_thread.rst
index 751c3e8849..fae278176d 100644
--- a/Doc/library/_thread.rst
+++ b/Doc/library/_thread.rst
@@ -93,15 +93,15 @@ It defines the following constants and functions:
    Return the thread stack size used when creating new threads.  The optional
    *size* argument specifies the stack size to be used for subsequently created
    threads, and must be 0 (use platform or configured default) or a positive
-   integer value of at least 32,768 (32kB). If changing the thread stack size is
+   integer value of at least 32,768 (32 KiB). If changing the thread stack size is
    unsupported, a :exc:`RuntimeError` is raised.  If the specified stack size is
-   invalid, a :exc:`ValueError` is raised and the stack size is unmodified.  32kB
+   invalid, a :exc:`ValueError` is raised and the stack size is unmodified.  32 KiB
    is currently the minimum supported stack size value to guarantee sufficient
    stack space for the interpreter itself.  Note that some platforms may have
    particular restrictions on values for the stack size, such as requiring a
-   minimum stack size > 32kB or requiring allocation in multiples of the system
+   minimum stack size > 32 KiB or requiring allocation in multiples of the system
    memory page size - platform documentation should be referred to for more
-   information (4kB pages are common; using multiples of 4096 for the stack size is
+   information (4 KiB pages are common; using multiples of 4096 for the stack size is
    the suggested approach in the absence of more specific information).
    Availability: Windows, systems with POSIX threads.