Adding clarity to the HELM installation example

doc/service_design/kubernetes/helm/HELM_Installation_aaS_Jenkins_Example.md

@@ -83,18 +83,19 @@ See the following image:
 ![img06.png](./img06.png)
 
  
-1. Drag-Drop the _CR_SPEC characteristic of jenkinsrfs from the Service>Text blocks
-2. Drag-Drop Text>Formatted text block
-3. Drag-Drop Text>Multi-line text input block
-4. Copy paste the YAML text
-5. Change the spec: destination:namespace to the value %s
-6. Drag-Drop Lists>Create list with block delete 2 items (click the gear icon). Connect it to formatted text block
-7. Drag-Drop Context>Current Service Order block and select the id. Connect it to the List
+1. Drag-Drop the _CR_SPEC block (Set characteristic value) of jenkinsrfs from the Service > Text blocks
+2. Drag-Drop the Text > Formatted text block and attach it after the block from the previous step
+3. Drag-Drop the Text > Multi-line text input block and attach it at the Input(String) connector of the block from the previous text 
+4. Copy paste the previously provided YAML text
+5. Change the spec:destination:namespace property to the value %s
+6. Drag-Drop the Lists > Create list block, delete the 2 extra items (click the gear icon). Attach it at the Variables(Array) connector of the formatted text block from the previous step.
+7. Drag-Drop the Service > Context > Current Service Order block and select the ID from the drop-down menu. Attach it to the List block of the previous step.
 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 
 2. Go to Service Specification Relationships and assign Jenkinsrfs
 3. Add also a Logo if you wish
@@ -143,7 +144,7 @@ Click to go to the secret resource (This is in the Resource inventory of OpenSli
 Use them to login in your Jenkins.
 
 
-> Exposing Jenkins to you external is a matter of cluster configuration and request (nodeport, load balancing, etc)! This is not a topic for this example
+> Exposing Jenkins externally is a matter of cluster configuration and request (nodeport, load balancing, etc), thus is not a topic for this example