Update Snap role section in Metadata from Spec file (#122)

Author: lukpueh

content/en/about.md

@@ -17,11 +17,12 @@ To learn more, see [TUF overview](/docs/overview/) and
 
 ## Governance
 
-The TUF project is managed by the [Linux Foundation] under the [Cloud Native Computing
-Foundation][CNCF]. The consensus builder for TUF is [Prof. Justin Cappos] of the
-[Secure Systems Lab] at [New York University](https://engineering.nyu.edu/). Project
-maintainers <sup>[[1]][[2]]</sup> are comprised of collaborators from academia and
-the industry. Contributors and maintainers are governed by the [CNCF Community Code
+The TUF project is managed by the [Linux Foundation] under the [Cloud Native
+Computing Foundation][CNCF]. The consensus builder for TUF is [Prof. Justin
+Cappos] of the [Secure Systems Lab] at
+[New York University](https://engineering.nyu.edu/). Project maintainers
+<sup>[[1]][[2]]</sup> are comprised of collaborators from academia and the
+industry. Contributors and maintainers are governed by the [CNCF Community Code
 of Conduct][CoC]. For details, see [Governance].
 
 ## Funding

content/en/docs/metadata.md

@@ -101,8 +101,8 @@ of a nested delegation.
 
 Signed by: Snapshot role.
 
-The snapshot.json metadata file lists version numbers of all metadata files
-other than timestamp.json. This file ensures that clients will see a consistent
+The snapshot.json metadata file lists version numbers and/or hashes of all of
+the targets metadata files. This file ensures that clients will see a consistent
 view of all files on the repository. That is, metadata files (and thus Target
 files) that existed on the repository at different times cannot be combined and
 presented to clients by an attacker.

content/en/docs/project/_index.md

@@ -9,11 +9,11 @@ The TUF project consists of three components:
 - [Specification] – the detailed TUF specification describes how to add TUF
   metadata to a repository and the process to arrange for clients to use that
   metadata to download and verify targets.
-- [Standardization process] – major changes to the specification, including new features,
-  are made as TUF Augmentation Proposals (TAPs).
+- [Standardization process] – major changes to the specification, including new
+  features, are made as TUF Augmentation Proposals (TAPs).
 - [Reference implementation] – python-tuf provides a reference implementation of
-  the TUF specification and is used as a vital part of the TAPs process to prototype
-  changes to the specification.
+  the TUF specification and is used as a vital part of the TAPs process to
+  prototype changes to the specification.
 
 The project is currently managed by a team of collaborators from academia and
 industry.