adding more images for #2 and

osl/documentation#7

docs/HELM_Installation_aaS_Jenkins_Example/HELM_Installation_aaS_Jenkins_Example.md

@@ -4,18 +4,28 @@ Manage Helm charts installations via OpenSlice Service Specifications and Servic
 
 
 > Kubernetes is an orchestration system for automating software deployment, scaling, and management. One can interact though the Kubernetes API and it has a set of objects ready for use out of the box. 
+
 > Helm is a tool that automates the creation, packaging, configuration, and deployment of Kubernetes applications by combining your configuration files into a single reusable package
+
 > At the heart of Helm is the packaging format called charts. Each chart comprises one or more Kubernetes manifests -- and a given chart can have child charts and dependent charts, as well. Using Helm charts:
+
 >       - Reduces the complexity of deploying Microservices
+
 >       - Enhances deployment speed
+
 >       - Developers already know the technology
+
 > There are many Helm charts and Helm repositories there that are ready to be used
+
 > Enable loose coupling and more orchestration scenarios
+
 >	Developers create and deploy applications in things they already know (e.g. Helm charts)
+
 > Use the TMF models as wrapper entities around Helm charts
 
 
-Use OpenSlice to expose them in service catalogs and deploy them in complex scenarios (service bundles) involving also other systems
+Use OpenSlice to expose them in service catalogs and deploy them in complex scenarios (service bundles) involving also other systems:
+
 	- Include e.g. RAN controllers, 
 	- Pass values through life cycle rules from one service to another, 
 	- Manage multiple Helms in multiple clusters
@@ -29,7 +39,9 @@ Please read more [here](../ExposingKubernetesResources.md)
 For installing HELM charts we will use ArgoCD a well known Kubernetes-native continuous deployment (CD) tool 
 
 > ArgoCD is a Kubernetes-native continuous deployment (CD) tool
+
 > While just deploying Heml charts is just a scenario for ArgoCD , in future one can exploit it for many things
+
 > Despite some other tools like FluxCD, it provides also a UI which is useful for management and troubleshooting
 
 
@@ -52,11 +64,11 @@ see image:
 # Example: Offer Jenkins as a Service via Openslice
 
 We will use the ```Kind: Application``` of ArgoCD and create a  ResourceFacingServiceSpecification for Jenkins
-1. Go to Service Specifications
-2. Create New Specification
-3. Give a Name, eg. jenkinsrfs
-4. Go to Resource Specification Relationships
-5. Assign ```Application@argoproj.io/v1alpha1@kubernetes@https://10.10.10.144:6443/```
+	1. Go to Service Specifications
+	2. Create New Specification
+	3. Give a Name, eg. jenkinsrfs
+	4. Go to Resource Specification Relationships
+	5. Assign ```Application@argoproj.io/v1alpha1@kubernetes@https://10.10.10.144:6443/```
 
 <img src="img02.png" width=640px>