Remove references to MTS where version is no longer MTS

content/en/docs/refguide10/general/mx-command-line-tool/app.md

@@ -96,7 +96,7 @@ These are the return codes:
 ## mx show-java-version Command{#show-java-version}
 
 {{% alert color="info" %}}
-This command is available from 10.14 onwards and in MTS versions 10.6.12+ and 10.12.2+.
+This command is available from 10.14 onwards and in versions 10.6.12+ and 10.12.2+.
 {{% /alert %}}
 
 The `mx show-java-version` command reports what the configured Java version of the app is.

content/en/docs/refguide10/installation/install.md

@@ -121,7 +121,7 @@ It is possible to prepare the prerequisite installers beforehand so the setup pr
       * Rename the *latest.exe* executable to *mendix_native_mobile_builder.exe*
    5. Git for Windows (x64)
       * For Studio Pro versions 10.0.0 and 10.1.0, rename the *Git-2.37.1-64-bit.exe* executable to *git_for_windows_installer.exe*
-      * For Studio Pro versions 10.2.0, 10.6.10 (or 10.6 MTS above 10.6.10), and 10.9.0, rename the *Git-2.41.0.3-64-bit.exe* executable to *git_for_windows_installer.exe*
+      * For Studio Pro versions 10.2.0, 10.6.10 (or 10.6.x above 10.6.10), and 10.9.0, rename the *Git-2.41.0.3-64-bit.exe* executable to *git_for_windows_installer.exe*
       * For Studio Pro versions 10.10.0 and above, rename the *Git-2.43.0-64-bit.exe* executable to *git_for_windows_installer.exe*
    6. Microsoft Edge WebView2 Evergreen Runtime (x64 or ARM64)
       * The *MicrosoftEdgeWebview2Setup.exe* does not need to be renamed

content/en/docs/refguide10/modeling/integration/machine-learning-kit/using-ml-kit/_index.md

@@ -266,9 +266,9 @@ The table below presents the compatibility list for your models per Studio Pro v
 
 | Studio Pro Version | ONNX Runtime Version |
 | --- | --- |
