Skip to content

Commit 903239e

Browse files
authored
fix(docs): correct typos in FAQ page (#4920)
Just some trivial typo fixes in the FAQ!
1 parent e319c2c commit 903239e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ If you are not able to get satisfaction after dealing directly with the source o
125125

126126
Yes!
127127

128-
The database in available in a GCS bucket maintained by OSV: [gs://osv-vulnerabilities](https://storage.googleapis.com/osv-vulnerabilities/index.html) (also [publicly browseable via the Google Cloud Console](https://console.cloud.google.com/storage/browser/osv-vulnerabilities) with a login)
128+
The database is available in a GCS bucket maintained by OSV: [gs://osv-vulnerabilities](https://storage.googleapis.com/osv-vulnerabilities/index.html) (also [publicly browseable via the Google Cloud Console](https://console.cloud.google.com/storage/browser/osv-vulnerabilities) with a login)
129129

130130
More information about how to download the database is available [here](data.md#data-dumps).
131131

@@ -176,7 +176,7 @@ Records that have the [`withdrawn`](https://ossf.github.io/osv-schema/#withdrawn
176176
The entry remains in the database, and is:
177177

178178
* returned by the `/vulns/<ID>` GET API
179-
* visible at `https://osv.dev/vulnerability/<ID>` page (and clearly visibly marked as "withdrawn")
179+
* visible at the `https://osv.dev/vulnerability/<ID>` page (and clearly visibly marked as "withdrawn")
180180
* still exported in the [GCS exports](#is-the-database-available-to-download) (including the `withdrawn` field)
181181

182182
### How does OSV.dev handle deleted records?

0 commit comments

Comments
 (0)