Change KI

Author: MariaShaposhnikova

content/en/docs/releasenotes/studio-pro/10/10.12.md

@@ -56,8 +56,6 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-  * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
   * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
@@ -93,8 +91,6 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-  * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * <a id="import-platform-supported-module"></a>Importing a platform-supported Marketplace module containing a Java action fails when the project does not have managed Java dependencies or when Gradle synchronization for managed Java dependencies is disabled. In these cases there is no `vendorlib` folder in the project directory, causing the import to fail.
   * Fixed in [10.6.17](/releasenotes/studio-pro/10.6/#fix-import-platform-supported-module) and [10.12.8](#fix-import-platform-supported-module).
 * <a id="upgrade-platform-supported-module"></a>Upgrading a platform-supported Marketplace module containing a Java action fails. Or adding a platform supported module that contains Java dependencies that are already used by the project fails. In these cases the project `vendorlib` directory already contains the same *.jar* files as the new module, which will fail the import process.
@@ -139,10 +135,8 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 * We fixed an issue where an **Oops** dialog was shown when the [Data Widgets](https://marketplace.mendix.com/link/component/116540?_gl=1*jpe0m1*_gcl_au*MTg4MTk2NjAyMi4xNzIxODA1MDU2) module was updated to version 2.24.0 or above, when a data grid 2 was configured with a column using the `owner` or `changedBy` system association.
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-    * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
-  * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
+    * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.
 * There is a positioning error in the logic editors when you are dragging a large element, such as a loop, into a sequence flow, it overlaps with the existing elements.
 * Studio Pro on Mac loads user settings from the previous version of the application.
@@ -179,8 +173,6 @@ This is the [MTS](/releasenotes/studio-pro/lts-mts/#mts) version 10 release for
 
 ### Known Issues
 
-* When importing Marketplace modules with Studio Pro, their version numbers do not represent the module's version. Instead they mention the current Studio Pro version. This does not affect previously imported Marketplace modules.
-    * Fixed in [10.14.0](/releasenotes/studio-pro/10.14/#fix-marketplace-modules).
 * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](/refguide/version-control-menu/#show-changes) dialog box.
     * Workaround: For details, see [this section](/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*.
 * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.