Fix MD lint issues (#2)

* fix lint Signed-off-by: Avishay <avishay.balter@gmail.com> * charter updated Signed-off-by: Avishay <avishay.balter@gmail.com> --------- Signed-off-by: Avishay <avishay.balter@gmail.com>
ossf · May 1, 2023 · 1233fa3 · 1233fa3
1 parent e71232f
commit 1233fa3
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/CHARTER.md b/CHARTER.md
@@ -2,7 +2,7 @@
 
 ## Memory Safety SIG
 
-Adopted [DATE]
+Adopted 03.28.2023
 
 This Technical Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the Memory Safety SIG open source community, which has been established as a Special Interest Group (SIG) (the "Technical Initiative") under the Open Source Security Foundation (the “OpenSSF”). All contributors (including committers, maintainers, and other technical positions) and other participants in the Technical Initiative (collectively, “Collaborators”) must comply with the terms of this Technical Charter and the OpenSSF Charter.
 

diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@ The Memory Safety SIG is a group working within the [OpenSSF's Best Practices Wo
 
 ## **Motivation**
 
-Memory safety vulnerabilities, caused by mistakes in memory management, are common in unsafe programming languages like C and C++.This type of vulnerability is responsible for a majority of security breaches, with estimates from Microsoft and Google showing that up to 70% and 90% of vulnerabilities in their products, respectively, are memory safety vulnerabilities. 
+Memory safety vulnerabilities, caused by mistakes in memory management, are common in unsafe programming languages like C and C++.This type of vulnerability is responsible for a majority of security breaches, with estimates from Microsoft and Google showing that up to 70% and 90% of vulnerabilities in their products, respectively, are memory safety vulnerabilities.
 
 Memory safe languages like Rust, Go, and Java are less prone to these types of errors. The consequences of these vulnerabilities are not just technical, but can result in significant financial losses and invasion of personal data and privacy. A recent analysis by Google Project Zero showed that 67% of vulnerabilities exploited in the wild were due to a lack of memory safety, making it a critical issue that needs to be addressed in software development.