From 57a4f20721fa495bcb47b70f9703a2b10307db66 Mon Sep 17 00:00:00 2001 From: "Alexios Zavras (zvr)" Date: Tue, 12 Nov 2024 10:45:54 +0100 Subject: [PATCH] Fixes typos found by OMG Signed-off-by: Alexios Zavras (zvr) --- model/Build/Properties/buildType.md | 2 +- model/Extension/Classes/Extension.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/model/Build/Properties/buildType.md b/model/Build/Properties/buildType.md index 24c796b0e..acaf96bdf 100644 --- a/model/Build/Properties/buildType.md +++ b/model/Build/Properties/buildType.md @@ -9,7 +9,7 @@ infrastructure that the build was invoked on. ## Description -A buildType is a IRI expressing the toolchain, platform, or infrastructure that +A buildType is an IRI expressing the toolchain, platform, or infrastructure that the build was invoked on. The buildType is used to interpret the meaning of other build parameters by diff --git a/model/Extension/Classes/Extension.md b/model/Extension/Classes/Extension.md index 1f9122d65..fa1fc546f 100644 --- a/model/Extension/Classes/Extension.md +++ b/model/Extension/Classes/Extension.md @@ -18,7 +18,7 @@ This approach serves multiple purposes: 2. Support extension of SPDX by adopting individuals or communities with Element characterization details uniquely specialized to their particular context. Enables adopting individuals or communities to utilize SPDX expressive capabilities along with expressing more arcane Element characterization details specific to them and not appropriate for standardization across SPDX. -3. Support structured capture of expressive solutions for gaps in SPDX coverage from real-world use. Enables adopting individuals or communities to express Element characterization details they require that are not currently defined in SPDX but likely should be. Enables a practical pipeline that +3. Support structured capture of expressive solutions for gaps in SPDX coverage from real-world use. Enables adopting individuals or communities to express Element characterization details they require that are not currently defined in SPDX but likely should be. Enables a practical pipeline that: - identifies gaps in SPDX that should be filled, - expresses solutions to those gaps in a way that allows the identifying adopters to use the extended solutions with SPDX and does not conflict with current SPDX,