metadata 1.3 edits

pep-0426.txt

@@ -33,9 +33,9 @@ Metadata Files
 
 The syntax defined in this PEP is for use with Python distribution
 metadata files. The file format is a simple UTF-8 encoded Key: value
-format with no line length parsable by the ``email`` module with an
-appropriate ``email.policy.Policy()``.  The field names listed in the
-`Fields`_ section are used as the header names.
+format with no maximum line length. It is parsable by the ``email``
+module with an appropriate ``email.policy.Policy()``.  The field names
+listed in the `Fields`_ section are used as the header names.
 
 There are two standard locations for these metadata files:
 
@@ -52,9 +52,9 @@ binary distribution archive format).
 Encoding
 ========
 
-Metadata 1.3 files are UTF-8, with the restriction that keys must be
-ASCII. Parsers should be aware that older versions of the Metadata
-specification do not specify an encoding.
+Metadata 1.3 files are UTF-8 with the restriction that keys must be
+ASCII. Parser implementations should be aware that older versions of
+the Metadata specification do not specify an encoding.
 
 Fields
 ======
@@ -560,10 +560,10 @@ Here are some example of fields using such markers::
    Requires-Dist: bar; python_version == '2.4' or python_version == '2.5'
    Requires-External: libxslt; 'linux' in sys.platform
 
-The micro-language behind this is the simplest possible: it compares only
-strings, with the ``==`` and ``in`` operators (and their opposites), and
-with the ability to combine expressions. Parethesis are also supported for
-grouping.
+The micro-language behind this is a simple subset of Python: it compares
+only strings, with the ``==`` and ``in`` operators (and their opposites),
+and with the ability to combine expressions. Parenthesis are supported
+for grouping.
 
 The pseudo-grammar is ::