From d838f4efb32021e9424a2a8915d74b802653bf42 Mon Sep 17 00:00:00 2001 From: Steve Springett Date: Wed, 6 Feb 2019 23:11:04 -0600 Subject: [PATCH] #12 spelling/grammar in doc --- schema/bom-1.1-DRAFT-1.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/schema/bom-1.1-DRAFT-1.xsd b/schema/bom-1.1-DRAFT-1.xsd index f619d83e..88247682 100644 --- a/schema/bom-1.1-DRAFT-1.xsd +++ b/schema/bom-1.1-DRAFT-1.xsd @@ -339,7 +339,7 @@ - External references provide a way to document systems, sites, and inforamtion that may be relevant but which + External references provide a way to document systems, sites, and information that may be relevant but which are not included with the BOM. @@ -447,7 +447,7 @@ Component pedigree is a way to document complex supply chain scenarios where components are created, distributed, modified, redistributed, combined with other components, etc. Pedigree supports viewing this complex chain from the beginning, the end, or anywhere in the middle. It also provides a way to - document variants where the exact relation may not be unknown. + document variants where the exact relation may not be known. @@ -503,7 +503,7 @@ The version allows component publishers/authors to make changes to existing BOMs to update various aspects of the document such as description or licenses. When a system - is presented with multiiple BOMs for the same component, the system should use the most recent + is presented with multiple BOMs for the same component, the system should use the most recent version of the BOM. The default version is '1' and should be incremented for each version of the BOM that is published. Each version of a component should have a unique BOM and if no changes are made to the BOMs, then each BOM will have a version of '1'.