format

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,9 +1,9 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Describe the bug** A clear and concise description of what the bug is.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,9 +1,9 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Is your feature request related to a problem? Please describe.** A clear and

DATA_BREACH_RESPONSE.md

@@ -7,15 +7,16 @@
 [Smart Contract Monitoring](#)
 [General Security Procedures](#)
 
-## Responsible Disclosure 
+## Responsible Disclosure
 
 Any parties who suspect a vulnerability or data breach
 should send an encrypted email to:
 
 sam bacha <sam@freighttrust.com>
 operations <admin@freighttrust.com>
 
-## Sensitive Data 
+## Sensitive Data
+
 The following is data that Freight Trust stores and considers
 sensitive. If any such data becomes accessible to an unauthenticated /
 unauthorized user, that will be considered a Data Breach:
@@ -24,19 +25,19 @@ Private repository contents (i.e. source code), whole or in "diff" form Private
 user email addresses Any secrets or tokens which grant access to the above
 
 > NOTE: Repository names, commit shas, Pull Request numbers, Pull Request
-descriptions, and GitHub user or organization names are not considered sensitive
-for the purposes of this response policy.
+> descriptions, and GitHub user or organization names are not considered sensitive
+> for the purposes of this response policy.
 
 ### Expectations In the event of a Data Breach,
 
 All running services will be stopped to prevent further access Impacted users
 will be notified by email within 24 hours, security@github.com will be notified
 within 24 hours, along with any other vendors that may be affected.
 
-### Non-Data-Breach Vulnerabilities  
+### Non-Data-Breach Vulnerabilities
 
-Freight Trust routinely monitors for patched vulnerabilities in the software 
+Freight Trust routinely monitors for patched vulnerabilities in the software
 and infrastructure it depends on. Most such vulnerabilities are not at risk of
 causing a Data Breach. In such cases, they will be patched without
 user-notification or data-breach response activities. These are published
-in our RSS Feed.
+in our RSS Feed.

DISCLAIMER.md

@@ -3,10 +3,10 @@
 **Last updated July 01, 2020**
 
 - [DISCLAIMER](#disclaimer)
-  * [WEBSITE DISCLAIMER](#website-disclaimer)
-  * [EXTERNAL LINKS DISCLAIMER](#external-links-disclaimer)
-  * [PROFESSIONAL DISCLAIMER](#professional-disclaimer)
-  * [TESTIMONIALS DISCLAIMER](#testimonials-disclaimer)
+  - [WEBSITE DISCLAIMER](#website-disclaimer)
+  - [EXTERNAL LINKS DISCLAIMER](#external-links-disclaimer)
+  - [PROFESSIONAL DISCLAIMER](#professional-disclaimer)
+  - [TESTIMONIALS DISCLAIMER](#testimonials-disclaimer)
 
 ## WEBSITE DISCLAIMER
 
@@ -55,6 +55,3 @@ extraneous information not relevant to the general public.
 The views and opinions contained in the testimonials belong solely to the individual user and do not reflect our views
 and opinions. We are not affiliated with users who provide testimonials, and users are not paid or otherwise
 compensated for their testimonials.
-
-
-

SUPPORT.md

@@ -15,12 +15,13 @@ Having a Github account is necessary for obtaining support including chat,
 troubleshooting, and issue management.
 
 - If you want to raise an issue, you can do so
-<<<<<<< HEAD
-  [on the github issue tab](https://github.com/${freight-trust}/${repository/{$ref}/issues).  
+  <<<<<<< HEAD
+  [on the github issue tab](https://github.com/${freight-trust}/${repository/{$ref}/issues).
 
 =======
-  [on the github issue tab](https://github.com/${freight-trust}/${repository/{$ref}/issues).
->>>>>>> 2.0.0
+[on the github issue tab](https://github.com/${freight-trust}/${repository/{$ref}/issues).
+
+> > > > > > > 2.0.0
 
 ### Useful support links