From 3bcd8750da8085bafb837ab64b0aa7b79ba1369e Mon Sep 17 00:00:00 2001
From: Jan Kowalleck <jan.kowalleck@gmail.com>
Date: Tue, 16 Jan 2024 14:22:04 +0100
Subject: [PATCH] docs

Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
---
 schema/bom-1.6.xsd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/schema/bom-1.6.xsd b/schema/bom-1.6.xsd
index 19f6a6f8..4f510f51 100644
--- a/schema/bom-1.6.xsd
+++ b/schema/bom-1.6.xsd
@@ -512,7 +512,7 @@ limitations under the License.
                         <xs:documentation>The component version range that may be provided to fulfill this capability.
                             MAY only occur if attribute `isExtraneous` is set to `true`.</xs:documentation>
                         <!-- Attention:
-                        Since XSD 1.1 `asserts` are mostly not implemented, there is currently no rule in this XSD,
+                        Since XSD 1.1 `asserts` are mostly not implemented, there is currently no rule in this XSD
                         that is taking cate of the plausibility between `version`/`versionRange` and `isExtraneous`=='true'
                         -->
                     </xs:annotation>
@@ -697,7 +697,7 @@ limitations under the License.
         This would be formal, if the support for XSD1.1's `assert` was properly implemented in validators and tools digesting XML.
         <xs:assert id="versionRange_requires_isExtraneous_eq_true"
                    test="if (versionRange) then (@isExtraneous eq 'true') else true()">
-            Child `versionRange` MAY only be present, if attribute `isExtraneous` is 'true'.
+            Child `versionRange` MAY only be present, if attribute `isExtraneous`=='true'.
         </xs:assert>
         -->
     </xs:complexType>