]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
In email docs, correct spelling of foregoing (GH-9856) (#9919)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Fri, 19 Oct 2018 00:17:25 +0000 (17:17 -0700)
committerR. David Murray <rdmurray@bitdance.com>
Fri, 19 Oct 2018 00:17:25 +0000 (20:17 -0400)
(cherry picked from commit c984d20ec81609aa439ccdb3af5bc35fca0c2112)

Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>
Doc/library/email.rst

index 1033d8c130eb756c8eba57d1d4813e07d28d47e8..07d455ba39d3cc83e49fd8cf1b4b2210313772d9 100644 (file)
@@ -87,7 +87,7 @@ to advanced applications.
 Following those is a set of examples of using the fundamental parts of the APIs
 covered in the preceding sections.
 
-The forgoing represent the modern (unicode friendly) API of the email package.
+The foregoing represent the modern (unicode friendly) API of the email package.
 The remaining sections, starting with the :class:`~email.message.Message`
 class, cover the legacy :data:`~email.policy.compat32` API that deals much more
 directly with the details of how email messages are represented.  The