Merge branch 'development' into teamserver-svn-drop-tls-v1

Author: MarkvanMents

content/en/docs/refguide/mobile/distributing-mobile-apps/overtheair-updates.md

@@ -23,7 +23,7 @@ Currently OTA does not update your app while the app is open or minimized.
 {{% /alert %}}
 
 {{% alert color="info" %}}
-Mendix OTA updates are the replacement for the deprecated [Release Over the Air Updates with App Center's CodePush (Deprecated)](/refguide/mobile/distributing-mobile-apps/overtheair-updates/). When opting in for OTA updates via the Mendix Runtime, CodePush OTA updates will be disabled. 
+Mendix OTA updates are the replacement for the deprecated [Release Over the Air Updates with App Center's CodePush (Deprecated)](/howto8/mobile/how-to-ota/). When opting in for OTA updates via the Mendix Runtime, CodePush OTA updates will be disabled. 
 {{% /alert %}}
 
 This guide will teach you how to do the following:

content/en/docs/refguide/modeling/pages/image-and-file-widgets/_index.md

@@ -1,13 +1,13 @@
 ---
-title: "Images, Videos and Files"
+title: "Images, Videos, and Files"
 url: /refguide/image-and-file-widgets/
 weight: 35
 tags: ["studio pro", "file widgets", "widget"]
 ---
 
 ## 1 Introduction
 
-Images, videos and files allow end-users to upload, download, and display files, images, and videos. 
+Images, videos, and files allow end-users to upload, download, and display files, images, and videos. 
 
 * [Static Image](/refguide/image/) – displays static image:
 

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/_index.md

@@ -119,7 +119,7 @@ If you also changed Java source code, added widgets or made other changes that a
 
 Committing is only allowed if your working copy is up to date with the repository. If someone else committed a change since the last time you pulled, you will have to pull first. This is because the revision you create with the commit should incorporate both your changes and the changes by the other person. Updating will combine the latest changes in the repository with your changes. After reviewing the result, and fixing any conflicts, you can commit again.
 
-### 4.3 Pushing
+### 4.3 Pushing {#pushing}
 
 Pushing is sending your local changes to the Team Server. After committing you need to push the committed changes if you want them to be accessible to others. By default, this is done when committing, but it is possible to wait for this step until later.
 

content/en/docs/refguide9/general/install.md

@@ -67,8 +67,8 @@ The prerequisites are the following:
 * Java JDK
 
     * For Mendix Studio Pro 9.18.0 and above – [Eclipse Temurin JDK 11 (x64)](https://github.com/adoptium/temurin11-binaries/releases)
-    * For Mendix Studio Pro versions above 9.14.0 but below 9.18.0 – [Adoptium Temurin Java SDK](https://github.com/adoptium/temurin11-binaries/releases/download/jdk-11.0.14.1%2B1/OpenJDK11U-jdk_x64_windows_hotspot_11.0.14.1_1.msi)
-    * For Mendix Studio Pro versions below 9.14.0 – [AdoptOpenJDK 11](https://cdn.mendix.com/installer/AdoptOpenJDK/OpenJDK11U-jdk_x64_windows_hotspot_11.0.3_7.msi)
+    * For Mendix Studio Pro 9.14 to 9.17 – [Adoptium Temurin Java SDK](https://github.com/adoptium/temurin11-binaries/releases/download/jdk-11.0.14.1%2B1/OpenJDK11U-jdk_x64_windows_hotspot_11.0.14.1_1.msi)
+    * For Mendix Studio Pro 9.13 and below – [AdoptOpenJDK 11](https://cdn.mendix.com/installer/AdoptOpenJDK/OpenJDK11U-jdk_x64_windows_hotspot_11.0.3_7.msi)
 * [Microsoft Visual C++ 2015 and 2019 Redistributable Package](https://aka.ms/vs/16/release/vc_redist.x64.exe)
 * [Mendix Native Mobile Builder one-click Installer](https://appdev-mx-cdn.s3.amazonaws.com/native-builders/latest.exe)
 * [Git for Windows (x64)](https://git-scm.com/download/win) using the following versions:
@@ -78,7 +78,7 @@ The prerequisites are the following:
     | [2.37.1](https://github.com/git-for-windows/git/releases/tag/v2.37.1.windows.1) | [2.41.0](https://github.com/git-for-windows/git/releases/tag/v2.41.0.windows.3) |
 
 * [Microsoft Edge WebView2 Evergreen Runtime (x64 or ARM64) (Evergreen Standalone Installer version)](https://developer.microsoft.com/en-us/microsoft-edge/webview2/)
-* For Mendix Studio Pro version 9.24.0 and above – [Gradle 7.6 or above](https://services.gradle.org/distributions/gradle-7.6-bin.zip)
+* For Mendix Studio Pro 9.24.0 and above – [Gradle 7.6 or above](https://services.gradle.org/distributions/gradle-7.6-bin.zip)
 
 Based on the error message you get from the installer you can decide to install a single prerequisite, or you can try to manually install them all.
 

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

@@ -73,7 +73,7 @@ Return codes are described in the table below:
 
 ### 3.2 mx create-project Command
 
-The `mx create-project` command creates a new app in Studio Pro. The app version depends on the version the tool was bundled with. For example, if you are using the mx tool for Studio Pro version 8.1.0.58215,  `mx create project` will create a new app in that version. 
+The `mx create-project` command creates a new app in Studio Pro. The app version depends on the version the tool was bundled with. For example, if you are using the mx tool for Studio Pro 8.1.0.58215,  `mx create project` will create a new app in that version. 
 
 #### 3.2.1 Usage
 
@@ -139,7 +139,7 @@ Errors in the MPR are always reported.
 
 For `INPUT`, enter a single *.mpr* file.
 
-From Studio Pro version 9.17, you can optionally specify the path to an exported Suppress Warnings file (JSON file). This means that `mx check -w` will use the list of suppressed warnings in the JSON file, instead of the default behavior which is to read from the *project-settings.user.json* file in the app directory.
+From Studio Pro 9.17, you can optionally specify the path to an exported Suppress Warnings file (JSON file). This means that `mx check -w` will use the list of suppressed warnings in the JSON file, instead of the default behavior which is to read from the *project-settings.user.json* file in the app directory.
 
 #### 3.3.2 Examples
 

content/en/docs/refguide9/general/system-requirements.md

@@ -201,7 +201,7 @@ Current support:
 * [Oracle Database](/refguide9/oracle/): 19, 21c
 * PostgreSQL: 11, 12, 13, 14, 15
 * [SAP HANA](/refguide9/saphana/): 2.00.040.00.1545918182
-* [IBM DB2](/refguide9/db2/): 11.5 for Linux, Unix, and Windows (please note that support for DB2 is deprecated and will be removed in Studio Pro version 10)
+* [IBM DB2](/refguide9/db2/): 11.5 for Linux, Unix, and Windows (please note that support for DB2 is deprecated and will be removed in Studio Pro 10)
 
 {{% alert color="warning" %}}
 Each app must have its own database. Mendix apps cannot share data by sharing the same database.

content/en/docs/refguide9/mobile/distributing-mobile-apps/overtheair-updates.md

@@ -23,7 +23,7 @@ Currently OTA does not update your app while the app is open or minimized.
 {{% /alert %}}
 
 {{% alert color="info" %}}
-Mendix OTA updates are the replacement for the deprecated [Release Over the Air Updates with App Center's CodePush (Deprecated)](/refguide9/mobile/distributing-mobile-apps/overtheair-updates/). When opting in for OTA updates via the Mendix Runtime, CodePush OTA updates will be disabled. 
+Mendix OTA updates are the replacement for the deprecated [Release Over the Air Updates with App Center's CodePush (Deprecated)](/howto8/mobile/how-to-ota/). When opting in for OTA updates via the Mendix Runtime, CodePush OTA updates will be disabled. 
 {{% /alert %}}
 
 This guide will teach you how to do the following:

content/en/docs/refguide9/mobile/using-mobile-capabilities/mobile-accessibility.md

@@ -16,7 +16,7 @@ This guide only applies to native mobile apps.
 
 Before starting this guide, make sure you have completed the following prerequisites:
 
-* Install Mendix Studio Pro version **9.22.0** or above
+* Install Mendix Studio Pro [9.22.0](/releasenotes/studio-pro/9.22/) or above
 * Complete the [Prerequisites](/refguide9/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Deploy Your First Mendix Native Mobile App*
 * Make sure you are using [Make It Native 9 app](/releasenotes/mobile/make-it-native-parent/)
 

content/en/docs/refguide9/mobile/using-mobile-capabilities/native-language-change.md

@@ -20,7 +20,7 @@ While this guide gives your end-user the ability to switch their app's language,
 
 Before starting this guide, make sure you have completed the following prerequisites:
 
-* Install Mendix Studio Pro version **9.14.0** or above
+* Install Mendix Studio Pro [9.14.0](/releasenotes/studio-pro/9.14/) or above
 * Complete the [Prerequisites](/refguide9/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Deploy Your First Mendix Native Mobile App*
 * Make sure your [Nanoflow Commons](/appstore/modules/nanoflow-commons/) module is up to date
 * Read the [Language Menu](/refguide9/translatable-texts/) guide to understand the basics of the Mendix Language menu

content/en/docs/refguide9/modeling/app-explorer/modules/configure-add-on-and-solution-modules.md

@@ -67,7 +67,7 @@ Below is the list of documents and elements that can be mark as **Usable**:
 ## 3 Exporting Add-on Modules and Solutions {#export}
 
 {{% alert color="info" %}}
-Before exporting an add-on module or a solution to customers, note that for Studio Pro versions 9.22 and below, English (US) and Dutch language translations are shipped with it by default, and for Studio Pro versions 9.23 and above, only English (US) is shipped by default (for more information, see the [Internationalization Improvements](/releasenotes/studio-pro/9.23/#internationalization-improvements) section of *9.23* Studio Pro release notes). This may be important if your app is in another language (not English (US) or Dutch) and your customers decide to translate the consumed solution or add-on to other languages. To avoid confusion, open [Language](/refguide9/translatable-texts/) > **Language Operations** and select the **Delete** operation for English (US) and/or Dutch. For more information on how to perform a certain operation, see [Language Operations](/refguide9/language-operations/).
+Before exporting an add-on module or a solution to customers, note that for Studio Pro 9.22 and below, English (US) and Dutch language translations are shipped with it by default, and for Studio Pro 9.23 and above, only English (US) is shipped by default (for more information, see the [Internationalization Improvements](/releasenotes/studio-pro/9.23/#internationalization-improvements) section of *9.23* Studio Pro release notes). This may be important if your app is in another language (not English (US) or Dutch) and your customers decide to translate the consumed solution or add-on to other languages. To avoid confusion, open [Language](/refguide9/translatable-texts/) > **Language Operations** and select the **Delete** operation for English (US) and/or Dutch. For more information on how to perform a certain operation, see [Language Operations](/refguide9/language-operations/).
 {{% /alert %}}
 
 ### 3.1 Exporting Add-on Module Package