Proofread

Author: adam-dupaski

content/en/docs/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-parent-9/pluggable-widgets-property-types-9.md

@@ -365,7 +365,7 @@ The return type of the expression must be defined using either the `type` or the
 ##### 4.1.2.1 Fixed Return Type
 
 {{% alert color="info" %}}
-The `type` attribute was required in Mendix versions [9.19](/releasenotes/studio-pro/9.19/) and below.
+The `type` attribute was required in Mendix [9.19](/releasenotes/studio-pro/9.19/) and below.
 {{% /alert %}}
 
 You can set a fixed return type for your expression property with one of the supported types from below.

content/en/docs/apidocs-mxsdk/apidocs/pluggable-widgets/pluggable-widgets-property-types.md

@@ -367,7 +367,7 @@ The return type of the expression must be defined using either the `type` or the
 ##### 4.1.2.1 Fixed Return Type
 
 {{% alert color="info" %}}
-The `type` attribute was required in Mendix versions [9.19](/releasenotes/studio-pro/9.19/) and below.
+The `type` attribute was required in Mendix [9.19](/releasenotes/studio-pro/9.19/) and below.
 {{% /alert %}}
 
 You can set a fixed return type for your expression property with one of the supported types from below.

content/en/docs/appstore/modules/document-generation.md

@@ -59,7 +59,7 @@ The PDF document generation service does not store pages or documents at any tim
 ### 1.4 Known Issues {#known-issues}
 
 * Some widgets, such as the [Charts](/appstore/widgets/charts/) widget, might not be fully loaded if they are rendered before all data is available. We check on pending network requests to prevent this, but this is not 100% reliable.
-* If you have the [Application Performance Monitor (APM)](/appstore/partner-solutions/apd/) or [Application Performance Diagnostics (APD)](/appstore/partner-solutions/apd/) add-on enabled in your app, or set the log level of the **Services** log node to *Trace*, the PDF Document Generation module will not be able to generate documents when used in Mendix Cloud. Note: This is only applicable for apps built in Mendix versions below 9.24.5 and Mendix 10.0.0.
+* If you have the [Application Performance Monitor (APM)](/appstore/partner-solutions/apd/) or [Application Performance Diagnostics (APD)](/appstore/partner-solutions/apd/) add-on enabled in your app, or set the log level of the **Services** log node to *Trace*, the PDF Document Generation module will not be able to generate documents when used in Mendix Cloud. Note: This is only applicable for apps built in Mendix 9.24.5 and below and Mendix 10.0.0.
 
 ## 2 Installation {#installation}
 

content/en/docs/appstore/modules/forgot-password.md

@@ -40,7 +40,7 @@ The Forgot Password module has the following dependencies:
 * [Encryption](/appstore/modules/encryption/)
 * [Mx Model Reflection](/appstore/modules/model-reflection/)
 
