Proofread

Author: adam-dupaski

content/en/docs/appstore/connectors/sap/use-sap-model-creator.md

@@ -72,7 +72,7 @@ Before starting this how-to, make sure you have completed the following prerequi
 * Obtain authentication credentials, if needed, for the SAP Catalog Service or SAP back-end system you wish to use
 
 {{% alert color="warning" %}}
-The Model Creator for SAP Integrations will produce a module which is in Mendix version 8.18.10. To use the module you will have to create your app in, or upgrade your app to, Mendix version 8.18.10 or above.
+The Model Creator for SAP Integrations will produce a module which is in Mendix 8.18.10. To use the module you will have to create your app in, or upgrade your app to, Mendix 8.18.10 or above.
 {{% /alert %}}
 
 ## 3 Generating an OData Data Model

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

@@ -14,9 +14,9 @@ The [Forgot Password](https://marketplace.mendix.com/link/component/1296/) modul
 This module allows the end-user to enter their email address, and an email will be sent with a confirmation link. The end-user then opens the link and gets the option to reset their password in both scenarios (Sign up and Forgot password). In the sign up case, the end-user will also be asked to provide their name. For version 5.3.0 of the module and above, you can specify different templates to be sent, depending on the language in which the end-user is seeing the app.
 
 {{% alert color="info" %}}
-Versions of the Forgot Password module below 4.1.0 (Mendix version 8) and 5.1.0 (Mendix version 9 and above) have a dependency on the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. We recommend that 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 9 and above) have a dependency on the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. We recommend that you upgrade to a later version using the instructions in [Migrate from Email Module with Templates to Email Connector](#migrate-email), below.
 
-There is no alternative version for use with Mendix version 7.
+There is no alternative version for use with Mendix 7.
 {{% /alert %}}
 
 There are three versions of the Forgot Password module, depending on whether you are using Mendix Studio Pro version 7, 8, or 9 and above — see the table, below. These all work in the same way, and require the same dependencies specified below.
@@ -29,7 +29,7 @@ There are three versions of the Forgot Password module, depending on whether you
 
 ¹ If you are using Mendix version 9.20.0 or above, you must use version 5.1.0 or above of the Forgot Password module.
 
-If you already use the Forgot Password module in your Mendix version 8 app, you can find instructions on how to upgrade in [Upgrading from Mendix Version 8 to Mendix Version 9](#upgrade8-9), at the end of this page.
+If you already use the Forgot Password module in your Mendix 8 app, you can find instructions on how to upgrade in [Upgrading from Mendix 8 to Mendix 9](#upgrade8-9), at the end of this page.
 
 ### 1.1 Dependencies {#dependencies}
 
@@ -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 version 8) and 5.1.0 (Mendix version 9 and above), and those for Mendix version 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 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.
 
 ## 2 Installing the Forgot Password Module{#installing}
 
@@ -85,7 +85,7 @@ In these instructions, it is assumed that your main module is `MyFirstModule`. I
             * `System.User`
             * `MyFirstModule.User`
 
-            ³ `Email_Connector` permissions are needed if you are using version 4.1.0 or above (Mendix version 8) or version 5.1.0 or above (Mendix version 9 and above). `EmailTemplate` permissions are only needed if using a version which uses the deprecated Email Module with Templates module.
+            ³ `Email_Connector` permissions are needed if you are using version 4.1.0 or above (Mendix 8) or version 5.1.0 or above (Mendix version 9 and above). `EmailTemplate` permissions are only needed if using a version which uses the deprecated Email Module with Templates module.
 
     * In the **Anonymous users** tab, set **Allow Anonymous users** to *Yes*
 1. Open [Navigation](/refguide/navigation/) and do the following:
@@ -129,11 +129,11 @@ To disable the signup functionality and use the Forgot Password module only for
     You can now reset your password.
         {{< figure src="/attachments/appstore/modules/forgot-password/reset-password-page.png" >}}
 
-## 4 Upgrading from Mendix Version 8 to Mendix Version 9 {#upgrade8-9}
+## 4 Upgrading from Mendix 8 to Mendix 9 {#upgrade8-9}
 
 To convert from Mendix 8.18.x to Mendix 9.12.5 or above, follow the steps below from within Studio Pro:
 
-1. Upgrade all the [dependencies](#dependencies) of the Forgot Password module to the latest version compatible with Mendix version 8.
+1. Upgrade all the [dependencies](#dependencies) of the Forgot Password module to the latest version compatible with Mendix 8.
 1. Open your app in Mendix 9.12.5 or above and allow it to be upgraded.
 1. Import the [Forgot Password](https://marketplace.mendix.com/link/component/1296/) module into your app.
 
@@ -147,17 +147,17 @@ You have now successfully upgraded the Forgot Password Module to work with Mendi
 
 ## 5 Migrating from Email Module with Templates to Email Connector{#migrate-email}
 
-Versions 4.1.0 (Mendix version 8) and 5.1.0 (Mendix version 9 and above) and above of the Forgot Password module use the [Email Connector](/appstore/connectors/email-connector/) module rather than the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. There is a community-supported [Email Connector Migration Utility](https://marketplace.mendix.com/link/component/205008) to help with your upgrade to these versions.
+Versions 4.1.0 (Mendix 8) and 5.1.0 (Mendix version 9 and above) and above of the Forgot Password module use the [Email Connector](/appstore/connectors/email-connector/) module rather than the deprecated [Email Module with Templates](https://marketplace.mendix.com/link/component/259/) module. There is a community-supported [Email Connector Migration Utility](https://marketplace.mendix.com/link/component/205008) to help with your upgrade to these versions.
 
 {{% alert color="warning" %}}
 Use these instructions before you upgrade the Forgot Password module. The point at which you should get the new version is included in the steps below.
 {{% /alert %}}
 
 ### 5.1 Dependencies
 
-* An app using Mendix version 8 or above.
+* An app using Mendix 8 or above.
 
-    The Forgot Password module versions compatible with Mendix version 7 (3.xx) continue to use the Email Module with Templates module as the Email Connector module is not compatible with Mendix version 7.
+    The Forgot Password module versions compatible with Mendix 7 (3.xx) continue to use the Email Module with Templates module as the Email Connector module is not compatible with Mendix 7.
 * The email templates must be set up as follows:
 
     * The reset password template must contain *_Reset* in the template name
@@ -192,7 +192,7 @@ Follow the [Migration Steps](https://github.com/mendixlabs/EmailConnectorMigrati
 
 #### 5.2.4 Actions After the Migration
 
-1. Import the latest version of the Forgot Password module (v4.1.0 or above for Mendix version 8, or v5.1.0 or above for Mendix version 9 and above). This will have the Email Connector module as a dependency.
+1. Import the latest version of the Forgot Password module (v4.1.0 or above for Mendix 8, or v5.1.0 or above for Mendix version 9 and above). This will have the Email Connector module as a dependency.
 1. Delete the Email Module with Templates module.
 1. Delete the Email Connector Migration Utility module.
 1. Remove the Administrator user roles for EmailTemplate and MigrationUtility.

content/en/docs/appstore/modules/oidc-provider.md

@@ -405,7 +405,7 @@ In versions of OIDC Provider below 1.1.0, the following values are not included
 ### 6.1 Infinite Loop of Redirects
 
 The OIDC provider module sets a cookie as a means to persist the session in the user’s browser. If the cookie is not properly set, this may lead to problems. For example, when the OIDC Provider module is used to build an IAM Broker, no session is established and the broker may initiate a new session at the upstream IdP, which results in an ‘infinite loop’ of redirects via the user’s browser.
-To ensure the cookie is properly set, the runtime setting com.mendix.core.SameSiteCookies must have value None. See [Environment Details](/developerportal/deploy/environments-details/#samesite) for more information how to set the correct value for SameSite runtime setting. Note that the default value for this setting changed in [Mendix version 8.11](/releasenotes/studio-pro/8.11/).
+To ensure the cookie is properly set, the runtime setting com.mendix.core.SameSiteCookies must have value None. See [Environment Details](/developerportal/deploy/environments-details/#samesite) for more information how to set the correct value for SameSite runtime setting. Note that the default value for this setting changed in [Mendix 8.11](/releasenotes/studio-pro/8.11/).
 
 ## 7 About Authorization{#about-authorization}
 

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

@@ -128,7 +128,7 @@ Once the Mx Model Reflection module has been imported into your app, you need to
 
 If you already have the [OpenIDConnect Single Sign-on (OIDC, OAuth2, SSO)](https://marketplace.mendix.com/link/component/117529) (community edition) in your module, you can migrate to this, platform supported, version by following the instruction below.
 
-#### 3.2.1 Upgrading from Mendix Version 8 to Mendix Version 9
+#### 3.2.1 Upgrading from Mendix 8 to Mendix 9
 
 To migrate from Mendix 8.18.x to Mendix 9.8.1 or above, follow the steps below:
 

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

@@ -36,7 +36,7 @@ The SAML SSO module supports the following [SAML 2.0](https://docs.oasis-open.or
 * Web browser SSO profile using one of the following bindings
     * HTTP redirect, 
     * HTTP POST bindings
-    * Artifact binding for SAML responses (Mendix version 8 and above)
+    * Artifact binding for SAML responses (Mendix 8 and above)
 * Single Logout profile
 
 The Mendix SAML SSO supports usage of SAML metadata in the following way:
@@ -114,7 +114,7 @@ There are different versions of the SAML module, depending on which version of M
 1. In Mendix Marketplace, search for the [SAML module](https://marketplace.mendix.com/link/component/1174/).
 2. In the **Documentation** tab, the *compatibility guidance* section indicates the latest recommended version for your LTS/MTS Mendix release. These guidelines are updated with each release of the SAML module, and you should refer to them to choose the version of the module that is compatible with your app. For additional information, some general considerations are listed below:
 
-    * For Mendix version 7 and version 8, you should use the latest published versions in the **1.x** and **2.x** range, respectively, unless otherwise indicated in the **Documentation** tab. 
+    * For Mendix 7 and 8, you should use the latest published versions in the **1.x** and **2.x** range, respectively, unless otherwise indicated in the **Documentation** tab. 
     * For Mendix version 9, there are odd- and even-numbered patch releases that contain the same changes and require the same Mendix version, but differ based on the version of Atlas UI that your app uses: 
 
         * The even-numbered releases (for example, 3.6.2) are intended for apps that use the 2.0 version of Atlas UI, that is, apps which were originally built on a version of Mendix below 9.0.0, and then upgraded to Mendix version 9.
@@ -236,7 +236,7 @@ The following settings control user provisioning:
 * **Uses InCommon Federation Standard** – IdPs that use the InCommon standard often do not specify the assertion attributes. When following the InCommon standard, a fixed set of assertion attributes will be available to choose from later.
 * **Identifying Assertion** (aka "Principal Key") – Specifies which of the assertion attributes identifies the user name.
 
-    {{% alert color="info" %}}In Mendix version 7,  all user names passing through the SAML module are converted to lower-case before login and creation. We strongly advise you to convert all existing and new user names to lower-case as well.{{% /alert %}}
+    {{% alert color="info" %}}In Mendix 7,  all user names passing through the SAML module are converted to lower-case before login and creation. We strongly advise you to convert all existing and new user names to lower-case as well.{{% /alert %}}
 
 * **User Entity** – The Mendix entity in which you will store and look up the user account. Most often something like `Administration.Account`.
 * **Attribute On** – Determines the attribute on which you want to do the lookup. This attribute will be compared against the passed **Identifying Assertion** (see above).
@@ -253,8 +253,8 @@ The following settings control user provisioning:
 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
-* v2.2.0 and above for Mendix version 8
-* v1.16.4 and above for Mendix version 7
+* v2.2.0 and above for Mendix 8
+* v1.16.4 and above for Mendix 7
 {{% /alert %}}
 
 * **Use custom logic for user provisioning** and **Use custom after sign-in logic**
@@ -322,7 +322,7 @@ You also need to define where the user account will be stored within your app. P
 * **User Entity** – The Mendix entity in which you will store and look up the user account. Most often something like `Administration.Account`.
 * **Attribute On** – Determines the attribute on which you want to do the lookup. This attribute will be compared against the passed **Identifying Assertion** (see above).
 
-In Mendix version 7, all user names passing through the SAML module are converted to lower-case before login and creation. We strongly advise you to convert all existing and new user names to lower-case as well.
+In Mendix 7, all user names passing through the SAML module are converted to lower-case before login and creation. We strongly advise you to convert all existing and new user names to lower-case as well.
 
 ### 4.2 Provisioning
 
@@ -351,8 +351,8 @@ 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
-* v2.2.0 and above for Mendix version 8
-* v1.16.4 and above for Mendix version 7
+* v2.2.0 and above for Mendix 8
+* v1.16.4 and above for Mendix 7
 
 #### 4.2.4 Just in Time Provisioning
 
@@ -396,7 +396,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
-* v2.3.0 and above for Mendix version 8
+* 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.
 
@@ -454,7 +454,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
-* v2.3.0 and above for Mendix version 8
+* v2.3.0 and above for Mendix 8
 
 #### 4.4.2 Use AssertionConsumerService Concept
 
@@ -490,7 +490,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
-* v2.3.0 and above for Mendix version 8
+* v2.3.0 and above for Mendix 8
 
 ### 4.6 Encryption Settings{#encryption-settings}
 

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

@@ -233,7 +233,7 @@ This release is identical to 1.11.1, but it is for Mendix 7.0.2 and above.
 ### Other Fixes
 
 * When defining a **Create trap message** action in the trigger configuration, the trap was not created and linked to the triggered event. Both issues are fixed.
-* If the log tool is used, there is now protection in place to configure the 1.11**Max messages to store**. By default, this is set to 100,000 records. This protection is in place to protect from overloading the database with records. **Fallback level** protection is now also in place. When the log tool notices issues like too much data is being processed, the **Fallback level** will set the logging to **INFO** for all log levels. In exceptional cases, the application generates too much INFO logging, which consumes heap memory and eventually causes the application to run out of memory. In this release, this behaviour still consumes heap memory, but there is a fix in place to prevent the application from running out of heap memory. The following fix in Mendix version 7.7.1 is also needed: We improved the memory management of persistable entities that have been committed to the persistent storage.
+* If the log tool is used, there is now protection in place to configure the 1.11**Max messages to store**. By default, this is set to 100,000 records. This protection is in place to protect from overloading the database with records. **Fallback level** protection is now also in place. When the log tool notices issues like too much data is being processed, the **Fallback level** will set the logging to **INFO** for all log levels. In exceptional cases, the application generates too much INFO logging, which consumes heap memory and eventually causes the application to run out of memory. In this release, this behaviour still consumes heap memory, but there is a fix in place to prevent the application from running out of heap memory. The following fix in Mendix 7.7.1 is also needed: We improved the memory management of persistable entities that have been committed to the persistent storage.
 
 ## 1.12.0