Proofread end-user and typos

Author: MarkvanMents

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

@@ -56,7 +56,7 @@ You can configure the module for certain actions in your app. All the configurat
 
 * **Project** tab     
     * **Submit successful image url** – changes the image to show on the last successfully submitted page
-    * **Allow screenshots** – controls whether the end user can take a screenshot or not
+    * **Allow screenshots** – controls whether the end-user can take a screenshot or not
 * **Advanced** tab
     * **App ID** – the unique identifier of your app, which you can find in your app’s [General Settings](/developerportal/collaborate/general-settings/) in the Developer Portal
 

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

@@ -164,7 +164,7 @@ You may have to add the *Anonymous* user role if it does not exist already.
 
 ### 4.2 Allowing Anonymous Users
 
-The OIDC module supports multiple OIDC/OAuth-compatible IdPs. To allow your end users to choose from a number of different IdPs, or to have the option to log back into the app after they have logged out, you will need to give them access to the app before they have signed in to the app. Therefore, you need to give anonymous users access to your app.
+The OIDC module supports multiple OIDC/OAuth-compatible IdPs. To allow your end-users to choose from a number of different IdPs, or to have the option to log back into the app after they have logged out, you will need to give them access to the app before they have signed in to the app. Therefore, you need to give anonymous users access to your app.
 
 In the **Anonymous** tab of the app security settings, do the following:
 
@@ -177,7 +177,7 @@ In the **Anonymous** tab of the app security settings, do the following:
 
 The OIDC SSO module works without a specified sign-in page. Therefore, in the navigation section of your app, set **Sign-in page** (in the **Authentication** section) to *(none)*.
 
