Update release-notes.md

cimug-org · Oct 4, 2024 · 3fdc6b1 · 3fdc6b1
1 parent a9c19b2
commit 3fdc6b1
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/release-notes.md b/docs/release-notes.md
@@ -28,7 +28,7 @@ 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.
 
 Enhancement [Issue #155](https://github.com/cimug-org/CIMTool/issues/155):
-An new radio button has been added to the namespace list on the "Import Schema" dialog. The option allows selection of the existing namespace schema to be selected when re-importing a new version of the same named schema.  When selected the namespace field auto-populate with the existing namespace. This solves a usability issue for end users who are working against base CIM with custom extensions and who need iteratively to re-import schema changes as their model evolves. It eliminates end users exiting the dialog in order to copy the namespace in the preferences screen to be able to paste a custom namespace into the field.
+A new radio button has been added to the namespace list on the "Import Schema" dialog. The option allows selection of the existing namespace schema to be selected when re-importing a new version of the same named schema.  When selected the namespace field auto-populate with the existing namespace. This solves a usability issue for end users who are working against base CIM with custom extensions and who need iteratively to re-import schema changes as their model evolves. It eliminates end users exiting the dialog in order to copy the namespace in the preferences screen to be able to paste a custom namespace into the field.
 
 ![image](https://github.com/user-attachments/assets/7bbaae28-17c7-4077-8113-2422ca29a1d0)