diff --git a/docs/HELM_Installation_aaS_Jenkins_Example/HELM_Installation_aaS_Jenkins_Example.md b/docs/HELM_Installation_aaS_Jenkins_Example/HELM_Installation_aaS_Jenkins_Example.md
index 89d57b77938c2c9be2e63a5e818cf59e3413d82d..ca1995192974c6b7bd2f14da7d954b6f9ab9de7d 100644
--- a/docs/HELM_Installation_aaS_Jenkins_Example/HELM_Installation_aaS_Jenkins_Example.md
+++ b/docs/HELM_Installation_aaS_Jenkins_Example/HELM_Installation_aaS_Jenkins_Example.md
@@ -10,9 +10,7 @@ Manage Helm charts installations via OpenSlice Service Specifications and Servic
 > 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
@@ -31,7 +29,7 @@ Use OpenSlice to expose them in service catalogs and deploy them in complex scen
 	- Manage multiple Helms in multiple clusters
 
 
-**The installation of HELM charts is based on OpenSlice CRD support**
+## The installation of HELM charts is based on OpenSlice CRD support
 
 Please read more [here](../ExposingKubernetesResources.md)
 
@@ -51,7 +49,7 @@ We will mainly use the CRD of ```Kind: Application``` that ArgoCD can manage
 
 Before proceeding, install ArgoCD in your management cluster, by following ArgoCD instructions
 
-As soon as you install ArgoCD, OpenSlice is automatically aware for specific new Kinds. The one we care is the ```Kind: Application``` that ArgoCD can manage under the apiGroup argoproj.io
+As soon as you install ArgoCD, OpenSlice is automatically aware for specific new Kinds. The one we will use is is the ```Kind: Application``` that ArgoCD can manage under the apiGroup argoproj.io
 
 Browse to Resource Specifications. You will see an entry like the following:
 
@@ -64,6 +62,7 @@ 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
@@ -134,7 +133,7 @@ On each installation OSOM will change the name of the resource in order to be un
     namespace: opencrdtest
  ```
  
-**This causea an issue that ArgoCD installs the Jenkins akways in the same namespace**
+**This implies that ArgoCD installs the Jenkins always in the same namespace**
  
 **To avoid this we will create a simple pre-provision rule to change the namespace properly**
 
@@ -150,6 +149,7 @@ See the following image:
 7. Drag-Drop Context>Current Service Order block and select the id. Connect it to the List
 8. Save the PRE_PROVISION Rule
 
+# Expose the service to your users
 
 Expose then as CustomerFacingServiceSpecification by using the previous RFSS as Service Specification Relationship 
 1. Create a Jenkins service and mark as Bundle and save it 
@@ -159,11 +159,16 @@ Expose then as CustomerFacingServiceSpecification by using the previous RFSS as
 <img src="img03.png" width=640px>
 <img src="img04.png" width=640px>
  
-Expose it now to a Category and a Catalog to be available for ordering. Y
- 
-#Order the service
+Expose it now to a Category and a Catalog to be available for ordering.
+  
+<img src="img061.png" >
+
+# Order the service
+
+Order the service from the catalog. 
+
 
-Order the service from the catalog. Soon the order will be completed and the Services will be active
+Soon the order will be completed and the Services will be active
 
 
 <img src="img07.png" width=640px>