TW review

Author: NicoletaComan

content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/_index.md

@@ -2,27 +2,27 @@
 title: "Teamcenter Connector 2606"
 url: /appstore/industry/teamcenter-connector/teamcenter-connector-2606/
 weight: 2
-description: "Describes the unified Teamcenter Connector 2606."
+description: "Describes Teamcenter Connector 2606, a unified Mendix Marketplace module for integrating Mendix with Teamcenter."
 ---
 
 ## Introduction
 
-Teamcenter Connector 2606 marks a shift in how Mendix integrates with Teamcenter. For the first time, we're bringing together everything you need in a single, unified Marketplace module. This release combines what were previously two separate Marketplace downloads: Teamcenter Connector and the Teamcenter Extension (which itself contained two modules: Teamcenter Toolkit and the Extension add-on) into one streamlined package that works seamlessly with Mendix 11.12 and higher.
+Teamcenter Connector 2606 is a unified Mendix Marketplace module that brings together everything you need to integrate Mendix with Teamcenter. It combines what were previously two separate Marketplace modules, Teamcenter Connector and Teamcenter Extension, with Teamcenter Extension containing two modules, Teamcenter Toolkit and the Extension add-on. Teamcenter Connector 2606 is a streamlined package that works seamlessly with Mendix 11.12 and above.
 
-Additionally, Teamcenter Extension has been re-built using the Web Extensibility Framework and is now available as a Teamcenter service document. You can think of a Teamcenter service document as a container that can be created on a per module basis which stores everything related to your Teamcenter integrations within a specific module. 
+Teamcenter Extension has been rebuilt using the Web Extensibility Framework and is available as a Teamcenter service document. A Teamcenter service document is a container that you can create on a per-module basis. It stores everything related to your Teamcenter integrations within a specific module.
 
-In previous versions, the Extension stored the Teamcenter integrations and configurations on disk (resources folder), separate from your Mendix app. This made version control tricky and team collaboration more complex. With the Teamcenter service document approach, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
+In previous versions, the Teamcenter Extension stored integrations and configurations on disk, in the resources folder, separate from your Mendix app. This made version control difficult and team collaboration more complex. With a Teamcenter service document, everything is stored inside the Mendix model, just like microflows, pages, and domain models. This means:
 
 * Your integrations travel with your module when you export it or commit it to version control.
 * You can have different Teamcenter service documents for different purposes within the same app.
-* You can have different Teamcenter service documents for different Teamcenter instances, for example for test and production. 
-  
-## Architecture Overview
+* You can have different Teamcenter service documents for different Teamcenter instances, such as for test and production.
 
-Here's how all the pieces fit together:
+### Architecture Overview
+
+The following diagram shows how all the pieces fit together:
 
 ```
-Studio Pro (Mendix 11.12+)
+Studio Pro 11.12+
 │
 ├── Teamcenter service document  ←  stores integrations + connection settings
 │     └── Extension UI (TypeScript / Web Extensibility Framework)
@@ -48,23 +48,25 @@ Studio Pro (Mendix 11.12+)
         (self-hosted v2506+ / Teamcenter X v2506+)
 ```
 
-## How it works in practice
+## How It Works
+
+These steps describe how Teamcenter Connector 2606 works in a nutshell: 
 
-1. You start by creating a Teamcenter service document, where you configure your Teamcener connection and create integrations.
+1. You start by creating a Teamcenter service document, where you configure your Teamcenter connection and create integrations.
 2. The Teamcenter service document generates domain model entities and microflows specific to your integration needs, placing them directly in your module.
-3. The generated microflows make use of predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer
+3. The generated microflows use predefined Teamcenter connector microflows for the integration with Teamcenter, using the TcConnector Java Actions to call Teamcenter's SOA layer.
 
 ## Prerequisites and Compatibility
 
-Before you start working with Teamcenter Connector 2606, make sure your environment meets these requirements:
+Before working with Teamcenter Connector 2606, make sure your environment meets these requirements:
 
-| Requirement | Minimum version |
-|---|---|
-| Mendix Studio Pro | 11.12.1 |
+| Requirement | Supported versions |
+| --- | --- |
+| Mendix Studio Pro | 11.12.1 and above |
 | Teamcenter (self-hosted) | 2606, 2512, 2506 |
 | Teamcenter X | 2606, 2512, 2506 |
 
-### Required Marketplace modules
+### Required Marketplace Modules
 
 * Community Commons
 * Encryption