Last batch of changes

NicoletaComan · NicoletaComan · commit 8ed6f6d77395 · 2025-09-23T10:23:02.000+02:00
diff --git a/content/en/docs/catalog/consume/_index.md b/content/en/docs/catalog/consume/_index.md
@@ -1,5 +1,5 @@
 ---
-title: "Consume Services"
+title: "Consuming Services"
 url: /catalog/consume/
 weight: 20
 aliases:
diff --git a/content/en/docs/catalog/consume/consume.md b/content/en/docs/catalog/consume/consume.md
@@ -1,5 +1,5 @@
 ---
-title: "Consume Registered Assets"
+title: "Consuming Registered Assets"
 url: /catalog/consume/consume-registered-assets/
 weight: 20
 description: "Describes how to use shared services and datasets through the Catalog."
diff --git a/content/en/docs/catalog/manage/_index.md b/content/en/docs/catalog/manage/_index.md
@@ -1,5 +1,5 @@
 ---
-title: "Manage Services"
+title: "Managing Services"
 url: /catalog/manage/
 weight: 30
 aliases:
diff --git a/content/en/docs/catalog/manage/curate.md b/content/en/docs/catalog/manage/curate.md
@@ -1,5 +1,5 @@
 ---
-title: "Curate Registered Assets"
+title: "Curating Registered Assets"
 url: /catalog/manage/curate/
 description: "Describes how to curate and enhance data assets in Catalog, and make them easier to find and understand."
 aliases:
@@ -25,7 +25,7 @@ Information that is added or changed during curation is stored in the Catalog fo
 
 ## Curate List {#curatelist}
 
-Owners and curators of registered assets can click **Curate** from the Catalog home page to see the curation list screen. This page provides an overview of all the registered assets you can curate as an owner under the **My Assets** tab. Curators will also see the **Company Assets** tab that lists all the registered assets:
+Owners and curators of registered assets can click **Curate** from the Catalog home page to see the curation list screen. This page provides an overview of all the registered assets you can curate as an owner under the **My Assets** tab. Curators will also see the **Company Assets** tab that lists all the registered assets.
 
 {{< figure src="/attachments/catalog/curate/curate-list.png" alt="curate list" class="no-border" >}}
 
@@ -63,15 +63,7 @@ When a dataset is selected, click **Edit the dataset** to do the following:
 
 The curate functions that are available for a selected service are to change **Service**, **Application**, and **Authentication** details This section describes the application details that can be changed: changing owners or changing the application icon.
 
-You can curate application details from the **Application** tab as follows:
-
-1. Click **Edit** > **Application** tab.
-
-    {{< figure src="/attachments/catalog/search/curation-option.png" alt="app edit screen" >}}
-
-2. The **Application** tab is displayed:
-
-    {{< figure src="/attachments/catalog/curate/edit-application.png" alt="app edit screen" >}}
+You can curate application details from the **Application** tab. To do that, click **Edit**, then go to the **Application** tab.
 
 ### Changing Owners of an App {#changing-owners}
 
@@ -130,7 +122,7 @@ When you want to upload a custom icon or image, the following apply:
 
 To **Upload a different icon** for the app, follow these steps:
 
-1. In the **Application** tab of the selected service, click **Upload a different icon** to display the **Upload Application Icon** pop up:
+1. In the **Application** tab of the selected service, click **Upload a different icon** to display the **Upload Application Icon** pop-up window.
 
     {{< figure src="/attachments/catalog/curate/icon-upload-dialog.png" alt="upload icon"   width="300"  class="no-border" >}}
 
@@ -143,7 +135,7 @@ To **Upload a different icon** for the app, follow these steps:
 
     {{< figure src="/attachments/catalog/curate/icon-preview.png" alt="upload icon"   width="300"  class="no-border" >}}
 
-5. The **Application** tab will now show the selected icon:
+5. The **Application** tab now displays the selected icon.
 
     {{< figure src="/attachments/catalog/curate/asset-metadata-new-icon.png" alt="upload icon" class="no-border" >}}
 
