Updated user facing delivery items

- included fix of a nit around key value semantics in json

Signed-off-by: Stefan Hagen <stefan@hagen.link>

csaf_2.1/prose/share/csaf-v2.1-draft.html

@@ -12115,7 +12115,7 @@ <h3 id="9118-conformance-clause-18-csaf-20-to-csaf-21-converter-">
       </li>
       <li>
         <p>
-          <code>/vulnerabilities[]/disclosure_date</code>: If a <code>release_date</code> was given, the CSAF 2.0 to CSAF 2.1 converter MUST convert the key as <code>disclosure_date</code>.
+          <code>/vulnerabilities[]/disclosure_date</code>: If a <code>release_date</code> was given, the CSAF 2.0 to CSAF 2.1 converter MUST convert its value as value into the <code>disclosure_date</code> element.
         </p>
       </li>
       <li>

csaf_2.1/prose/share/csaf-v2.1-draft.md

@@ -9737,7 +9737,7 @@ Secondly, the program fulfills the following for all items of:
 
   The tool SHOULD implement an option to use the latest available CWE version at the time of the conversion that still matches.
 
-* `/vulnerabilities[]/disclosure_date`: If a `release_date` was given, the CSAF 2.0 to CSAF 2.1 converter MUST convert the key as `disclosure_date`.
+* `/vulnerabilities[]/disclosure_date`: If a `release_date` was given, the CSAF 2.0 to CSAF 2.1 converter MUST convert its value as value into the `disclosure_date` element.
 * `/vulnerabilities[]/metrics/ssvc_v1`: If a SSVC vector or decision points of an SSVC vector are given in an item of `notes` of the current
   vulnerability using the `title` `SSVC` and the `category` `other`, the CSAF 2.0 to CSAF 2.1 converter MUST convert that data into the `ssvc_v1`
   object within the current vulnerability.