Update release-notes.md

docs/release-notes.md

@@ -1,4 +1,4 @@
-# Release Notes
+![image](https://github.com/user-attachments/assets/ef5b01ae-6b42-4257-beae-1fc37c10217e)# Release Notes
 This section contains CIMTool release notes and can be used for quick reference of what has changed in each version. Note that these notes are the same
 as those available on GitHub [here](https://github.com/cimug-org/CIMTool/releases), but contain more versions since this log pre-dates 
 GitHub being the version control system for CIMTool.
@@ -22,7 +22,7 @@ Introduced in this release is support for the generation of UML class diagrams f
 ![image](https://github.com/user-attachments/assets/894b180a-7080-436c-9d1c-bb9632c3e7cc)
 
 Defect [Issue #154](https://github.com/cimug-org/CIMTool/issues/154):
-The **CIMTool** RDFS2020 builder made available in the 2.0.0 release required additional development to both fix areas not in proper alignment with that generated by [CimConteXtor](https://www.cimcontextor.net/index.php/en/products/cimcontextor/cimcontextor). It should be noted that the builder currently generates RDFS2020 schema's with "flattened" CIMDatatypes (i.e. value, unit, multplier attributes note defined within the generated RDFS). The final development for generating the "unflattened" CIMDatatypes (i.e. that explicitly define value, unit, multiplier, etc.) will be in a future release.
+The **CIMTool** RDFS2020 builder made available in the 2.0.0 release required additional development to both fix areas not in proper alignment with that generated by [CimConteXtor](https://www.cimcontextor.net/index.php/en/products/cimcontextor/cimcontextor). It should be noted that the builder currently generates RDFS2020 schema's with "flattened" CIMDatatypes (i.e. value, unit, multiplier attributes note defined within the generated RDFS). The final development for generating the "unflattened" CIMDatatypes (i.e. that explicitly define value, unit, multiplier, etc.) will be in a future release.
 
 Defect [Issue #156](https://github.com/cimug-org/CIMTool/issues/156):
 A post **CIMTool** 2.1.0 release task was to extensively test and address known issues related to profiling custom extensions using the newly supported 64-bit EA 16.x .qea, .qeax, and '.feap' project file types introduced in 2.1.0. This was decided to allow for 2.1.0 to be released to end users that only needed to profile using normative CIM without extensions. The outcome of this effort allows for profiling using a single EA project file (e.g. `.qea` or `.eap`) as your schema via the use of the `baseuri` tagged value for specifying the namespaces for your extensions with the `.eap`/`.qea` project file.  The resulting behavior when profiling using these new schema formats is designed to mirror the same behavior observed when using `baseuri` with multiple `.xmi` files to model extensions.