-² Versions of the Forgot Password module below 4.1.0 (Mendix 8) and 5.1.0 (Mendix version 9 and above), and those for Mendix 7 (3.xx) have a dependency on the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. We recommend that if you are using Mendix versions 8 and above, you upgrade to a later version using the instructions in [Migrate from Email Module with Templates to Email Connector](#migrate-email), below.
+² Versions of the Forgot Password module below 4.1.0 (Mendix 8) and 5.1.0 (Mendix version 9 and above), and those for Mendix 7 (3.xx) have a dependency on the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. We recommend that if you are using Mendix 8 and above, you upgrade to a later version using the instructions in [Migrate from Email Module with Templates to Email Connector](#migrate-email), below.
 
 ## 2 Installing the Forgot Password Module{#installing}
 

content/en/docs/appstore/modules/mendix-sso.md

@@ -18,7 +18,7 @@ Because your app end-users are signing in with a Mendix account, they will all n
 {{% /alert %}}
 
 {{% alert color="info" %}}
-For Mendix versions 9.20 and above, you will need to use version 4.0.1 or above of the Mendix SSO module.
+For Mendix 9.20 and above, you will need to use version 4.0.1 or above of the Mendix SSO module.
 {{% /alert %}}
 
 ### 1.1 Typical Usage Scenarios{#typical-usage}
@@ -65,7 +65,7 @@ If your app does not have the Mendix SSO module, it is available from the Mendix
 If you need a newer version of the Mendix SSO module (for example, to use a new feature), then it is also available from the Marketplace via the same link.
 
 {{% alert color="info" %}}
-For Mendix versions 9.20 and above, you will need to use version 4.0.1 or above of the Mendix SSO module.
+For Mendix 9.20 and above, you will need to use version 4.0.1 or above of the Mendix SSO module.
 {{% /alert %}}
 
 In addition, the Mendix SSO module has a default implementation for user administration. This can be used in any Mendix app, but if you want to implement customized user administration this is also possible. See [Customizing Mendix SSO](#customizing), below, for more information.
@@ -83,7 +83,7 @@ To deactivate Mendix SSO, follow these two steps:
 1. Follow the instructions below to rename the original login file (by default *login-without-sso.html*) in the **theme/web** or **theme** folder of your app to *login.html* — this removes the single sign-on button from your sign in screen:
     1. Open your app directory in File Explorer by selecting the menu item **App** > **Show App Directory in Explorer**.
 
-    2. Go to the **theme/web** folder (for Mendix versions below 9.0.0 this will be the **theme** folder).
+    2. Go to the **theme/web** folder (for Mendix versions below 9.0.0, this is the **theme** folder).
     3. Rename *login.html* to *login-with-sso.html*.
     4. Rename *login-without-sso.html* to *login.html*.
 
@@ -164,7 +164,7 @@ To enable Mendix SSO in your app, follow these steps:
 5. Change the page that Mendix uses to log you in (`login.html`) to allow logging in using SSO. To do this, perform the following steps:
 
     1. Go to **App** > **Show App Directory in Explorer** in Studio Pro to open the app directory in your file explorer.
-    2. Go to the **theme/web** folder (for Mendix versions below 9.0.0 this will be the **theme** folder).
+    2. Go to the **theme/web** folder (for Mendix versions below 9.0.0, this is the **theme** folder).
     3. Rename *login.html* to  *login-without-sso.html*.
     4. Rename *login-with-mendixsso-button.html* or *login-with-mendixsso-automatically.html* to *login.html*. The differences between two versions of the file which you can use to replace `login.html` are as follows:
         * `login-with-mendixsso-button.html` – adds a button to the standard sign in page which the end-user can click to initiate the single sign-on process — this gives the end-user the possibility to sign in using a user name and password if desired

content/en/docs/appstore/modules/saml.md

@@ -154,7 +154,7 @@ By default, the SAML module will be installed as the **SAML20** module in your a
 You can use single sign on to automatically sign users in to your app by redirecting every user accessing `index.html` to the Mendix `/SSO/` endpoint. To do this, you need to add `<meta http-equiv="refresh" content="0;URL=/SSO/" />` to the `index.html` file.
 
 {{% alert color="info" %}}
-For Mendix versions 9 and 10, there is no `index.html` file, so you need to create this file first. You can find instructions on how to do this in the [Customizing index.html (Web)](/howto/front-end/customize-styling-new/#custom-web) section of *Customize Styling*.
+For Mendix 9 and 10, there is no `index.html` file, so you need to create this file first. You can find instructions on how to do this in the [Customizing index.html (Web)](/howto/front-end/customize-styling-new/#custom-web) section of *Customize Styling*.
 {{% /alert %}}
 
 If you use this method, do not forget to set the **SSOLandingPage** constant to a value different than `index.html`. Otherwise, the app will come back to `index.html` which will be redirected again to single sign on, resulting in an endless loop. **SSOLandingPage** specifies a different landing page so the end-user does not end up on `index.html` again after a login attempt. We recommend that you change this constant to `/index3.html` and create an `index3.html` page in your `/theme` folder and copy contents of the original `index.html` (without the added redirect) into it. The authenticated end-user will then land on `index3.html` which will display the content of the app. If the user authentication fails, the user will be directed to the **DefaultLoginPage** instead. 
@@ -252,7 +252,7 @@ The following settings control user provisioning:
 {{% alert color="info" %}}
 These settings are only available in the following versions of the module (depending on which Mendix version you are using)
 
-* v3.1.8/v3.1.9 and above for Mendix versions 9 and 10
+* v3.1.8/v3.1.9 and above for Mendix 9 and 10
 * v2.2.0 and above for Mendix 8
 * v1.16.4 and above for Mendix 7
 {{% /alert %}}
@@ -350,7 +350,7 @@ See [Custom Behavior](#customuserprovisioning), below, for more information.
 
 These settings are only available in the following versions of the module (depending on which Mendix version you are using)
 
-* v3.1.8/v3.1.9 and above for Mendix versions 9 and 10
+* v3.1.8/v3.1.9 and above for Mendix 9 and 10
 * v2.2.0 and above for Mendix 8
 * v1.16.4 and above for Mendix 7
 
@@ -395,7 +395,7 @@ In-session authentication is a process that takes place within a session that wa
 
 In-session authentication at the SAML IdP is only available in the following versions of the module (depending on which Mendix version you are using)
 
-* v3.3.0/v3.3.1 and above for Mendix versions 9 and 10
+* v3.3.0/v3.3.1 and above for Mendix 9 and 10
 * v2.3.0 and above for Mendix 8
 
 Usage of the in-session authentication changes the user roles that apply to the current session. If your app is configured with multiple IDP configurations, the in-session authentication will use the same SAML IDP as the initial (non-anonymous) session. If there is no current session, the end-user can select their IDP. In-session authentication uses the setting `ForceAuthn=true`, which means that the IdP will always authenticate an end-user even if the IdP already has a session for that end-user.
@@ -453,7 +453,7 @@ To use artifact binding, select ARTIFACT_BINDING option for **Response protocol
 
 Using artifact binding for SAML responses at the SAML IdP is only available in the following versions of the module (depending on which Mendix version you are using)
 
-* v3.3.0/v3.3.1 and above for Mendix versions 9 and 10
+* v3.3.0/v3.3.1 and above for Mendix 9 and 10
 * v2.3.0 and above for Mendix 8
 
 #### 4.4.2 Use AssertionConsumerService Concept
@@ -489,7 +489,7 @@ Although the typical use case for requesting attributes is to obtain information
 
 Requesting user attributes at the SAML IdP is only available in the following versions of the module (depending on which Mendix version you are using)
 
-* v3.3.0/v3.3.1 and above for Mendix versions 9 and 10
+* v3.3.0/v3.3.1 and above for Mendix 9 and 10
 * v2.3.0 and above for Mendix 8
 
 ### 4.6 Encryption Settings{#encryption-settings}
@@ -605,9 +605,9 @@ When enabling the log node SSO to show trace messages, you can find detailed inf
 * **"Unable to validate Response, see SAMLRequest overview for detailed response. Error: An error occurred while committing user: p:'johndoe@company.com'/u:'JoHnDoE@CoMpAnY.CoM'"** – All user names passing through the SAML module are converted to lower-case, so make sure all the existing user names and new user names are also converted to lower-case. This is because certain systems are not case-sensitive (for example, Active Directory).
 * **“Could not create a session for the provided user principal.”** – This error can be shown if the IdP configuration does not contain any application attributes for the entity where the user (and user principal) is to be found (and stored).
 
-### 6.2 Troubleshooting an Endless Redirect Loop in Mendix Versions 9 and 10
+### 6.2 Troubleshooting an Endless Redirect Loop in Mendix 9 and 10
 
-When using the [SAML](/appstore/modules/saml/) module for SSO in Mendix versions 9 and 10, you might get stuck in an endless redirect loop. This is because the default value for SameSite cookies is `"Strict"`, and the session cookies cannot be forwarded.
+When using the [SAML](/appstore/modules/saml/) module for SSO in Mendix 9 and 10, you might get stuck in an endless redirect loop. This is because the default value for SameSite cookies is `"Strict"`, and the session cookies cannot be forwarded.
 
 To avoid this issue, make sure your IdP (identity provider) and your app are in the same domain, and thus on the same site. For example, if your app is on `app.domain.com` and you open the deep link `app.domain.com/link/test`, then you are redirected to your IdP to sign in on `idp.domain.com/SSO`. After you sign in successfully, you are sent back to `app.domain.com/SSO/assertion`. Finally, you are forwarded to `app.domain.com/link/test`. Since your requests always stay on the same site, the cookie can be forwarded each time.
 

content/en/docs/appstore/partner-solutions/apd/release-notes/index.md

@@ -522,7 +522,7 @@ The statistics tool now gathers statistics over different time periods:
 * The JDBC query and explain-plan functionality for the built-in database work only after starting the database viewer in the Mendix Modeler from the advanced menu of the console.
 * The performance tool can run out of memory when recording. The protection options advised for the performance tool still expect 1 GB of available memory, so for small implementations, the protection options should be stricter.
 * When the Before Shutdown microflow is not configured, and some tools are running, the shutdown of the Mendix application can hang for about a minute.
-* For Mendix versions 5 and above, the microflow names are taken from the action caption. So if the action caption is changed in the Mendix Modeler, the Call Microflow action in the performance tool does not drill down. In addition, the caption only contains the microflow name, not the module name, so if multiple microflows exist with the same name but they are in different modules, the performance tool cannot pick the right one.
+* For Mendix 5 and above, the microflow names are taken from the action caption. So if the action caption is changed in the Mendix Modeler, the Call Microflow action in the performance tool does not drill down. In addition, the caption only contains the microflow name, not the module name, so if multiple microflows exist with the same name but they are in different modules, the performance tool cannot pick the right one.
 * On load-balanced environments without sticky sessions, the APM tool is randomly connected to instances, and this does not work! For 1.6.1, you need access to specific servers to use the APM tool.
 * ChartJS sometimes is not responsive enough, and a refresh of the page might be needed.
 * When the runtime stops and the APM console is open, errors appear due to the auto-refresh of grids and ChartJS.
@@ -667,7 +667,7 @@ Per module it can be configured to remove data after a certain amount of days. D
 This version supports Mendix 6.2.0 and above only. Also only on java 8.
 
 * Statistics Tool gave a parse error on logout in the logging. Not really visible for users, but would create a trap if trapping on warnings. Now fixed, so logout is also in the statistics.
-* During installation there were sometimes errors on startup, because Mendix generates different parameter names in java in different Mendix versions. Sometimes 'FileName' was allowed, sometimes not and then it becomes 'FileNameParameter1' in java. The parameter names with 'FileName' have changed to 'FileNameParameter' in 3 import java actions to prevent these installation errors. Also parameter 'MicroflowName' in java action ExecuteMicroflowAsync is changed into 'MicroflowNameParameter'.
+* During installation there were sometimes errors on startup, because Mendix generates different parameter names in Java in different Mendix versions. Sometimes 'FileName' was allowed, sometimes not and then it becomes 'FileNameParameter1' in java. The parameter names with 'FileName' have changed to 'FileNameParameter' in 3 import java actions to prevent these installation errors. Also parameter 'MicroflowName' in java action ExecuteMicroflowAsync is changed into 'MicroflowNameParameter'.
 * A grid in the Mendix 6 version of the performance tool details was changed from to be able to sort on loop iterations.
 * When choosing sample data during install the explain plan sample data for MySQL is now also added.
 

content/en/docs/appstore/partner-solutions/ats/release-notes/release-notes.md

@@ -715,7 +715,7 @@ Mendix applications that are based on [Mendix 7.22.2](/releasenotes/studio-pro/7
 
 ### Fixes
 
-* We fixed an issue where a click was not be recorded on some buttons in Mendix versions 7.18+.
+* We fixed an issue where a click was not be recorded on some buttons in Mendix 7.18 and above.
 * In rare cases under a very high testing load, jobs got stuck in the queued status. We have added additional checks to prevent this from happening.
 * In some scenarios, the **Recordings** tab was not available in ATS. We addressed this issue by changing the way recordings are retrieved.
 * We fixed a UI issue where double-clicking on an item in an ATS repository showed a generic error message.
@@ -822,7 +822,7 @@ Mendix applications based on Mendix 7.16 can now be tested and recorded with ATS
 
 ### Limitations
 
-* For Mendix versions 7.13 and above it is likely that test will not properly wait for the execution of asynchronous microflows. As a temporary workaround please manually add the **Sleep** step with a proper duration after triggering asynchronous microflows.
+* For Mendix 7.13 and above, it is likely that test will not properly wait for the execution of asynchronous microflows. As a temporary workaround please manually add the **Sleep** step with a proper duration after triggering asynchronous microflows.
 * We did not explicitly test the impact of nanoflows on ATS, but we have not yet received any issue reports related to them
 
 ## 2.8.0
@@ -1000,7 +1000,7 @@ You can now run ATS tests against Internet Explorer 11. We are happy to announce
 
 ### Mendix 7.11 and 7.12
 
-Mendix applications built on Mendix versions 7.11 or 7.12 can now be tested and recorded with ATS. We have not explicitly tested the impact of nanoflows (the newest feature added in Mendix 7.12) on ATS, but we do not expect any significant problems here.
+Mendix applications built on Mendix 7.11 or 7.12 can now be tested and recorded with ATS. We have not explicitly tested the impact of nanoflows (the newest feature added in Mendix 7.12) on ATS, but we do not expect any significant problems here.
 
 ### Improvements
 

content/en/docs/appstore/partner-solutions/ats/rg-ats/v2/rg-two-recorder/_index.md

@@ -43,7 +43,7 @@ In most cases for the Desktop Recorder, no additional administrative privileges
 
 These are the current limitations on recording:
 
-* Clicking the data grid search button is only recorded on Mendix versions higher than 5.19
+* Clicking the data grid search button is only recorded on Mendix 5.20 and above
 * Multi-selection in grids via <kbd>Ctrl</kbd> + click is not recorded
 * Switching between browser tabs/windows is not recorded
 * Assertions are not recorded