From 16827a7f8ed82e712288e669765658d86e228f95 Mon Sep 17 00:00:00 2001 From: Tadashi Nemoto Date: Wed, 13 Nov 2024 09:44:14 +0900 Subject: [PATCH] Fix heading of scout/how-tos/artifact-types/ --- content/manuals/scout/how-tos/artifact-types.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/manuals/scout/how-tos/artifact-types.md b/content/manuals/scout/how-tos/artifact-types.md index 524219fc8c..e62a1452df 100644 --- a/content/manuals/scout/how-tos/artifact-types.md +++ b/content/manuals/scout/how-tos/artifact-types.md @@ -56,7 +56,7 @@ You can use prefixes with the following commands: This section contains a few examples showing how you can use prefixes to specify artifacts for `docker scout` commands. -## Analyze a local project +### Analyze a local project The `fs://` prefix lets you analyze local source code directly, without having to build it into a container image. @@ -112,7 +112,7 @@ pkg:npm/fastify@3.29.0 CRITICAL 0 ``` -## Compare a local project to an image +### Compare a local project to an image With `docker scout compare`, you can compare the analysis of source code on your local filesystem with the analysis of a container image.