From 221cad8c96ba431f9bb8738c91163a57e1b5f802 Mon Sep 17 00:00:00 2001 From: Sebastian Schuberth Date: Wed, 13 Dec 2023 10:58:21 +0100 Subject: [PATCH] docs: Clarify that repository license choices also apply to projects Also slightly improve the sentence's wording in general. Signed-off-by: Sebastian Schuberth --- website/docs/configuration/ort-yml.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/configuration/ort-yml.md b/website/docs/configuration/ort-yml.md index 00a4a2f5ae7b0..3e49820f1ccc7 100644 --- a/website/docs/configuration/ort-yml.md +++ b/website/docs/configuration/ort-yml.md @@ -414,9 +414,9 @@ license_choices: To globally select a license from an SPDX expression, that offers a choice, an SPDX expression for a `given` and a `choice` must be provided. The `choice` is applied to the whole `given` SPDX expression. With a repository license -choice, the license choice is applied to each package that offers this license as a choice. Not allowing `given` to be -null helps only applying the choice to a wanted `given` as opposed to all licenses with that choice, which could lead to -unwanted choices. The license choices for a project can be overwritten by applying a +choice, the license choice is applied to each project or package that offers this specific license choice. Not allowing +`given` to be null helps only applying the choice to a wanted `given` as opposed to all licenses with that choice, which +could lead to unwanted choices. The license choices for a project can be overwritten by applying a [license choice to a package](#license-choice-by-package). ```yaml