From 1dba5f2c0d36117cef285d25f9c857c81982035d Mon Sep 17 00:00:00 2001 From: Terry Jan Reedy Date: Fri, 24 Sep 2021 21:56:09 -0400 Subject: [PATCH] bpo-45277: Fix typo in codecs doc (GH-28555) encoding => encode (cherry picked from commit 4c0fc65cd8a6d4c18330505576ccd4b46abeec1c) Co-authored-by: Terry Jan Reedy --- Doc/library/codecs.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/codecs.rst b/Doc/library/codecs.rst index 0dcd88f9fd5b7f..ef71832bcef1d3 100644 --- a/Doc/library/codecs.rst +++ b/Doc/library/codecs.rst @@ -923,7 +923,7 @@ it's a device to determine the storage layout of the encoded bytes, and vanishes once the byte sequence has been decoded into a string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a normal character that will be decoded like any other. -There's another encoding that is able to encoding the full range of Unicode +There's another encoding that is able to encode the full range of Unicode characters: UTF-8. UTF-8 is an 8-bit encoding, which means there are no issues with byte order in UTF-8. Each byte in a UTF-8 byte sequence consists of two parts: marker bits (the most significant bits) and payload bits. The marker bits