Fix format

Signed-off-by: Patrice Chalin <pchalin@gmail.com>

Author: chalin

analyses/2023/in-toto/survey-of-existing-doc.md

@@ -14,7 +14,7 @@ The following links are loosely sorted into conceptual categories.
 **GitHub repo for home page**: https://github.com/in-toto/in-toto.io
 
 **Specifications**  
- https://github.com/in-toto/docs/blob/master/in-toto-spec.md (also contains most
+https://github.com/in-toto/docs/blob/master/in-toto-spec.md (also contains most
 of the user doc)
 
 https://github.com/in-toto/attestation

analyses/2023/porter/analysis.md

@@ -168,12 +168,12 @@ Scale:
 
 ## Contributor documentation
 
-| Criteria                                  | 1   | 2   | 3   | 4   | 5   |
+| Criteria                                  | 1   | 2   | 3   | 4   | 5   |     |
 | ----------------------------------------- | --- | --- | --- | --- | --- | --- |
 | Communication methods documented          |     |     |     |     | ✅  | NW  |
-| Beginner friendly issue backlog           |     |     |     |     | ✅  |
-| “New contributor” getting started content |     |     |     | ✅  |     |
-| Project governance documentation          |     |     |     |     | ✅  |
+| Beginner friendly issue backlog           |     |     |     |     | ✅  |     |
+| “New contributor” getting started content |     |     |     | ✅  |     |     |
+| Project governance documentation          |     |     |     |     | ✅  |     |
 
 Scale:
 

docs/website-guidelines-checklist.md

@@ -18,23 +18,23 @@ all projects
         Unless there's a strong necessity to use CLA, we encourage projects to
         use DCO as it's easier to setup and use.
 - [ ] 2. Reference the origin company correctly (if needed)<br/> _Note_: It is
-     OK to say that, e.g., “Prometheus was originally created by SoundCloud” or
-     “Kubernetes builds upon 15 years of experience of running production
-     workloads at Google,” but the origin company should not otherwise be
-     referred to on the project homepage.
+      OK to say that, e.g., “Prometheus was originally created by SoundCloud” or
+      “Kubernetes builds upon 15 years of experience of running production
+      workloads at Google,” but the origin company should not otherwise be
+      referred to on the project homepage.
 - [ ] 3. No links or forms for capturing enterprise support leads should be
-     present<br/> _Note_: It is fine to have an enterprise support, commercial
-     partners or similar page.
+      present<br/> _Note_: It is fine to have an enterprise support, commercial
+      partners or similar page.
   - [ ] If page is present, the companies list is alphabetized or randomized on
         load.
   - [ ] If page is present, the vetting of companies listed is complete<br/>
         _Note_: Projects are welcome to outsource this vetting to CNCF staff if
         it becomes a burden.
 - [ ] 4. Links to companies offering support go to a page that at least mentions
-     support of the project
+      support of the project
 - [ ] 5. Copyright notice present at bottom of page.<br/> Copyright should be to
-     the project authors or to CNCF, not the origin company. For details, see
-     [Copyright notices](https://github.com/cncf/foundation/blob/master/copyright-notices.md).
+      the project authors or to CNCF, not the origin company. For details, see
+      [Copyright notices](https://github.com/cncf/foundation/blob/master/copyright-notices.md).
 - [ ] 6. CNCF Branding elements
   - [ ] “We are a Cloud Native Computing Foundation project.” or “We are a Cloud
         Native Computing Foundation sandbox project.” present (depending on