@@ -165,7 +157,7 @@ If a description was included in the contract, it will be displayed in the Servi
 
 To edit the asset metadata, follow these steps:
 
-1. On the **Curate** page, click **Edit** to display the Edit Service
+1. On the **Curate** page, click **Edit** to display the Edit Service screen.
     {{< figure src="/attachments/catalog/curate/service-metadata-box.png" alt="service metadata" class="no-border" >}}
 
 2. The description from the service metadata is displayed in the **Description provided by the contract**. This cannot be changed, as it is part of the service definition. You can provide an alternative description in the **Description** box.
@@ -178,7 +170,7 @@ To edit the asset metadata, follow these steps:
 Add tags to categorize a registered service and provide additional means for finding the service. Tags that are specified for a service also apply to the datasets and attributes that are exposed in the service. Specify tags for the selected service by following these steps:
 
 1. On the Service details page of a selected service, click **Edit** to display the Edit Service screen.
-2. To add tags, click the empty **Tags** input area:
+2. To add tags, click the empty **Tags** input area.
 
     {{< figure src="/attachments/catalog/curate/service-metadata-tags.png" alt="tags" class="no-border" >}}
 
diff --git a/content/en/docs/catalog/manage/search.md b/content/en/docs/catalog/manage/search.md
@@ -1,5 +1,5 @@
 ---
-title: "Search in the Catalog"
+title: "Searching in the Catalog"
 url: /catalog/manage/search/
 description: "Describes how to find services and datasets in the Catalog."
 aliases:
