[3.15] gh-155193: Fix the *canonical* decoder lists in the 3.15 What's New and NEWS (GH-156302) (#156370)

gh-155193: Fix the *canonical* decoder lists in the 3.15 What's New and NEWS (GH-156302)
(cherry picked from commit 5f31aee)

Co-authored-by: Advit Arora <advitarora2@gmail.com>

Author: miss-islington

Doc/whatsnew/3.15.rst

@@ -1001,7 +1001,7 @@ base64
 
 * Added the *canonical* parameter in
   :func:`~base64.b32decode`, :func:`~base64.b32hexdecode`,
-  :func:`~base64.b64decode`, :func:`~base64.urlsafe_b64decode`,
+  :func:`~base64.b64decode`,
   :func:`~base64.a85decode`, :func:`~base64.b85decode`, and
   :func:`~base64.z85decode`,
   to reject encodings with non-zero padding bits or other non-canonical

Misc/NEWS.d/3.15.0b1.rst

@@ -1081,10 +1081,10 @@ Deprecate :meth:`http.cookies.Morsel.js_output` and
 .. nonce: iHWO0v
 .. section: Library
 
-Add a *canonical* keyword-only parameter to the base16, base32, base64,
-base85, ascii85, and Z85 decoders in :mod:`base64` and :mod:`binascii`. When
-true, encodings with non-zero padding bits (base16/32/64) or non-canonical
-encodings (base85/ascii85) are rejected.  Single-character final groups in
+Add a *canonical* keyword-only parameter to the base32, base64, base85,
+ascii85, and Z85 decoders in :mod:`base64` and :mod:`binascii`. When true,
+encodings with non-zero padding bits (base32/64) or non-canonical encodings
+(base85/ascii85) are rejected.  Single-character final groups in
 :func:`binascii.a2b_ascii85` and :func:`binascii.a2b_base85` are now always
 rejected as encoding violations, regardless of *canonical*; previously they
 were silently ignored and produced no output bytes.