-To allow your end users to choose from a number of different IdPs, or to have the option to log back into the app after they have logged out, set a **Role-based home page** for role **Anonymous** to **OIDC.Login_Web_Button**. See [Role-Based Home Pages](/refguide/navigation/#role-based) in *Navigation* for more information.
+To allow your end-users to choose from a number of different IdPs, or to have the option to log back into the app after they have logged out, set a **Role-based home page** for role **Anonymous** to **OIDC.Login_Web_Button**. See [Role-Based Home Pages](/refguide/navigation/#role-based) in *Navigation* for more information.
 
 In addition, administrators will need to have access to configure OIDC and also manage end-users. You can do this by including the pages `Administration.Account_Overview` and `OIDC.OIDC_Client_Overview` into the app navigation, or a separate administration page.
 

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

@@ -53,7 +53,7 @@ For encryption of SAML messages the following options are supported:
 
 For easy configurability, the SAML module offers the following:
 
-* a SAML administration screen that allows you to configure one or multiple SAML IdP’s. IdP discovery is supported by an endpoint that returns a page listing all configured IdPs so the end user can select the IdP where they have an account.
+* a SAML administration screen that allows you to configure one or multiple SAML IdP’s. IdP discovery is supported by an endpoint that returns a page listing all configured IdPs so the end-user can select the IdP where they have an account.
 * various options as per the SAML 2.0 specification and as indicated on this page
 
 #### 1.2.2 Other Features
@@ -371,7 +371,7 @@ By default, the module does not allow for unsolicited requests. That means that
 
 #### 4.3.2 Enable Force Authentication
 
-Checking this box will force the SAML IdP  to (re)authenticate end-users, even if they are already signed in at the SAML IdP. Only check this box if stronger security for your app is more important than the convenience of having single sign-on for your end users.
+Checking this box will force the SAML IdP  to (re)authenticate end-users, even if they are already signed in at the SAML IdP. Only check this box if stronger security for your app is more important than the convenience of having single sign-on for your end-users.
 
 #### 4.3.3 Enable Mobile Authentication Token
 
@@ -401,7 +401,7 @@ In-session authentication at the SAML IdP is only available in the following ver
 * v3.3.0/v3.3.1 and above for Mendix version 9
 * v2.3.0 and above for Mendix version 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.
+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.
 
 This flow can be initiated by using the URL `https://{app-url}/sso/login?action=verify`
 
@@ -487,7 +487,7 @@ If you need to change your identity provider metadata you can find more informat
 
 In the **Attribute Consuming Service** tab, you can configure your app using the SAML protocol to request specific attributes, such as Date of Birth or Gender, from the SAML IdP. Your SAML IdP documentation will tell you what attributes can be requested. In the request you can also indicate whether you consider the attribute as mandatory or optional for your app’s logic.
 
-You can set up two sets of attributes, by adding new attributes, editing existing attributes, or removing selected attributes. These will be provided at different times. Those listed under **I want to request attribute(s) at my IDP during initial login** will be returned when the end user initially signs in. Those listed under **I want to request attribute(s) at my IDP during in-session login** will be returned during [In-session Authentication](#in-session).
+You can set up two sets of attributes, by adding new attributes, editing existing attributes, or removing selected attributes. These will be provided at different times. Those listed under **I want to request attribute(s) at my IDP during initial login** will be returned when the end-user initially signs in. Those listed under **I want to request attribute(s) at my IDP during in-session login** will be returned during [In-session Authentication](#in-session).
 Although the typical use case for requesting attributes is to obtain information about the user, you can request an attribute with a specific value. In this case, you can configure the optional **Attribute value that must be returned**.
 
 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)
@@ -574,12 +574,12 @@ The following diagram gives an overview of all endpoints that the SAML SSO modul
 
 {{< figure src="/attachments/appstore/modules/saml/saml-endpoints.png">}}
 
-End users can access your app through the following endpoints when using the SAML SSO module:
+End-users can access your app through the following endpoints when using the SAML SSO module:
 
 * **/SSO/discovery** – If there are multiple active IdP configurations and discovery is enabled, this page can give a list of all the IdP configuration. It also allows the user to click the correct URL to sign in.
 * **/SSO/login/[IdP Alias]** or **/SSO/login?_idp_id=[IdP_Alias]&action=verify&on={contextname}** – For logging using a specific IdP, you have to open either of these two URLs and pass the IdP alias as a parameter in the URL.
     The (optional) parameters for this end point are as follows:
-    * **idp_id** – this indicates which idp will be used to sign the end user in if you connect your app using multiple SAML IdPs
+    * **idp_id** – this indicates which idp will be used to sign the end-user in if you connect your app using multiple SAML IdPs
     * **action=verify** – indicates that in-session authentication is being requested (see [In-session Authentication](#in-session) for more information)
     * **on={contextname}** – this gives context to the initiation of in-session authentication,  (see [In-session Authentication](#in-session) for more information)
 * **/SSO/login/SSO/** or **/SSO/login/SSO?action=verify&on={contextname}** – If you have only one active IdP, opening these URLs will automatically try to log you in using the active IdP. In the case of multiple active IdPs and discovery enabled, the user will be redirected to the discovery page.  If discovery is not allowed, the user will receive an error message. The optional parameters work as described above.

content/en/docs/developerportal/collaborate/general-settings/_index.md

@@ -57,7 +57,7 @@ Only users with the **App Settings** permission can change the description of th
 
 On the **Access Management** tab, you can manage and invite app users. App users are end-users who can access the deployed app on specific environments. They can use and test your deployed app, and provide feedback.
 
-To manage users or invite users for an app deployed on a specific environment, click **Mange Users** or **Invite Users** for that environment. For more information, see the [Mange Users](#manage-users) and [Invite Users](#invite-users) section below.
+To manage users or invite users for an app deployed on a specific environment, click **Mange Users** or **Invite Users** for that environment. For more information, see the [Manage Users](#manage-users) and [Invite Users](#invite-users) section below.
 
 {{% alert color="info" %}}
 You can also manage app users from Studio, by clicking **Manage Users** on the **Settings > Roles and Permissions** page within Studio.

content/en/docs/developerportal/deploy/mendix-cloud-deploy/mendix-sso.md

@@ -164,7 +164,7 @@ To enable Mendix SSO in your app, follow these steps:
     2. Go to the **theme/web** folder (for Mendix versions below 9.0.0 this will be 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
+        * `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
         * `login-with-mendixsso-automatically.html` – automatically initiates the single sign-on process without needing to click a button
 
 Your app is now configured to use Mendix Single Sign-on when it is deployed to the Cloud.

content/en/docs/partners/sap/sap-destination-service.md

@@ -172,7 +172,7 @@ You should catch any exceptions when using the **Get Destination** to access the
 
 {{< figure src="/attachments/partners/sap/sap-destination-service/get-destination-error-flow.png" >}}
 
-If your access token has expired, you will get a return code of **401**. The access token cannot be refreshed automatically and the end user will be signed out and will need to sign in again to get a new token.
+If your access token has expired, you will get a return code of **401**. The access token cannot be refreshed automatically and the end-user will be signed out and will need to sign in again to get a new token.
 
 If the **Get Destination** action returns a different error, or signing in again does not solve the issue, then continue testing for other possible causes.
 

content/en/docs/partners/siemens/mindsphere/_index.md

@@ -27,7 +27,7 @@ The MindSphere IIoT for Makers is easy to add to your app but has the following
 
 * You cannot make your app multi-tenant – see [Multi-tenancy](/partners/siemens/mindsphere-development-considerations/#multitenancy) in *MindSphere Development Considerations* for more information on multi-tenancy
 * Your app cannot be deployed to the MindSphere platform and cannot leverage the MindSphere Application Lifecycle including the deployment to third parties
-* End users cannot use MindSphere credentials to sign in to your app, you must handle app security within your app
+* End-users cannot use MindSphere credentials to sign in to your app, you must handle app security within your app
 * It is not possible to use Sub- / Cross Tenancy
 
 For full information on using the MindSphere IIoT for Makers see [MindSphere IIoT for Makers](/partners/siemens/mindsphere-app-service/).

content/en/docs/partners/siemens/mindsphere/mindsphere-app-service.md

@@ -29,7 +29,7 @@ MindSphere IIoT for Makers is easy to add to your app but has the following limi
 
 * You cannot make your app multi-tenant – see [Multi-tenancy](/partners/siemens/mindsphere-development-considerations/#multitenancy) in *MindSphere Development Considerations* for more information on multi-tenancy
 * Your app cannot be deployed to the MindSphere platform and cannot be added to the MindSphere Developer Cockpit
-* End users cannot use MindSphere credentials to sign in to your app, so MindSphere does not know anything about individual app end users — you must design your app to handle any required security for each end user
+* End-users cannot use MindSphere credentials to sign in to your app, so MindSphere does not know anything about individual app end-users — you must design your app to handle any required security for each end-user
 
 MindSphere IIoT for Makers can be used in any Mendix app, for example an app which is based on the Mendix **Blank App**. However, it is not suitable for apps which are designed to be deployed to MindSphere, such as the **Siemens MindSphere Starter Application**, the **Siemens MindSphere Pump Asset Example**, or an app which is using the **Siemens MindSphere SSO** module.