docs: fix some typo (#3171)

This commit is contained in:
Nozomi Morimoto
2022-11-14 21:15:31 +09:00
committed by GitHub
parent 42e81ad0a6
commit 9ebdc51d3a
4 changed files with 6 additions and 6 deletions

View File

@@ -1,6 +1,6 @@
# Kubernetes Compliance
## NSA Complaince Report
## NSA Compliance Report
!!! warning "EXPERIMENTAL"
This feature might change without preserving backwards compatibility.

View File

@@ -149,7 +149,7 @@ Total: 20 (UNKNOWN: 3, LOW: 0, MEDIUM: 7, HIGH: 5, CRITICAL: 5)
## Scanning a Branch
Pass a `--branch` agrument with a valid branch name on the remote repository provided:
Pass a `--branch` argument with a valid branch name on the remote repository provided:
```
$ trivy repo --branch <branch-name> <repo-name>
@@ -157,7 +157,7 @@ $ trivy repo --branch <branch-name> <repo-name>
## Scanning upto a Commit
Pass a `--commit` agrument with a valid commit hash on the remote repository provided:
Pass a `--commit` argument with a valid commit hash on the remote repository provided:
```
$ trivy repo --commit <commit-hash> <repo-name>
@@ -165,7 +165,7 @@ $ trivy repo --commit <commit-hash> <repo-name>
## Scanning a Tag
Pass a `--tag` agrument with a valid tag on the remote repository provided:
Pass a `--tag` argument with a valid tag on the remote repository provided:
```
$ trivy repo --tag <tag-name> <repo-name>

View File

@@ -230,7 +230,7 @@ podAnnotations: {}
## Other Tools to use and deploy Trivy
For additional tools and ways to install and use Trivy in different envrionments such as in Docker Desktop and Kubernetes clusters, see the links in the [Ecosystem section](../ecosystem/tools.md).
For additional tools and ways to install and use Trivy in different environments such as in Docker Desktop and Kubernetes clusters, see the links in the [Ecosystem section](../ecosystem/tools.md).
[ecr]: https://gallery.ecr.aws/aquasecurity/trivy

View File

@@ -50,7 +50,7 @@ spec:
### Apply the policy to your Kubernetes cluster
Ensure that you have Kyverno already deployed and running on your cluster -- for instance throught he Kyverno Helm Chart.
Ensure that you have Kyverno already deployed and running on your cluster -- for instance through he Kyverno Helm Chart.
Next, apply the above policy:
```