-| 10.6 MTS  | 1.14.0 |
-| 10.12 MTS (10.12.18 and above) | 1.22.0 |
-| 10.18 MTS (10.18.10 and above) | 1.22.0 |
+| 10.6  | 1.14.0 |
+| 10.12 (10.12.18 and above) | 1.22.0 |
+| 10.18 (10.18.10 and above) | 1.22.0 |
 | 10.24 LTS (10.24.3 and above)  | 1.22.0 |
 
  For more information on the required IR/ML opset versions, see [ONNX Runtime Compatibility](https://onnxruntime.ai/docs/reference/compatibility.html).

content/en/docs/refguide10/modeling/integration/mapping-documents/import-mappings.md

@@ -101,6 +101,6 @@ If you are importing a very long JSON string, the underlying conversion library
 
 Mendix uses the Jackson Core XML library when performing the import mapping and this [has a limit of 20 million](https://javadoc.io/static/com.fasterxml.jackson.core/jackson-core/2.15.1/com/fasterxml/jackson/core/StreamReadConstraints.html#DEFAULT_MAX_STRING_LEN) characters (in earlier versions 5 million) in the JSON string.
 
-In Mendix version 10.9.0 and above and Mendix MTS version 10.6, patch releases 10.6.5 and above, you can override this using the [mapping.import.MaxJsonReadingLength](/refguide10/custom-settings/#mapping.import.MaxJsonReadingLength) custom setting.
+In Mendix version 10.9.0 and above and Mendix version 10.6, patch releases 10.6.5 and above, you can override this using the [mapping.import.MaxJsonReadingLength](/refguide10/custom-settings/#mapping.import.MaxJsonReadingLength) custom setting.
 
 Mendix recommends that you only add this setting if you will be getting very long JSON strings as it may result in more memory usage.

content/en/docs/refguide10/modeling/menus/edit-menu/preferences-dialog.md

@@ -192,7 +192,7 @@ Changing these values for another application will also affect the commits made
 #### Enable Current Windows User Authentication {#enable-windows-authentication}
 
 {{% alert color="info" %}}
-This setting is available in Studio Pro MTS versions 10.6.21 and above, 10.12.14 and above, 10.18.3 and above.
+This setting is available in Studio Pro versions 10.6.x (10.6.21 and above), 10.12.x (10.12.14 and above), and 10.18.3 and above.
 {{% /alert %}}
 
 When this option is selected, the application automatically uses credentials of the currently logged-in Windows user to authenticate and connect to the on-premises Git server. This feature streamlines the authentication process by eliminating the need for users to manually enter their credentials, enhancing both security and user convenience. By leveraging Windows authentication, organizations can ensure that access to the Git server is seamlessly integrated with their existing IT infrastructure, providing a smooth and efficient workflow for development teams.

content/en/docs/refguide10/runtime/custom-settings/_index.md

@@ -75,7 +75,7 @@ The following custom settings can be configured:
 | <a id="UploadedFilesPath" href="#UploadedFilesPath">UploadedFilesPath</a> | The location of the uploaded files. A valid path can be: `\\FileServer\CustomerPortalFiles`. | [deployment folder]\data\files |
 | <a id="EnableFileDocumentCaching" href="#EnableFileDocumentCaching">EnableFileDocumentCaching</a> | Defines whether file documents should be cached. Only enable this if you are sure that the file documents will not contain sensitive information. Images are always cached. | false |
 | <a id="ObjectManagementStrictChangeBehavior" href="#ObjectManagementStrictChangeBehavior">ObjectManagement.<wbr>StrictChangeBehavior</a> | Defines the behavior when changing values of Enums and Calculated attributes.<br/>When set to true, setting an invalid value for an Enum attribute and/or setting a value for a Calculated attribute will result in an InvalidEnumerationValueException and/or ReadOnlyAttributeException respectively.<br/>When set to false, changes to the values of Enums and/or Calculated attributes will be allowed.<br/>We plan to remove this setting in Mendix 11, after which, an exception will always be raised when setting an invalid value. | true |
-| <a id="mapping.import.MaxJsonReadingLength" href="#mapping.import.MaxJsonReadingLength">mapping.import.MaxJsonReadingLength</a> | The maximum length of the JSON string received from the remote which can be processed with import mapping. Use this setting when you expect a string which is longer than the default. See [Import Mappings](/refguide10/import-mappings/#troubleshooting) for more information. <br />*This setting was introduced in Mendix version 10.9.0 and Mendix MTS version 10.6, patch version 10.6.5.* | 20000000 *(dependent on library version)* |
+| <a id="mapping.import.MaxJsonReadingLength" href="#mapping.import.MaxJsonReadingLength">mapping.import.MaxJsonReadingLength</a> | The maximum length of the JSON string received from the remote which can be processed with import mapping. Use this setting when you expect a string which is longer than the default. See [Import Mappings](/refguide10/import-mappings/#troubleshooting) for more information. <br />*This setting was introduced in Mendix version 10.9.0 and Mendix version 10.6, patch version 10.6.5.* | 20000000 *(dependent on library version)* |
 
 ### ApplicationRootUrl {#applicationrooturl-section}
 
@@ -269,8 +269,8 @@ The settings below influence the behavior of the Mendix web client.
 | Name | Description | Default Value |
 | --- | --- | --- |
 | <a id="EnableKeepAlive" href="#EnableKeepAlive">EnableKeepAlive</a> | Defines whether the web client sends a keep alive request every SessionTimeout/2 milliseconds, to prevent a session timeout. Each click in the browser also acts as KeepAlive. Disabling this property will result in a user being logged out automatically after 10 minutes of inactivity, even if the browser remains open. | true |
-| <a id="PhoneUserAgentRegEx" href="#PhoneUserAgentRegEx">PhoneUserAgentRegEx</a> | *This method does not accurately identify devices. It is removed and an alternative method is used in 10.21.0 and above, and MTS versions 10.6.22, 10.12.16, and 10.18.5 and above.*<br />Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a phone. The regular expression is matched against the user-agent header sent by the client's web browser. | Android, Mobile (iPhone, iPod, BlackBerry) |
-| <a id="TabletUserAgentRegEx" href="#TabletUserAgentRegEx">TabletUserAgentRegEx</a> |  *This method does not accurately identify devices. It is removed and an alternative method is used in 10.21.0 and above, and MTS versions 10.6.22, 10.12.16, and 10.18.5 and above.*<br />Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a tablet. The regular expression is matched against the User-Agent header sent by the client's web browser. | Android, iPad |
+| <a id="PhoneUserAgentRegEx" href="#PhoneUserAgentRegEx">PhoneUserAgentRegEx</a> | *This method does not accurately identify devices. It is removed and an alternative method is used in 10.21.0 and above, and versions 10.6.x, 10.12.x, and 10.18.x from versions 10.6.22, 10.12.16, and 10.18.5.*<br />Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a phone. The regular expression is matched against the user-agent header sent by the client's web browser. | Android, Mobile (iPhone, iPod, BlackBerry) |
+| <a id="TabletUserAgentRegEx" href="#TabletUserAgentRegEx">TabletUserAgentRegEx</a> |  *This method does not accurately identify devices. It is removed and an alternative method is used in 10.21.0 and above, and versions 10.6.x, 10.12.x, and 10.18.x from versions 10.6.22, 10.12.16, and 10.18.5.*<br />Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a tablet. The regular expression is matched against the User-Agent header sent by the client's web browser. | Android, iPad |
 | <a id="commendixwebuiHybridAppLoginTimeOut" href="#commendixwebuiHybridAppLoginTimeOut">com.<wbr>mendix.<wbr>webui.<wbr>HybridAppLoginTimeOut</a> | Determines how many minutes your token will remain valid before re-authenticating using your full credentials.  If no value is set the token will expire after One year *(Mendix version 10.9.0 and above)* or never expire *(Mendix versions below 10.9.0)*. |  |
 | <a id="commendixwebuiFeedbackSizeWarningThreshold" href="#commendixwebuiFeedbackSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>FeedbackSizeWarningThreshold</a> | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 |
 | <a id="commendixwebuiStateSizeWarningThreshold" href="#commendixwebuiStateSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>StateSizeWarningThreshold</a> | A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 100 |

content/en/docs/releasenotes/studio-pro/lts-mts.md

@@ -22,11 +22,8 @@ For Mendix 10 and 11, we are planning to follow this release timeline:
 
 | Release | Date |
 | --- | --- |
-| 10.6 MTS | December 2023 |
-| 10.12 MTS | June 2024 |
-| 10.18 MTS | December 2024 |
-| 11.0 GA | June 2025 |
 | 10.24 LTS | June 2025 |
+| 11.0 GA | June 2025 |
 | 11.6 MTS | December 2025 |
 | 11.12 MTS | June 2026 |
 | 11.18 MTS | December 2026 |
@@ -87,21 +84,21 @@ For the support duration, the LTS will receive patch releases only.
 
 ### Upgrading Impact
 
-The impact of upgrading from an LTS to an LTS is often the lowest of these options. That is because an LTS has the longest support duration and only gets critical fixes, which results in high stability over time. In addition, depending on how rigorous your application update/release process is, the upgrade would only have to be done once, as opposed to multiple times between MTS versions or monthly release versions.
+Upgrading from an LTS to an LTS often has the lowest impact compared to other upgrade options. That is because an LTS has the longest support duration and only gets critical fixes, which results in high stability over time. In addition, depending on how rigorous your application update/release process is, the upgrade would only have to be done once, as opposed to multiple times between MTS versions or monthly release versions.
 
 ## Medium-Term Support Version (MTS) {#mts}
 
 An MTS is a minor version released approximately every 6 months after a new major version release for general availability.
 
 There are currently no MTS versions of Studio Pro. The next one that will occur is 11.6, planned for release in [December, 2025](#major-version).
 
-Release notes for the current MTS version are marked with an MTS badge (<text class="badge badge-pill badge-mts" style="margin-left:0px">MTS</text>) in the left sidebar.
+Release notes for any current MTS versions are marked with an MTS badge (<text class="badge badge-pill badge-mts" style="margin-left:0px">MTS</text>) in the left sidebar.
 
 Mendix MTS versions offer a balance between getting the latest and greatest Mendix has to offer every month, and security and stability.
 
 {{% alert color="info" %}}
 
-Mendix recommends using the latest patch version of the release as the latest version will contain the latest fixes.
+Mendix recommends using the latest patch version of the release as this will contain the latest fixes.
 
 {{% /alert %}}