From 820632c765444f00585ca096143ebc8c84a83d7f Mon Sep 17 00:00:00 2001
From: "Uwe Jandt (DESY, HIFIS)" <uwe.jandt@desy.de>
Date: Mon, 3 Aug 2020 13:13:20 +0200
Subject: [PATCH] Removed colons `;` as they look ugly

---
 cloud-platform.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/cloud-platform.md b/cloud-platform.md
index 5692e0eb7..2831730fe 100644
--- a/cloud-platform.md
+++ b/cloud-platform.md
@@ -18,20 +18,20 @@ 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.
 
-[**Have a look at 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 (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.
+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!
 
-- 
GitLab