Fix file format checks

Author: Dindihub

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

@@ -40,7 +40,10 @@ There may also be any number of delegated target roles.
 
 Signed by: Root role.
 
-The snapshot role signs a metadata file that provides information about the latest version of all targets metadata on the repository (the top-level targets role and all delegated roles). This information allows clients to know which metadata files have been updated and also prevents mix-and-match attacks.
+The snapshot role signs a metadata file that provides information about the
+latest version of all targets metadata on the repository (the top-level targets
+role and all delegated roles). This information allows clients to know which
+metadata files have been updated and also prevents mix-and-match attacks.
 
 See
 [example](https://raw.githubusercontent.com/theupdateframework/tuf/develop/tests/repository_data/repository/metadata/root.json)

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.