summaryrefslogtreecommitdiff
path: root/Lib/email
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2013-08-10 18:47:37 +0300
committerEzio Melotti <ezio.melotti@gmail.com>2013-08-10 18:47:37 +0300
commit08a1472e65fc0a471924caa406a3b9a6ac755c67 (patch)
treeb3a4cfd7db0062774927a9a289ac0f0ea0601e17 /Lib/email
parent8281e7c24c08debff65f41a1e8c81ba8e6d5250b (diff)
parent2af76da7b4dae90f33ee1e87d10afc6506e9b2a5 (diff)
downloadcpython-git-08a1472e65fc0a471924caa406a3b9a6ac755c67.tar.gz
Merge typo fixes from 3.3.
Diffstat (limited to 'Lib/email')
-rw-r--r--Lib/email/architecture.rst6
-rw-r--r--Lib/email/generator.py2
2 files changed, 4 insertions, 4 deletions
diff --git a/Lib/email/architecture.rst b/Lib/email/architecture.rst
index 80d24fe5b9..78572ae63b 100644
--- a/Lib/email/architecture.rst
+++ b/Lib/email/architecture.rst
@@ -24,9 +24,9 @@ The email package consists of three major components:
Conceptually the package is organized around the model. The model provides both
"external" APIs intended for use by application programs using the library,
and "internal" APIs intended for use by the Parser and Generator components.
-This division is intentionally a bit fuzy; the API described by this documentation
-is all a public, stable API. This allows for an application with special needs
-to implement its own parser and/or generator.
+This division is intentionally a bit fuzzy; the API described by this
+documentation is all a public, stable API. This allows for an application
+with special needs to implement its own parser and/or generator.
In addition to the three major functional components, there is a third key
component to the architecture:
diff --git a/Lib/email/generator.py b/Lib/email/generator.py
index 24f2abf210..4ea0b559b9 100644
--- a/Lib/email/generator.py
+++ b/Lib/email/generator.py
@@ -349,7 +349,7 @@ class Generator:
# This used to be a module level function; we use a classmethod for this
# and _compile_re so we can continue to provide the module level function
# for backward compatibility by doing
- # _make_boudary = Generator._make_boundary
+ # _make_boundary = Generator._make_boundary
# at the end of the module. It *is* internal, so we could drop that...
@classmethod
def _make_boundary(cls, text=None):