diff --git a/Readme.md b/Readme.md
index 86de34c2cae7f5aefdbbcf0e9a88655e4aa461e0..3ad1fa6ad355c3f134aac9e86b2251023f2405c5 100644
--- a/Readme.md
+++ b/Readme.md
@@ -6,7 +6,7 @@ More info at [TDL website](https://tdl.etsi.org)
 
 ## Installing the plug-ins
 
-The TDL tools are available as a set of Eclipse plug-ins. You need to first be able to run Eclipse. The [Eclipse Modeling Tools (2021-06)](https://www.eclipse.org/downloads/packages/release/2021-06/r/eclipse-modeling-tools) distribution contains most of the necessary prerequisites for the TDL tools. Newer versions should be compatible but have not been extensively tested yet.
+The TDL tools are available as a set of Eclipse plug-ins. You need to first be able to run Eclipse. The [Eclipse Modeling Tools (2022-12)](https://www.eclipse.org/downloads/packages/release/2022-12/r/eclipse-modeling-tools) distribution contains most of the necessary prerequisites for the TDL tools. Newer versions should be compatible but have not been extensively tested yet.
 
 Once Eclipse is up and running, the easiest way to install the TOP tools is from the Eclipse Marketplace - simply search for TDL in the Eclipse Marketplace client within Eclipse, or go to the [TOP Marketplace Listing](https://marketplace.eclipse.org/content/top-tdl-open-source-project) and drag the install button into the Eclipse window.
 
@@ -59,21 +59,23 @@ From end-user's perspective this translates to two file extensions - `.tdltx` fo
  * Download and install Eclipse Modeling Tools package
  * Install following additional components from Eclipse Marketplace
      * Sirius (v7)
-     * Eclipse Xtext (v2.26 or newer)
+     * Eclipse Xtext (v2.29 or newer)
      * Epsilon (v2.x)
      * Eclipse OCL (v6.x)
  * Check out the repository
  * Import the plug-ins in the Eclipse workspace
+     * Import -> Existing Projects into Workspace
  * Generate the meta-model code
      * Open the `tdl.genmodel` 
-     * Make sure that the "Realisation of OCL embedded within Ecore models" is set to "Delegate for interpretation at run-time" in the Eclipse preferences
+     * Make sure that the "Realisation of OCL embedded within Ecore models" is set to "Delegate for interpretation at run-time" in the Eclipse preferences (setting it on project level does not seem sufficient currently)
      * Right click on the top-node and generate model code 
+     * Repeat the above for the `structured.genmodel` and the `configurations.genmodel`
  * Generate textual editor code
      * Open the `GenerateTDLan2.mwe`
      * Right click and select Run As -> MWE2 Workflow
      * Additionally (or alternatively) repeat the same steps for the `GenerateTPLan2.mwe` (for editing structured test objectives)
      * Additionally (or alternatively) repeat the same steps for the `GenerateTDLtx.mwe` (for brace-based TDL TX representation)
-     * Additionally (or alternatively) repeat the same steps for the `GenerateTDLtxi.mwe` (for indentation-based TDL TX representation)
+     * Additionally (or alternatively) repeat the same steps for the `GenerateTDLtxi.mwe` (for indentation-based TDL TX representation, requires that the `GenerateTDLtx.mwe` is executed first)
      * Additionally (or alternatively) repeat the same steps for the `GenerateData.mwe` (for the graphical viewer)
 
 ## Converters
@@ -82,19 +84,12 @@ The converters component can be optionally installed with the TDL core and edito
 
 ### Implementation of the OpenAPI import into TDL
 
-The generation of data types and other elements based on OpenAPI yaml specifications is based on the [KaiZen OpenAPI Parser](https://github.com/RepreZen/KaiZen-OpenApi-Parser). The corresponding [Eclipse plug-in](https://marketplace.eclipse.org/content/kaizen-openapi-editor) needs to be installed before installing the importer. While the transformation components can be installed individually, the user-interface currently depends on all the transformation plug-ins.
+The generation of data types and other elements based on OpenAPI yaml specifications is based on the [OpenAPI Generator](https://openapi-generator.tech). Previous implementation based on the [KaiZen OpenAPI Parser](https://github.com/RepreZen/KaiZen-OpenApi-Parser) (requiring that the corresponding [Eclipse plug-in](https://marketplace.eclipse.org/content/kaizen-openapi-editor) needs to be installed before installing the importer) is now deprecated and will be removed soon. While the transformation components can be installed individually, the user-interface currently depends on all the transformation plug-ins.
 
 The implementation currently supports: 
  * Importing of data definitions under `components/schemas`.
  * Data mappings to the base OpenAPI definition for traceability.
- * Annotations with warnings regarding conventions.
-
-Part of the implementation was developed as a lab project with contributions from:
- * Lennart Thiesen
- * Marlin Preibisch
- * Niklas Mertsch
- * René Lars Wetzelt
- * Vincent Florens Hasse
+ * Data mappings to the target (Java) data implementaions derived from the OpenAPI definitions for executability.
 
 ### Implementation of the ASN.1 import into TDL
 The generation of data types based on ASN.1 specifications is based on the [BeanIt ASN1Bean](https://github.com/beanit/asn1bean) (formerly known as jASN).