From c71ed7123ad0e47f028016ef74e6429c9dd6584f Mon Sep 17 00:00:00 2001
From: Joseph Doundoulakis <67523692+JosephDoun@users.noreply.github.com>
Date: Sun, 3 May 2026 07:08:43 +0200
Subject: [PATCH] Fix typo in ASCII encoding explanation

Corrected a typo in the explanation of 'extended ASCII'.
---
 docs/avoid.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/avoid.rst b/docs/avoid.rst
index 3a4070c5..e86a4865 100644
--- a/docs/avoid.rst
+++ b/docs/avoid.rst
@@ -64,7 +64,7 @@ A sign that something is about to go wrong with encodings is if a developer is t
 
 ASCII is a set of 128 character codes (95 of them displayable). It has not had any new characters added to it since the backslash was added in 1967.
 
-Because ASCII is a 7-bit encoding but our computers use 8-bit bytes, it seems clear that ASCII *could* be extended to assign a meaning to all 256 possible bytes. There are many different encodings that have done so, and they're all incompatible with one another, which is why treating bytes as characters as a bad idea and why we have Unicode now.
+Because ASCII is a 7-bit encoding but our computers use 8-bit bytes, it seems clear that ASCII *could* be extended to assign a meaning to all 256 possible bytes. There are many different encodings that have done so, and they're all incompatible with one another, which is why treating bytes as characters is a bad idea and why we have Unicode now.
 
 Many developers refer to one of these encodings as "extended ASCII", whose colloquial meaning is "the encoding of 256 characters that I learned first". Its meaning is completely dependent on the country you were in and the operating system you were using when you started programming: