Fixed the spelling mistakes and grammatical errors
@@ -22,11 +22,11 @@ databases, which in itself does not make sense because the data is about
FOSS.
National Vulnerability Database which is the primary data source for all
-things security, is not particulary catered to address FOSS security
+things security, is not particularly catered to address FOSS security
issues, because:
-1. It predates explosion of FOSS software usage
-2. It's data format reflects commercial vendor-centric point of view,
+1. It predates the explosion of FOSS software usage
+2. It's data format reflects a commercial vendor-centric point of view,
this is due to the usage of
`CPE <https://nvd.nist.gov/products/cpe>`__ to map vulnerabilities
and the packages.
@@ -42,7 +42,7 @@ The How
VulnerableCode independently aggregates many software vulnerability data
sources that can easily be recreated in a decentralized fashion. These
data sources include security advisories published by distros, package
-managers etc. Due to this the data obtained is not generalized to apply
+managers, etc. Due to this, the data obtained is not generalized to apply
for other ecosystems. This increases the accuracy as the same version of
a package across different distros may or may not be vulnerable to some
vulnerability.
@@ -53,7 +53,7 @@ This makes it really easy to answer questions like "Is package foo
vulnerable to vulnerability bar ? ".
The web interface enables community curation of data by enabling
-addition of new packages, vulnerabilities and modifying the
+the addition of new packages, vulnerabilities, and modifying the
relationships between them as shown in GIF. Along with the web interface
the API allows seamless consumption of the data.
