Fix typos

mergestat · Oct 16, 2023 · 779b903 · 779b903
1 parent 4094a8b
commit 779b903
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/blog/2023-01-24-github-advisories-with-sql/index.md b/blog/2023-01-24-github-advisories-with-sql/index.md
@@ -206,7 +206,7 @@ LIMIT 10
 This has been a high level view of *all* the advisories found in a specific GitHub-maintained [public database](https://github.com/github/advisory-database/).
 To examine the advisories that impact your organization or team, you'd want to join the data in this repository with information about what packages your code brings in - potentially by using SBOMs or even parsing package manifests.
 
-Tools such as [Dependabot](https://github.com/features/security) already do this for the GitHub ecosystem, and automate the maintainence of dependencies as well.
+Tools such as [Dependabot](https://github.com/features/security) already do this for the GitHub ecosystem, and automate the maintenance of dependencies as well.
 There are, however, [other databases](https://github.com/aquasecurity/vuln-list) and ecosystems emerging that track advisories and vulnerabilities.
 [MergeStat](https://github.com/mergestat/mergestat) supports [some](https://github.com/mergestat/mergestat/blob/main/internal/syncer/trivy_repo_scan.go) of these tools today, and we are working to make it possible for anyone to easily bring the [output of their own selection of tools](https://github.com/mergestat/mergestat/discussions/704) in.
 We believe the easier it is to access data involved in key aspects of the software-supply-chain, the more secure and the more effective engineering organizations may be.

diff --git a/blog/2023-02-13-open-source-vulnerability-management/index.md b/blog/2023-02-13-open-source-vulnerability-management/index.md
@@ -111,7 +111,7 @@ ORDER BY count(*) DESC
 ```
 
 ```sql
--- Count of grype vulnerabilties by id
+-- Count of grype vulnerabilities by id
 SELECT count(*), id, description, type FROM grype_repo_vulnerabilities
 GROUP BY id, description, type
 ORDER BY count(*) DESC

diff --git a/docs/mergestat/querying/examples.md b/docs/mergestat/querying/examples.md
@@ -24,6 +24,6 @@ For now, here is the current state of what we are working on and some of the roa
 - Metabase (_roadmap_)
 - Apache Superset (_roadmap_)
 
-## MergeStat Grafana Example Dashbaord
+## MergeStat Grafana Example Dashboard
 
 ![MergeStat Grafana Example Dashboard](https://github.com/mergestat/mergestat/blob/main/examples/templates/grafana/screenshots/mergestat-examples.png?raw=true)
diff --git a/docs/mergestat/querying/schema/tables/git_commits.md b/docs/mergestat/querying/schema/tables/git_commits.md
@@ -34,7 +34,7 @@ COMMENT ON COLUMN git_commits.hash IS 'hash of the commit';
 COMMENT ON COLUMN git_commits.message IS 'message of the commit';
 COMMENT ON COLUMN git_commits.author_name IS 'name of the author of the the modification';
 COMMENT ON COLUMN git_commits.author_email IS 'email of the author of the modification';
-COMMENT ON COLUMN git_commits.author_when IS 'timestamp of when the modifcation was authored';
+COMMENT ON COLUMN git_commits.author_when IS 'timestamp of when the modification was authored';
 COMMENT ON COLUMN git_commits.committer_name IS 'name of the author who committed the modification';
 COMMENT ON COLUMN git_commits.committer_email IS 'email of the author who committed the modification';
 COMMENT ON COLUMN git_commits.committer_when IS 'timestamp of when the commit was made';

diff --git a/docs/mergestat/querying/schema/tables/github_pull_request_commits.md b/docs/mergestat/querying/schema/tables/github_pull_request_commits.md
@@ -39,7 +39,7 @@ COMMENT ON COLUMN github_pull_request_commits.hash IS 'hash of the commit';
 COMMENT ON COLUMN github_pull_request_commits.message IS 'message of the commit';
 COMMENT ON COLUMN github_pull_request_commits.author_name IS 'name of the author of the the modification';
 COMMENT ON COLUMN github_pull_request_commits.author_email IS 'email of the author of the modification';
-COMMENT ON COLUMN github_pull_request_commits.author_when IS 'timestamp of when the modifcation was authored';
+COMMENT ON COLUMN github_pull_request_commits.author_when IS 'timestamp of when the modification was authored';
 COMMENT ON COLUMN github_pull_request_commits.committer_name IS 'name of the author who committed the modification';
 COMMENT ON COLUMN github_pull_request_commits.committer_email IS 'email of the author who committed the modification';
 COMMENT ON COLUMN github_pull_request_commits.committer_when IS 'timestamp of when the commit was made';