Proofreading changes from Feddo

Author: MarkvanMents

content/developerportal/deploy/deploying-to-mindsphere.md

@@ -63,7 +63,7 @@ This is the recommended approach if you are building a new application, as it wi
 If you have an existing app which was not based on the MindSphere starter app, you can import the required customization. There are three modules which you need are:
 
 * MindSphere SSO from the Mendix App Store here: [Siemens MindSphere SSO](https://appstore.home.mendix.com/link/app/108805/).
-* MindSphere OS Bar Connector (MindSphere_UI_Resources) from the Mendix App Store here: [Siemens MindSphere OS Bar Connector](https://appstore.home.mendix.com/link/app/108804/).
+* MindSphere OS Bar Connector from the Mendix App Store here: [Siemens MindSphere OS Bar Connector](https://appstore.home.mendix.com/link/app/108804/).
 * MindSphere Theme Pack (MindSphere_UI_Resources) from the Mendix App Store here: [Siemens MindSphere Theme Pack](https://appstore.home.mendix.com/link/app/108803/).
 
 ### 2.2 Single Sign-On (MindSphereSingleSignOn){#mssso}
@@ -98,15 +98,15 @@ This is the base URL for all requests to MindSphere APIs. For example, the URL f
 
 This is the URL where the public key can be found to enable token validation during the login process. For example, the URL for MindSphere on AWS PROD is `https://core.piam.eu1.mindsphere.io/token_keys`.
 
-#### 2.2.2 Microflows
+#### 2.2.2 Microflows{#microflows}
 
 The MindSphereSingleSignOn module also provides three microflows which are used to support SSO within MindSphere and allow the user’s **tenant** and **email** to be obtained for use within the app.
 
 ![Folder structure showing microflows in the MindSphereSingleSignOn module](attachments/deploying-to-mindsphere/image3.png)
 
 **RegisterSingleSignOn**
 
-This microflow must be added to the *Runtime* tab of the *Project > Settings* dialog, accessed through the *Project Explorer*. It needs to be selected as the *After startup* microflow or added as a sub-microflow to an existing after startup microflow.
+This microflow must be added as the *After startup* microflow or added as a sub-microflow to an existing after startup microflow. You can do this on the *Runtime* tab of the *Project > Settings* dialog, accessed through the *Project Explorer*.
 
 ![Project settings dialog](attachments/deploying-to-mindsphere/image4.png)
 

content/howto/mindsphere/mindsphere-example-app.md

@@ -6,7 +6,7 @@ tags: ["Siemens", "MindSphere", "Example", "Asset Management", "Time Series", "R
 
 ## 1 Introduction
 
-You can write Mendix apps which analyze data held in MindSphere, the open, cloud-based, IoT operating system from Siemens. To help you build your app, the [Siemens MindSphere Pump Asset Example](https://appstore.home.mendix.com/link/app/108810/) app is available in the Mendix App Store and can be used as the starting point for a new Mendix app.
+You can create Mendix apps which analyze data held in MindSphere, the open, cloud-based, IoT operating system from Siemens. To help you build your app, the [Siemens MindSphere Pump Asset Example](https://appstore.home.mendix.com/link/app/108810/) app is available in the Mendix App Store and can be used as the starting point for a new Mendix app.
 
 This documentation provides more explanation of the MindSphere example app. Please note that this app is not production-ready. It is designed as an example of how you might begin to build a Mendix/MindSphere app.
 

content/refguide/mindsphere/mindsphere-development-considerations.md

@@ -70,7 +70,7 @@ For a MindSphere app to be multi-tenant, each user can only see the data from a
 
 ### 3.1 Control through MindSphere APIs
 
-The Authorization HTTP Header (see DS_MindSphereAccessToken in section 2.2.2, Microflows) which is passed for every MindSphere API call ensures that the user can only obtain data which is authorized to them via their tenant.
+The Authorization HTTP Header (see DS_MindSphereAccessToken in the [Microflows](/developerportal/deploy/deploying-to-mindsphere#microflows) section of *Siemens Mindsphere – deployment*) which is passed for every MindSphere API call ensures that the user can only obtain data which is authorized to them via their tenant.
 
 ### 3.2 Control within a Mendix app
 
@@ -94,7 +94,7 @@ It is not necessary to put an access rule on every entity within the domain mode
 
 To make your Mendix app multi-tenant, do the following:
 
-1.  Make all *permanent* entities which have a **TenantId** attribute a specialization of the MindSphereSingleSignOn.TenantObject entity.  
+1.  Make all *persistent* entities which have a **TenantId** attribute a specialization of the MindSphereSingleSignOn.TenantObject entity.  
     This ensures that every object is associated with the Tenant object of the user who creates it.
 2.  Every action on this object must have the following XPath constraint: