From: Gregory P. Smith <greg@mad-scientist.com>
Date: Sun, 1 Feb 2009 00:30:50 +0000 (+0000)
Subject: documentation wording fix for issue4903
X-Git-Tag: v3.1a1~333
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fa6cf39e7095d4fba72d0364054512d17b9c3e60;p=python

documentation wording fix for issue4903
---

diff --git a/Doc/library/binascii.rst b/Doc/library/binascii.rst
index 39130a85a6..83dcb67ec6 100644
--- a/Doc/library/binascii.rst
+++ b/Doc/library/binascii.rst
@@ -120,11 +120,11 @@ The :mod:`binascii` module defines the following functions:
    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 b5875ee037..2ab145081e 100644
--- a/Doc/library/zlib.rst
+++ b/Doc/library/zlib.rst
@@ -48,11 +48,11 @@ The available exception and functions in this module are:
    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 @@ The available exception and functions in this module are:
    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.