documentation wording fix for issue4903
diff --git a/Doc/library/binascii.rst b/Doc/library/binascii.rst
index 39130a8..83dcb67 100644
--- a/Doc/library/binascii.rst
+++ b/Doc/library/binascii.rst
@@ -120,11 +120,11 @@
To generate the same numeric value across all Python versions and
platforms use crc32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
- return value will have the correct 32bit binary representation
+ return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
- The return value will always be unsigned and in the range [0, 2**32-1]
+ The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.
diff --git a/Doc/library/zlib.rst b/Doc/library/zlib.rst
index b5875ee..2ab1450 100644
--- a/Doc/library/zlib.rst
+++ b/Doc/library/zlib.rst
@@ -48,11 +48,11 @@
To generate the same numeric value across all Python versions and
platforms use adler32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
- return value will have the correct 32bit binary representation
+ return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
- The return value will always be unsigned and in the range [0, 2**32-1]
+ The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.
@@ -93,11 +93,11 @@
To generate the same numeric value across all Python versions and
platforms use crc32(data) & 0xffffffff. If you are only using
the checksum in packed binary format this is not necessary as the
- return value will have the correct 32bit binary representation
+ return value is the correct 32bit binary representation
regardless of sign.
.. versionchanged:: 3.0
- The return value will always be unsigned and in the range [0, 2**32-1]
+ The return value is unsigned and in the range [0, 2**32-1]
regardless of platform.