From 9eb9e9d384953ee0e9c2312d186c79ab1ff0815c Mon Sep 17 00:00:00 2001 From: Arthit Suriyawongkul Date: Thu, 26 Sep 2024 13:00:37 +0700 Subject: [PATCH] Fix typo - "Asbtract" -> "Abstract" - Also fix inconsistent use of emphasis markup (`_,,,_` -> `*...*`) Signed-off-by: Arthit Suriyawongkul --- model/Security/Classes/VexVulnAssessmentRelationship.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/model/Security/Classes/VexVulnAssessmentRelationship.md b/model/Security/Classes/VexVulnAssessmentRelationship.md index 9e76cfe4c..49644fb24 100644 --- a/model/Security/Classes/VexVulnAssessmentRelationship.md +++ b/model/Security/Classes/VexVulnAssessmentRelationship.md @@ -4,7 +4,7 @@ SPDX-License-Identifier: Community-Spec-1.0 ## Summary -Asbtract ancestor class for all VEX relationships +Abstract ancestor class for all VEX relationships ## Description @@ -17,10 +17,10 @@ When linking elements using a VexVulnAssessmentRelationship, the following requirements must be observed: - The from: end must be a /Security/Vulnerability classed element -- The to: end must point to elements representing the VEX _products_. +- The to: end must point to elements representing the VEX *products*. To specify a different element where the vulnerability was detected, the VEX -relationship can optionally specify _subcomponents_ using the assessedElement +relationship can optionally specify *subcomponents* using the assessedElement property. VEX inherits information from the document level down to its statements. When a