From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Fri, 19 Oct 2018 00:17:25 +0000 (-0700) Subject: In email docs, correct spelling of foregoing (GH-9856) (#9919) X-Git-Tag: v3.7.2rc1~273 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2bc1e8c909773b4721c961d45eff7f4a41425b9b;p=thirdparty%2FPython%2Fcpython.git In email docs, correct spelling of foregoing (GH-9856) (#9919) (cherry picked from commit c984d20ec81609aa439ccdb3af5bc35fca0c2112) Co-authored-by: Cheryl Sabella --- diff --git a/Doc/library/email.rst b/Doc/library/email.rst index 1033d8c130eb..07d455ba39d3 100644 --- a/Doc/library/email.rst +++ b/Doc/library/email.rst @@ -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