From be91dc65d639d49d9b5b11ffb346994d30c6c6f8 Mon Sep 17 00:00:00 2001 From: Puerco Date: Fri, 25 Aug 2023 08:00:03 -0700 Subject: [PATCH] docs: fix some typos on main README (#1455) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Adolfo García Veytia (Puerco) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d913cb19..d97c1f3f 100644 --- a/README.md +++ b/README.md @@ -159,12 +159,12 @@ cat ./sbom.json | grype Grype supports input of [Syft](https://github.com/anchore/syft), [SPDX](https://spdx.dev/), and [CycloneDX](https://cyclonedx.org/) SBOM formats. If Syft has generated any of these file types, they should have the appropriate information to work properly with Grype. It is also possible to use SBOMs generated by other tools with varying degrees of success. Two things that make Grype matching -more successful are inclusion of CPE and Linux distribution information. If an SBOM does not include any CPE information, it +more successful are the inclusion of CPE and Linux distribution information. If an SBOM does not include any CPE information, it is possible to generate these based on package information using the `--add-cpes-if-none` flag. To specify a distribution, use the `--distro :` flag. A full example is: ``` -grype --add-cpes-if-none --distro alpine:3.10 sbom:some-apline-3.10.spdx.json +grype --add-cpes-if-none --distro alpine:3.10 sbom:some-alpine-3.10.spdx.json ``` ### Supported versions @@ -276,7 +276,7 @@ Grype lets you define custom output formats, using [Go templates](https://golang **Please note:** Templates can access information about the system they are running on, such as environment variables. You should never run untrusted templates. -There are several example templates in the [templates](https://github.com/anchore/grype/tree/main/templates) directory in the Grype source which can serve a starting point for a custom output format. For example, [csv.tmpl](https://github.com/anchore/grype/blob/main/templates/csv.tmpl) produces a vulnerability report in CSV (comma separated value) format: +There are several example templates in the [templates](https://github.com/anchore/grype/tree/main/templates) directory in the Grype source which can serve as a starting point for a custom output format. For example, [csv.tmpl](https://github.com/anchore/grype/blob/main/templates/csv.tmpl) produces a vulnerability report in CSV (comma separated value) format: ```text "Package","Version Installed","Vulnerability ID","Severity"