From 2af76da7b4dae90f33ee1e87d10afc6506e9b2a5 Mon Sep 17 00:00:00 2001 From: Ezio Melotti Date: Sat, 10 Aug 2013 18:47:07 +0300 Subject: [PATCH] Fix a couple of typos. --- Lib/email/architecture.rst | 6 +++--- Lib/email/generator.py | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Lib/email/architecture.rst b/Lib/email/architecture.rst index 80d24fe5b94..78572ae63b4 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 24f2abf2102..4ea0b559b99 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):