diff --git a/cloud-platform.md b/cloud-platform.md
index b3d9097d397c1690680e002b1655336f92a8200d..5692e0eb79a82f37f44b70db1f55f439efb07220 100644
--- a/cloud-platform.md
+++ b/cloud-platform.md
@@ -14,23 +14,24 @@ The upcoming Helmholtz Cloud will initially consist of approximately 20 of 25 se
 
 #### How can I access it? And when?
 It is the purpose of HIFIS to allow a common, harmonized access to Helmholtz Cloud services via 
-a single portal -- the Cloud Access Layer: 
+a single portal -- the Cloud Access Layer --
 and Single-Sign-On (SSO). 
 The initial set of services as well as the first version of the access layer is scheduled to be available by the end of 2020.
 
-[**See also our roadmap**](roadmap).
+[**Have a look at our roadmap!**](roadmap).
 
 #### What are the plans for the Cloud Access Layer?
-The initial version of the Cloud Access Layer is planned to be kept simple while at the same time incorporating one of the most important features, the single-sign on functionality. Further functionality of the first version includes
-* list of services
-* detail view for services
-* possibility to access a service via a link
-* indication of service status
+The initial version of the Cloud Access Layer is planned to be kept simple while at the same time incorporating one of the most important features, the single-sign on (SSO) functionality. 
+Further functionality of the first version includes:
+* List of services;
+* Detailed view for services;
+* Possibility to access a service via a link;
+* Indication of service status.
 
-Later versions will contain more enhanced features like
-* personal workspace with overview about the personal set of services
-* possibility to request more specific setup of services
-* creation of meta services, e.g. combination of JupyterLab with HPC resources and a storage service
+Later versions will contain more enhanced features like:
+* Personal workspace with overview about the personal set of services;
+* Possibility to request more specific setup of services;
+* Creation of meta services, e.g. combination of JupyterLab with HPC resources and a storage service.
 
 If you have suggestions about additional use cases and functionality, please feel free to contact us. We appreciate all input from the user community!