@@ -70,13 +70,13 @@ The **Search** screen is divided into the [search](#search-pane) pane on the lef
 
 ### Search Pane {#search-pane}
 
-The collapsible **Search** pane is used to search for registered assets in the Catalog:
+The collapsible **Search** pane is used to search for registered assets in the Catalog.
 
 {{< figure src="/attachments/catalog/search/search-pane.png" alt="search pane"   width="300"  class="no-border" >}}
 
 #### Specifying the Search
 
-Enter a search string in the **Search** area with a minimum of 3 alphanumeric characters. Searching for the wildcard `*` or the empty string `''` will return all registered items.
+Enter a search string in the **Search** area with a minimum of 3 alphanumeric characters. Searching for the wildcard `*` or the empty string `''` returns all registered items.
 
 #### Filters {#filter}
 
@@ -217,11 +217,11 @@ The environment type indicates the quality and the status of the data that the e
 
 ### Curation Option {#curation-option}
 
-The **Curation Option** is displayed in the asset detail screen if you are the owner of the selected asset or a curator. In **Edit**, you can edit the information that is displayed in the Catalog for an asset:
+The **Curation Option** is displayed in the asset detail screen if you are the owner of the selected asset or a curator. In **Edit**, you can edit the information that is displayed in the Catalog for an asset.
 
 {{< figure src="/attachments/catalog/search/curation-option.png" alt="curation option"   width="300"  >}}
 
-* For the selected service, you can edit [Application Details](/catalog/manage/curate/#curate-application), [Service Details](/catalog/manage/curate/#service-details), and Authentication
+For the selected service, you can edit the [Application Details](/catalog/manage/curate/#curate-application), the [Service Details](/catalog/manage/curate/#service-details), and the Authentication.
 
 For further details, see the [Discoverable and Validated](/catalog/manage/curate/#discoverability) section of *Curate Registered Assets*.
 
@@ -231,7 +231,7 @@ The service URI is the location of the service contract of the service, also kno
 
 ### Download the Contract of a Service {#download-contract}
 
-For a selected service, you can click **Download** to download the service contract that is located at the service endpoint. A ZIP file that includes the all the files that make up the full contract is generated and downloaded.
+For a selected service, you can click **Download Contract** to download the service contract that is located at the service endpoint. A ZIP file that includes the all the files that make up the full contract is generated and downloaded.
 
 The resulting ZIP file is named `DataHub_<service_name>_<service_version>_<technology>.zip` where the string `<technology>` identifies the service protocol.
 
diff --git a/content/en/docs/catalog/register/_index.md b/content/en/docs/catalog/register/_index.md
@@ -1,5 +1,5 @@
 ---
-title: "Register Services"
+title: "Registering Services"
 url: /catalog/register/
 weight: 10
 aliases:
diff --git a/content/en/docs/catalog/register/automate-registration.md b/content/en/docs/catalog/register/automate-registration.md
@@ -1,5 +1,5 @@
 ---
-title: "Automate Catalog Registration"
+title: "Automating Catalog Registration"
 linktitle: "Automate Catalog Registration"
 url: /catalog/register/automate-registration/
 description: "Learn how to automate Catalog registration in a pipeline deploying to a (virtual) Mendix on Kubernetes deployment."
diff --git a/content/en/docs/catalog/register/register-data.md b/content/en/docs/catalog/register/register-data.md
@@ -1,5 +1,5 @@
 ---
-title: "Register Resources in the Catalog"
+title: "Registering Resources in the Catalog"
 linktitle: "Register Resources"
 url: /catalog/register/register-data/
 description: "Describes how to register resources in the Catalog: through Mendix Cloud or in the UI form."
diff --git a/content/en/docs/marketplace/create-content/create-connectors/_index.md b/content/en/docs/marketplace/create-content/create-connectors/_index.md
@@ -84,9 +84,6 @@ To start setting up your app, open Studio Pro and do the following:
 
 1. Create a [new app](/refguide/new-app/) for your connector.
 2. Create a module to contain your connector. To do this, right-click anywhere in the **App Explorer** outside of existing modules, and choose **Add Module**.
-
-    {{< figure src="/attachments/appstore/create-content/create-connectors/add-module.png" class="no-border" >}}
-
 3. Give your module a name fitting for the type of connector you are building.
 4. Create the basic folder structure at root level. 
 
diff --git a/content/en/docs/marketplace/create-content/create-connectors/connector-guide-best-practices.md b/content/en/docs/marketplace/create-content/create-connectors/connector-guide-best-practices.md
@@ -122,7 +122,7 @@ While Java is likely going to be a primary choice for building your connector mo
 
 To ensure that end-users can reuse your Mendix build logic as easily as possible, you need to make microflows available as microflow or workflow activities. For details, see the [Triggering a Workflow via a Microflow](/refguide/perform-workflow-basic-functions/#trigger-microflow) section of *Performing Workflow Basic Functions*).
 
-Ensure that a microflow is visible in the **Toolbox**, in the [Expose as microflow action](/refguide/java-actions/#expose-microflow-action) section of the microflow properties. You can do this by right-clicking in your microflow working area. Additionally, you can specify a caption for the action, a category for the **Toolbox**, and an icon. These will be used in the **Toolbox**, and also in the microflows, so they need to be easy to read for the end-user:
+Ensure that a microflow is visible in the **Toolbox**, in the [Expose as microflow action](/refguide/java-actions/#expose-microflow-action) section of the microflow properties. You can do this by right-clicking in your microflow working area. Additionally, you can specify a caption for the action, a category for the **Toolbox**, and an icon. These will be used in the **Toolbox**, and also in the microflows, so they need to be easy to read for the end-user.
 
 {{< figure src="/attachments/appstore/create-content/create-connectors/connector-guide-best-practices/microflow-action.png" class="no-border" >}}
 
diff --git a/content/en/docs/marketplace/create-content/create-solutions/implement-solutions/_index.md b/content/en/docs/marketplace/create-content/create-solutions/implement-solutions/_index.md
@@ -13,10 +13,6 @@ This page provides information and guidance on how to set up and upgrade a solut
 
 ## Solution Lifecycle
 
-This image presents the typical solution lifecycle:
-
-{{< figure src="/attachments/appstore/create-content/implement-solutions/solution-lifecycle.png" alt="Adaptable Solution Lifecycle" class="no-border" >}}
-
 There are three main stages a solution goes through during its lifecycle:
 
 * **Build** – This stage is performed by an ISV, who creates a solution and releases new versions with improvements. Mendix recommends releasing a new solution version along with a [Studio Pro LTS](/releasenotes/studio-pro/lts-mts/#lts) release.
diff --git a/content/en/docs/marketplace/create-content/create-solutions/implement-solutions/sol-set-up.md b/content/en/docs/marketplace/create-content/create-solutions/implement-solutions/sol-set-up.md
@@ -23,7 +23,7 @@ To set up a Mendix solution, make sure the following prerequisites are met:
 
 To set up a solution, follow these steps:
 
-1. Open Studio Pro and [import](/refguide/import-and-export/) the *.mxsolution* package:
+1. Open Studio Pro and [import](/refguide/import-and-export/) the *.mxsolution* package.
 
     {{< figure src="/attachments/appstore/create-content/implement-solutions/solution-import.png" alt="Import Solution" class="no-border" >}}
 
diff --git a/content/en/docs/marketplace/create-content/create-solutions/sol-adapt/_index.md b/content/en/docs/marketplace/create-content/create-solutions/sol-adapt/_index.md
@@ -15,7 +15,8 @@ While [Mendix best practices for development](/refguide/dev-best-practices/) app
 
 ## What Is an Adaptable Solution?
 
-In an adaptable solution, up to 20% of the end solution can be adapted through customizations, extensions, integrations, or new customer-specific modules. Instead of being tied to a prescriptive software-as-a-service (SaaS) solution that only allows for configuration at runtime, adaptable solutions allow for design-time adaptation through model-level changes to cater to the needs of your specific implementation.
+In an adaptable solution, up to 20% of the end solution can be adapted through customizations, extensions, integrations, or new customer-specific modules. The 80% that is left is the core solution, which is shared across all customers without any changes.    
+Instead of being tied to a prescriptive software-as-a-service (SaaS) solution that only allows for configuration at runtime, adaptable solutions allow for design-time adaptation through model-level changes to cater to the needs of your specific implementation. They can be sold to multiple customers, and can be upgraded to new versions.
 
 {{< figure src="/attachments/appstore/create-content/create-solutions/sol-adapt/sol-architecting/adaptable-solution-architecture.png" alt="Adaptable Solution architecture" class="no-border" >}}
 
diff --git a/content/en/docs/marketplace/create-content/create-solutions/sol-adapt/sol-architecting.md b/content/en/docs/marketplace/create-content/create-solutions/sol-adapt/sol-architecting.md
@@ -66,8 +66,6 @@ For design-time adaptations, Mendix recommends referencing [How to Set Up a Solu
 
 The customer model instances run with [IP protection](/appstore/creating-content/sol-ip-protection/) enabled. This means that parts of the original solution model can be hidden. Once the solution is published with the protected solution models, the consumer of the solution model can no longer unhide the implementation.
 
-{{< figure src="/attachments/appstore/create-content/create-solutions/sol-adapt/solution-deployment.png" alt="Development and deployment model for Solution Implementation"  width="50%" class="no-border" >}}
-
 ### Customers Without Adaptation
 
 Not all customers might require model adaptation. This means they can run on an unmodified version of the original solution model. In this case, Mendix recommends distributing and deploying a deployment package (MDA), which also prevents inspection in the Mendix model and ensures seamless upgrades. This can be combined with [flexible environments](/developerportal/deploy/mendix-cloud-deploy/#flexible-environments) and/or a multi-tenancy setup.
diff --git a/content/en/docs/marketplace/create-content/upload-content/_index.md b/content/en/docs/marketplace/create-content/upload-content/_index.md
@@ -166,7 +166,7 @@ On the **Enable** page, in the **Documentation** section, you can enter details
 
 The editor comes with a set of basic formatting tools, such as bold, bullet lists, and URL links.
 
-<a id="screenshot"></a>2. Click **Upload Screenshot** to upload images of the component from your computer. This is required for submitting a new component, and is especially important for configuration steps:
+<a id="screenshot"></a>2. Click **Upload Screenshot** to upload images of the component from your computer. This is required for submitting a new component, and is especially important for configuration steps.
 
 {{< figure src="/attachments/appstore/submit-content/enable.png"  >}}
 
diff --git a/content/en/docs/marketplace/use-content/_index.md b/content/en/docs/marketplace/use-content/_index.md
@@ -49,7 +49,7 @@ To download content in Studio Pro [9.19](/releasenotes/studio-pro/9.19/) and abo
     * Filter via the **Categories** and **Subcategories** drop-down menus, which correspond to the [Marketplace content types](/appstore/overview/).
     * Filter for **All Content**, **My Company Content**, or **Platform-Supported Content**.
 
-5. Select a component from the pane to see its details:
+5. Select a component from the pane to see its details.
 
     {{< figure src="/attachments/appstore/use-content/component-details.png" alt="Details of Blank App example component" class="no-border" >}}
 
@@ -78,7 +78,7 @@ If you download a module, the **Import Module** dialog box opens, where you shou
 
    * **Add as a new module** (default option when the module is downloaded to your app for the first time ) – If you select this option, new entities and attributes are created in your app.
 
-   * **Replace existing module** (default option when the module already exists in your app) – If you select this option, you need to specify which **Module to replace**
+   * **Replace existing module** (default option when the module already exists in your app) – If you select this option, you need to specify which **Module to replace**.
 
      {{% alert color="warning" %}}If you have made any changes to the existing module, selecting the **Replace existing module** option replaces all the changes that you made. For example, your renamed entities, attributes, and associations, as well as their respective tables and columns represented in the database will all be replaced. If you have changed data types, your user data can be influenced as well. User data will not be changed, though, if you have not changed entities, attributes, or associations. For more information, see [Attribute Type Migration](/refguide/attributes-type-migration/).{{% /alert %}}
 
@@ -99,7 +99,7 @@ If you download an [extension](/appstore/modules/#introduction), a warning dialo
 Click **OK** in the confirmation pop-up window. Your extension is now installed and ready to use.    
 Depending on the extension that you have installed, the functionality appears in a certain location of your app. Read the extension-specific documentation to get more information on how to use it.
 
-If you do not want to trust the extension and would prefer to remove the extension altogether, you can remove the add-on module that was added.
+If you do not want to trust the extension and would prefer to remove it altogether, you can remove the add-on module.
 
 {{< figure src="/attachments/appstore/use-content/trust-extension.png" alt="trust extension" >}}
 
@@ -145,12 +145,8 @@ To import content downloaded from the online Mendix Marketplace into Studio Pro,
 2. Search in the online Marketplace for the component you want to download, and open the [component details page](/appstore/component-details/).
 3. Access **Usage**, then **Version** to see the required Studio Pro version for the component. Do not download a component that requires a higher version than the one you are using.
 4. Go to the **Releases** tab and **Download** the desired version. Mendix recommends using the latest version of the component if possible.
-5. In the **App Explorer**, right-click the app, then click **Import module package**, and select the component you downloaded:
-
-    {{< figure src="/attachments/appstore/use-content/import-module-in-app-explorer.png" alt="import-module-in-app-explorer" class="no-border" >}}
-
-    The **Import Module** dialog box opens. 
-
+5. In the **App Explorer**, right-click the app, then click **Import module package**, and select the component you downloaded.    
+   The **Import Module** dialog box opens. 
 6. In the **Import Module** dialog box, select one of these options:
 
     * **Add as a new module** (default option when the module is downloaded to your app for the first time ) – If you select this option, new entities and attributes are created in your app.
@@ -236,7 +232,7 @@ After you place the widget on your page, some new errors can appear in the [Erro
 
 To configure the widget, follow these steps:
 
-1. Go to the **Errors** pane and check the error message. This error shows after you drop the **Rating** widget into the page:
+1. Go to the **Errors** pane and check the error message. This error shows after you drop the **Rating** widget into the page.
 
     {{< figure src="/attachments/appstore/use-content/widget-errors.png" alt="Errors pane" class="no-border" >}}
 
diff --git a/content/en/docs/support/deployment-strategy-support.md b/content/en/docs/support/deployment-strategy-support.md
diff --git a/content/en/docs/support/prepare-your-app.md b/content/en/docs/support/prepare-your-app.md
diff --git a/content/en/docs/support/submit-support-request.md b/content/en/docs/support/submit-support-request.md
