From ac5703265af0c09da22dd8eba7b1271472a553f4 Mon Sep 17 00:00:00 2001 From: Nicolas Nobelis Date: Fri, 12 Apr 2024 11:21:26 +0200 Subject: [PATCH] fix(docs): Add the correct `snippet_choices` element in the documentation Signed-off-by: Nicolas Nobelis --- website/docs/configuration/snippet-choice.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/configuration/snippet-choice.md b/website/docs/configuration/snippet-choice.md index b307a0ef8e420..f7073f9252c9a 100644 --- a/website/docs/configuration/snippet-choice.md +++ b/website/docs/configuration/snippet-choice.md @@ -74,7 +74,7 @@ Now an operator decided that the snippet `pkg:github/RS2007/dotfiles@0384a21038f To do so, the user defines in the repository's `.ort.yml` the following **snippet choice**: ```yaml -package_snippet_choices: +snippet_choices: - provenance: url: "https://github.com/vdurmont/semver4j.git" choices: @@ -133,7 +133,7 @@ How to deal with a source location that has *only* false positives snippets? The solution is to use the `NO_RELEVANT_FINDING` reason in the `.ort.yml` file: ```yaml -package_snippet_choices: +snippet_choices: - provenance: url: "https://github.com/vdurmont/semver4j.git" choices: