Merge pull request python#17 from joshuagl/joshuagl/tweaks

Minor tweaks

Author: trishankatdatadog

pep-0458.txt

@@ -147,8 +147,8 @@ interpreted as described in RFC 2119__.
 __ http://www.ietf.org/rfc/rfc2119.txt
 
 This PEP focuses on integrating TUF with PyPI; however, the reader is
-encouraged to read about TUF's design principles [2]_.  It is also RECOMMENDED
-that the reader be familiar with the TUF specification [16]_.
+encouraged to read about TUF's design principles [2]_ and SHOULD be
+familiar with the TUF specification [16]_.
 
 Terms used in this PEP are defined as follows:
 
@@ -385,7 +385,7 @@ client library inside the package manager then loads the *root* metadata and dow
 the rest of the roles, including updating the *root* metadata if it has changed.
 An `outline of the update process`__ is available.
 
-__ https://github.com/theupdateframework/specification/blob/master/tuf-spec.md#5-detailed-workflows.
+__ https://github.com/theupdateframework/specification/blob/master/tuf-spec.md#5-detailed-workflows
 
 
 Minimum Security Model
@@ -473,9 +473,9 @@ PyPI and Key Requirements
 
 In this section, the kinds of keys required to sign for TUF roles on PyPI are
 examined.  TUF is agnostic with respect to choices of digital signature
-algorithms.  For the purpose of discussion, it is assumed that most digital
-signatures will be produced the ed25519 algorithm [25]_ as this algorithm has 
-native and well-tested Python support.
+algorithms.  For the purpose of discussion, it is assumed that all digital
+signatures will be produced with the Ed25519 algorithm [25]_ as this algorithm
+has native and well-tested Python support.
 Nevertheless, we do NOT recommend any particular digital signature algorithm in
 this PEP because there are a few important constraints: first, cryptography
 changes over time; and second, TUF