From 25f4c450665eeb74f3ff5942b3495e1dc82bf4ec Mon Sep 17 00:00:00 2001 From: NatasaKralj <83953175+NatasaKralj@users.noreply.github.com> Date: Sat, 1 Nov 2025 20:13:41 +0000 Subject: [PATCH 1/2] Run markdownlint-cli2 on docs to find (and correct) linting errors. --- .../apidocs/deployment/build-api.md | 4 +-- .../local-app-files-api.md | 10 +++---- .../web/web-extensions-howtos/menu-api.md | 1 - .../mx-azure/configuration/_index.md | 26 +++++++++---------- .../deployment/mx-azure/mx-azure-backups.md | 1 + .../deployment/mx-azure/mx-azure-deploy.md | 1 - .../mx-azure-security-and-compliance.md | 1 - .../developerportal/app-insights/feedback.md | 2 +- .../integration/use-a-client-certificate.md | 1 - .../modules/snowflake/mendix-data-loader.md | 2 +- .../mendix-profile/user-settings.md | 1 - .../nt-studio-pro-10-parent/nt-14-rn.md | 2 +- .../nt-studio-pro-11-parent/nt-15-rn.md | 16 ++++++------ .../docs/releasenotes/studio-pro/10/10.18.md | 7 ++--- .../docs/releasenotes/studio-pro/11/11.0.md | 2 +- .../en/docs/releasenotes/studio-pro/9/9.24.md | 4 +-- 16 files changed, 39 insertions(+), 42 deletions(-) diff --git a/content/en/docs/apidocs-mxsdk/apidocs/deployment/build-api.md b/content/en/docs/apidocs-mxsdk/apidocs/deployment/build-api.md index 6a9a8873f6d..a91fe81fdc5 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/deployment/build-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/deployment/build-api.md @@ -296,9 +296,9 @@ An object with the following key-value pairs: {{% alert color="warning" %}} -- For apps using SVN for version control, this call will build the specified revision even if that revision is not on the specified branch. +* For apps using SVN for version control, this call will build the specified revision even if that revision is not on the specified branch. -- For apps using Git for version control, using a short commit hash can cause timeouts with large repositories. Mendix recommends using the full commit hash +* For apps using Git for version control, using a short commit hash can cause timeouts with large repositories. Mendix recommends using the full commit hash {{% /alert %}} ##### Example diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/local-app-files-api.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/local-app-files-api.md index 0dabbe13c44..c67276dbde6 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/local-app-files-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/local-app-files-api.md @@ -67,11 +67,11 @@ Implement the code described in the [Code Descriptions](#code-descriptions) sect }; ``` - ## Code Descriptions {#code-descriptions} +## Code Descriptions {#code-descriptions} The following sections explain the various parts of the code. - ### saveFile +### saveFile The `saveFile` callback calls the `putFile` API. It sets the file name to `HelloWorld.txt` and the content to `Hello world from a file!`. @@ -85,7 +85,7 @@ Implement the code described in the [Code Descriptions](#code-descriptions) sect }; ``` - ### loadFile +### loadFile The `loadFile` callback calls the `getFile` API. It requests to load `HelloWorld.txt`, then shows a message box that displays the content of the file. @@ -99,7 +99,7 @@ Implement the code described in the [Code Descriptions](#code-descriptions) sect }; ``` - ### deleteFile +### deleteFile The `deleteFile` callback calls the `deleteFile` API. It requests to delete `HelloWorld.txt`. @@ -110,7 +110,7 @@ Implement the code described in the [Code Descriptions](#code-descriptions) sect }; ``` - ### Adding Buttons +### Adding Buttons The final part of the code adds three new buttons which, when clicked, call the callbacks described above. diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/menu-api.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/menu-api.md index 9a6d1f87151..7af3650a9a1 100644 --- a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/menu-api.md +++ b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/web-extensions-howtos/menu-api.md @@ -29,7 +29,6 @@ A menu has the following properties: | `hasSeparatorAfter`
(default: `false`) | Adds a visual separator after the item | | `enabled`
(default: `true`) | Indicates that the menu item notifies the listener when clicked | - {{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/web/menus/grouped_menus.png" width="300" >}} ## Creating a Simple Menu diff --git a/content/en/docs/deployment/mx-azure/configuration/_index.md b/content/en/docs/deployment/mx-azure/configuration/_index.md index aebb397a642..30933c0c4ba 100644 --- a/content/en/docs/deployment/mx-azure/configuration/_index.md +++ b/content/en/docs/deployment/mx-azure/configuration/_index.md @@ -29,31 +29,31 @@ The [Mendix on Azure Portal](https://mendixonazure.mendix.com) provides a variet | --- | --- | --- | | Load Balancer Type | Controls whether your applications are reachable publicly or only privately via your own (Virtual) Network or Private Endpoints. | Yes | | AKS Node CIDR IP Range | Defines the IP address range on the VNet hosting AKS cluster nodes. This can only be set during initial deployment and should align with your organization's IP plan if you plan to connect Mendix on Azure to other networks via peering. Default is acceptable when no interconnection is required. | No | -| AKS Network Isolated Cluster | When set to true will lead to a cluster without egress configuration, please carefully read the [documentation on cluster networking modes ](/developerportal/deploy/mendix-on-azure/configuration/ingress-egress/) to understand the implications | No | +| AKS Network Isolated Cluster | When set to true will lead to a cluster without egress configuration, please carefully read the [documentation on cluster networking modes](/developerportal/deploy/mendix-on-azure/configuration/ingress-egress/) to understand the implications | No | For more information, see [Configuring Ingress and Egress](/developerportal/deploy/mendix-on-azure/configuration/ingress-egress/). ### Application Cluster Settings -| Advanced Option | Description | Editable after Initial Creation | -| --- | --- | --- | +| Advanced Option | Description | Editable after Initial Creation | +| --- | --- | --- | | AKS Node VM Size | The VM size used on the AKS application cluster. Default should suffice in most circumstances. You can change the default size in case of performance issues (for example, using non-burstable instances can improve Mendix Runtime performance), or if your Mendix app environment instances require more RAM than available under current selection. In case a Mendix app environment instance is configured to require more RAM than available on the current VM size, switching to a larger VM size might be required to have the app instance start at all. | Yes | -| AKS Maximum Node Count | The number of available cluster nodes will be increased and decreased automatically based on the combined capacity requirement of all deployed Mendix apps. This setting controls the upper limit to the number of available nodes in order to avoid cost surprises. | Yes | -| AKS Service Tier | The [AKS service tier](https://learn.microsoft.com/en-us/azure/aks/free-standard-pricing-tiers) determines the service level Microsoft provides on the Mendix on Azure Kubernetes cluster control plane. This does not impact application performance, only Microsoft's SLA. The Free tier is sufficient in most situations. Standard can be considered by organizations that value a financially backed SLA. For information about the associated costs, refer to Microsoft documentation. The Premium tier does not offer any additional value in combination with Mendix on Azure and is not recommended. | Yes | +| AKS Maximum Node Count | The number of available cluster nodes will be increased and decreased automatically based on the combined capacity requirement of all deployed Mendix apps. This setting controls the upper limit to the number of available nodes in order to avoid cost surprises. | Yes | +| AKS Service Tier | The [AKS service tier](https://learn.microsoft.com/en-us/azure/aks/free-standard-pricing-tiers) determines the service level Microsoft provides on the Mendix on Azure Kubernetes cluster control plane. This does not impact application performance, only Microsoft's SLA. The Free tier is sufficient in most situations. Standard can be considered by organizations that value a financially backed SLA. For information about the associated costs, refer to Microsoft documentation. The Premium tier does not offer any additional value in combination with Mendix on Azure and is not recommended. | Yes | ### Database Settings -| Advanced Option | Description | Editable after initial creation | -| --- | --- | --- | -| Enable Read Replica | Enables a read replica for direct app database access. For more information, see [Direct Database Access](/developerportal/deploy/mendix-on-azure/configuration/direct-database-access/). | Yes | -| Compute Tier and Size | Specifies the DB Compute Tier for the shared PostgreSQL database used by all Mendix app environments. You may need to increase it for better app performance. For more information, see [Compute options in Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-compute) in Microsoft documentation. | Yes | -| Storage Performance Tier | Specifies the Storage Performance Tier for the shared PostgreSQL database. Consider increasing if performance issues arise. For more information, see [Storage in Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-storage) in Microsoft documentation. | Yes | +| Advanced Option | Description | Editable after initial creation | +| --- | --- | --- | +| Enable Read Replica | Enables a read replica for direct app database access. For more information, see [Direct Database Access](/developerportal/deploy/mendix-on-azure/configuration/direct-database-access/). | Yes | +| Compute Tier and Size | Specifies the DB Compute Tier for the shared PostgreSQL database used by all Mendix app environments. You may need to increase it for better app performance. For more information, see [Compute options in Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-compute) in Microsoft documentation. | Yes | +| Storage Performance Tier | Specifies the Storage Performance Tier for the shared PostgreSQL database. Consider increasing if performance issues arise. For more information, see [Storage in Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-storage) in Microsoft documentation. | Yes | ### Observability Settings -| Advanced Option | Description | Editable after initial creation | -| --- | --- | --- | -| Managed Grafana Accessibility | Determines whether the Managed Grafana observability dashboard is accessible publicly or only via private endpoints. [Virtual network peering](/developerportal/deploy/mendix-on-azure/configuration/interconnecting-networks/#network-peering) is required for private access. | Yes | +| Advanced Option | Description | Editable after initial creation | +| --- | --- | --- | +| Managed Grafana Accessibility | Determines whether the Managed Grafana observability dashboard is accessible publicly or only via private endpoints. [Virtual network peering](/developerportal/deploy/mendix-on-azure/configuration/interconnecting-networks/#network-peering) is required for private access. | Yes | ## Self-service configuration available via Microsoft Azure Portal diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index 279fdbe03b0..a266d603fb6 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -27,6 +27,7 @@ You must have **Manage Apps Backups** permission for the namespace to use this f {{% alert color="info" %}} Backups cannot be created while the environment is in any of these states: + * Creation in progress * Creation failed * Deployment package is being deployed diff --git a/content/en/docs/deployment/mx-azure/mx-azure-deploy.md b/content/en/docs/deployment/mx-azure/mx-azure-deploy.md index 6613da3eb22..19720aa2372 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-deploy.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-deploy.md @@ -44,7 +44,6 @@ To deploy the solution, perform the following steps: {{< figure src="/attachments/deployment/mx-azure/available-clusters.png" class="no-border" >}} - 7. Identify the entry belonging to the Managed Application you deployed in previous steps. In the **Actions** column, click the dropdown menu icon, and then select **Initialize**. The preflight check launches to verify the conditions are in place to successfully initialize a Mendix on Azure cluster. diff --git a/content/en/docs/deployment/mx-azure/mx-azure-security-and-compliance.md b/content/en/docs/deployment/mx-azure/mx-azure-security-and-compliance.md index ad6d92e9583..bb45c073086 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-security-and-compliance.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-security-and-compliance.md @@ -23,7 +23,6 @@ The automatic SOC2 assessment currently has identified the following compliance | AKS - cluster VNET: [All Internet traffic should be routed via your deployed Azure Firewall](https://www.azadvertizer.net/azpolicyadvertizer/fc5e4038-4584-4632-8c85-c0448d374b2c.html) | This is not automated, but customers can deploy their own Firewall if required. | | Storage Account: [Storage accounts should use customer-managed key for encryption](https://www.azadvertizer.net/azpolicyadvertizer/6fac406b-40ca-413b-bf8e-0bf964659c25.html) | The cluster is deployed and managed by Mendix, so this is not needed. | - ### Access to Customer Environments by Mendix Mendix accesses customer environments securely by leveraging native Azure capabilities and adhering to Microsoft's best practices: diff --git a/content/en/docs/developerportal/app-insights/feedback.md b/content/en/docs/developerportal/app-insights/feedback.md index e5b6d134e94..51400830079 100644 --- a/content/en/docs/developerportal/app-insights/feedback.md +++ b/content/en/docs/developerportal/app-insights/feedback.md @@ -135,7 +135,7 @@ The following options are available: * **Ungroup** – Ungroup all feedback in the group. This action does not delete the group. * **Delete Group** – Delete the group and all feedback within it. This action is destructive and, once you delete a group with feedback, the feedback is also deleted. * Group Name – The name of the group, which you can edit by clicking it. - * **Description** – The description of the group. + * **Description** – The description of the group. * **Tags** – Any tags assigned to the group. You can either select a tag from the drop-down list, or create a new tag by typing its name inside the text box, then clicking **Create [the tag name]**. A tag should contain maximum 50 characters. diff --git a/content/en/docs/howto9/integration/use-a-client-certificate.md b/content/en/docs/howto9/integration/use-a-client-certificate.md index 3a8f8f8e006..2ebe461f67f 100644 --- a/content/en/docs/howto9/integration/use-a-client-certificate.md +++ b/content/en/docs/howto9/integration/use-a-client-certificate.md @@ -78,4 +78,3 @@ To configure client certificates in Mendix Cloud, follow these steps: 3. Close the **Details** screen. 6. Click **Stop application** and then **Start application**. - diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md index 45698979c72..3b66ab82dff 100755 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md @@ -66,7 +66,7 @@ If you want to use specific resources, you should instead expose a new endpoint 9. Click **Back** to return to the **Details** page. 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table. 11. Click **Create** to start setting up the Ingestion Configuration. - * **Target Database** – Name of the database for data ingestion + ***Target Database** – Name of the database for data ingestion * **Target Schema** – Target schema where all data will be ingested 12. Click **Save**. 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule. diff --git a/content/en/docs/mendix-portal/mendix-profile/user-settings.md b/content/en/docs/mendix-portal/mendix-profile/user-settings.md index 66b14cb678c..55ba5872da7 100644 --- a/content/en/docs/mendix-portal/mendix-profile/user-settings.md +++ b/content/en/docs/mendix-portal/mendix-profile/user-settings.md @@ -29,7 +29,6 @@ This is what you can do on the [Profile](https://user-settings.mendix.com/link/p * Choose to make your profile public by clicking **Make Profile Public**. This allows the Mendix community to view your profile. To make your public profile private again, click **Make Profile Private**. - * Add a **Recovery Email** address, which is useful if you lose access to your account or Mendix Profile. You can provide a non-business email address for this. ### Merging Profiles {#merging-profiles} diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md index 944e90f896b..92a5ad74848 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-10-parent/nt-14-rn.md @@ -11,7 +11,7 @@ description: "Native Template 14" ### Improvements -- We have installed react-native-edge-to-edge to ensure proper layout behavior and visual consistency on Android 15 and newer devices. +* We have installed react-native-edge-to-edge to ensure proper layout behavior and visual consistency on Android 15 and newer devices. ## 14.1.6 {#1416} diff --git a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md index e7c4c0c5955..adc5362dd2d 100644 --- a/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md +++ b/content/en/docs/releasenotes/mobile/native-template/nt-studio-pro-11-parent/nt-15-rn.md @@ -11,7 +11,7 @@ description: "Native Template 15" ### Improvements -- We have installed react-native-edge-to-edge to ensure proper layout behavior and visual consistency on Android 15 and newer devices. +* We have installed react-native-edge-to-edge to ensure proper layout behavior and visual consistency on Android 15 and newer devices. ## 15.4.1 {#1541} @@ -19,7 +19,7 @@ description: "Native Template 15" ### Improvements -- We migrated from `react-native-camera` to `react-native-vision-camera` for new architecture compatibility. +* We migrated from `react-native-camera` to `react-native-vision-camera` for new architecture compatibility. ## 15.4.0 {#1540} @@ -27,12 +27,12 @@ description: "Native Template 15" ### Improvements -- We migrated from `react-native-push-notification` to `@notifee/react-native` for improved architecture compatibility and enhanced push notification features. -- We upgraded `react-native-permissions` to version 5.4.2. -- We removed `react-native-schedule-exact-alarm-permission` dependency. -- We added a `USE_BIOMETRIC` permission in Android. -- We migrated from `react-native-fast-image` to `@d11/react-native-fast-image` for new architecture compatibility. -- We upgraded `react-native-reanimated` to v3.16.7. +* We migrated from `react-native-push-notification` to `@notifee/react-native` for improved architecture compatibility and enhanced push notification features. +* We upgraded `react-native-permissions` to version 5.4.2. +* We removed `react-native-schedule-exact-alarm-permission` dependency. +* We added a `USE_BIOMETRIC` permission in Android. +* We migrated from `react-native-fast-image` to `@d11/react-native-fast-image` for new architecture compatibility. +* We upgraded `react-native-reanimated` to v3.16.7. ## 15.3.1 {#1531} diff --git a/content/en/docs/releasenotes/studio-pro/10/10.18.md b/content/en/docs/releasenotes/studio-pro/10/10.18.md index 71d77bac597..b88cbe53a81 100644 --- a/content/en/docs/releasenotes/studio-pro/10/10.18.md +++ b/content/en/docs/releasenotes/studio-pro/10/10.18.md @@ -15,9 +15,10 @@ weight: 82 ### Fixes -- We fixed an issue in the interactive documentation (Swagger UI) page for published OData services, which would indicate that it did not support OpenAPI version 3.0.4. (Tickets 256982, 257611) -- We added refresh functionality for Marketplace when a session times out. The reload button properly handles the event by closing the details page and refreshing the **Search** tab view. -- We fixed an issue where task queue tasks were not able to mark themselves as completed after execution. +* We fixed an issue in the interactive documentation (Swagger UI) page for published OData services, which would indicate that it did not support OpenAPI version 3.0.4. (Tickets 256982, 257611) +* We added refresh functionality for Marketplace when a session times out. The reload button properly handles the event by closing the details page and refreshing the **Search** tab view. +* We fixed an issue where task queue tasks were not able to mark themselves as completed after execution. + * We fixed an issue where trying to delete a huge number (millions) of anonymous sessions during startup would cause out of memory errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047) ## 10.18.11 {#101811} diff --git a/content/en/docs/releasenotes/studio-pro/11/11.0.md b/content/en/docs/releasenotes/studio-pro/11/11.0.md index a6a7c92bc61..d0aca65ff79 100644 --- a/content/en/docs/releasenotes/studio-pro/11/11.0.md +++ b/content/en/docs/releasenotes/studio-pro/11/11.0.md @@ -361,4 +361,4 @@ For details on upgrading to Studio Pro 11, see [Upgrading from Mendix Studio Pro * In the React client, the debugger does not reconnect when restarting an app. * Fixed in [11.1.0](/releasenotes/studio-pro/11.1/#fix-debugger-reconnect). * When loading a view entity without entity access applied, an exception is thrown if it is then used in a context requiring entity access. (Tickets 257900, 259602, 260557) - * Fixed in [11.2.0](/releasenotes/studio-pro/11.2/#fix-view-entity-context-switch). \ No newline at end of file + * Fixed in [11.2.0](/releasenotes/studio-pro/11.2/#fix-view-entity-context-switch). diff --git a/content/en/docs/releasenotes/studio-pro/9/9.24.md b/content/en/docs/releasenotes/studio-pro/9/9.24.md index 5f1fb234444..9856bf34185 100644 --- a/content/en/docs/releasenotes/studio-pro/9/9.24.md +++ b/content/en/docs/releasenotes/studio-pro/9/9.24.md @@ -19,11 +19,11 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 9 release for a ### Improvements -- We now avoid resetting a failed login count during login when it is already zero. (Ticket 260858) +* We now avoid resetting a failed login count during login when it is already zero. (Ticket 260858) ### Fixes -- We fixed an issue where **Import Mappings** using **Find an object (by key)** or **Call a microflow** did not create an object for valid input. (Tickets 255130, 260462) +* We fixed an issue where **Import Mappings** using **Find an object (by key)** or **Call a microflow** did not create an object for valid input. (Tickets 255130, 260462) ## 9.24.39 From 3f7e3cb6db61487cafa48d5ac762eae9124fb922 Mon Sep 17 00:00:00 2001 From: Olufunke Moronfolu Date: Mon, 3 Nov 2025 13:40:03 +0100 Subject: [PATCH 2/2] lint correction --- content/en/docs/developerportal/app-insights/feedback.md | 2 +- .../modules/snowflake/mendix-data-loader.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/developerportal/app-insights/feedback.md b/content/en/docs/developerportal/app-insights/feedback.md index 51400830079..f29dec02b5e 100644 --- a/content/en/docs/developerportal/app-insights/feedback.md +++ b/content/en/docs/developerportal/app-insights/feedback.md @@ -134,7 +134,7 @@ The following options are available: * **Ungroup** – Ungroup all feedback in the group. This action does not delete the group. * **Delete Group** – Delete the group and all feedback within it. This action is destructive and, once you delete a group with feedback, the feedback is also deleted. -* Group Name – The name of the group, which you can edit by clicking it. +* **Group Name** – The name of the group, which you can edit by clicking it. * **Description** – The description of the group. * **Tags** – Any tags assigned to the group. You can either select a tag from the drop-down list, or create a new tag by typing its name inside the text box, then clicking **Create [the tag name]**. diff --git a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md index 3b66ab82dff..45698979c72 100755 --- a/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md +++ b/content/en/docs/marketplace/platform-supported-content/modules/snowflake/mendix-data-loader.md @@ -66,7 +66,7 @@ If you want to use specific resources, you should instead expose a new endpoint 9. Click **Back** to return to the **Details** page. 10. Click the **Ingestion Configuration** tab to set up your ingestion destination table. 11. Click **Create** to start setting up the Ingestion Configuration. - ***Target Database** – Name of the database for data ingestion + * **Target Database** – Name of the database for data ingestion * **Target Schema** – Target schema where all data will be ingested 12. Click **Save**. 13. Click the **Data Ingestion** tab, where you can start your data ingestion or set up a schedule.