Update infrastructure-intro.md

tech/docs/infrastructure/infrastructure-intro.md

@@ -16,15 +16,15 @@ For the development of **First project iteration cycle**, we defined the followi
 
 During the iteration, the following components have been deployed:
 
-- on WeTransform cloud infrastructure, a k8s deployment of the hale connect stack as been installed and configured. This instance can provide user management and has been integrated with the GitHub repository <https://github.com/soilwise-he/Soilwise-credentials>. The stack provides [Transformation](../technical_components/transformation.md), [Metadata Generation](../technical_components/metadata_augmentation.md#automatic-metadata-generation) and [Validation](../technical_components/metadata_validation.md) capabilities.
+- On WeTransform cloud infrastructure, a k8s deployment of the hale connect stack as been installed and configured. This instance can provide user management and has been integrated with the GitHub repository <https://github.com/soilwise-he/Soilwise-credentials>. The stack provides [Transformation](../technical_components/transformation.md), [Metadata Generation](../technical_components/metadata_augmentation.md#automatic-metadata-generation) and [Validation](../technical_components/metadata_validation.md) capabilities.
 - The Soilwise infrastructure uses components provided by Github. Github components are used to
   - Administer and assign to roles the different Soilwise users
   - Register, prioritise and assign tasks
   - Store source code of software artifacts
   - Author documentation
   - Run CI/CD pipelines
   - Collect user feedback
-- on infrastructure provided by Wageningen University
+- On infrastructure provided by Wageningen University
   - A PostGres database on the PostGres cluster
   - A number of repositories at the university Gitlab instance, including CI/CD pipelines to run metadata harvesters
   - A range of services deployed on the univerity k8s cluster, with their configuration stored on Gitlab. Container images are stored on the university Harbor repository
@@ -33,4 +33,8 @@ During the iteration, the following components have been deployed:
 
 ## Future work - Iteration 2
 
-The main objective of iteration 2 is to integrate the different components that have been deployed so far, as well as additional ones. The integrations will, whereever feasible, build on open APIs. We intend to retain the distributed architecture, though the staging and production environments may switch to an overall kubernetes-based orchestration mode if it is deemed necessary and advantageous at that point in time.
+The main objective of iteration 2 is to reorganise the orchestration of the different components, so all components can be centrally accessed and monitored.  
+
+The integrations will, whereever feasible, build on API's which are standardised by W3C, OGC or de facto, such as Open API or GraphQL. 
+
+The intention is to set up a distributed architecture, with the staging and production environment to switch to an overall kubernetes-based orchestration mode if it is deemed necessary and advantageous at that point in time.