diff --git a/doc/architecture/CRIDGE/CRIDGEforDevelopers.md b/doc/architecture/CRIDGE/CRIDGEforDevelopers.md
index 10cd9ac45c80ad5606af1fa18d611b753ad261fd..0457e529c34d138e17203fb2fbb2b10f858a386b 100644
--- a/doc/architecture/CRIDGE/CRIDGEforDevelopers.md
+++ b/doc/architecture/CRIDGE/CRIDGEforDevelopers.md
@@ -216,9 +216,9 @@ OSOM sends to CRIDGE a message with the following information:
 
 ## Probe further
 
- -  See examples of exposing operators via OpenSlice:
- 	- [Exposing Kubernetes Operators as a Service : Offering "Calculator as a Service" through OpenSlice](../../service_design/examples/ExposingCRDs_aaS_Example_Calculator/ExposingCRDs_aaS_Example_Calculator.md)
-
+- See examples of exposing Kubernetes Operators as a Service via OpenSlice:
+    - [Offering "Calculator as a Service"](../../service_design/examples/ExposingCRDs_aaS_Example_Calculator/ExposingCRDs_aaS_Example_Calculator.md)
+    - [Offering "Helm installation as a Service" (Jenkins example)](../../service_design/examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md)
  	
  	
  	
diff --git a/doc/portals_intro.md b/doc/portals_intro.md
index 995cb5de8a59be612e8663b45ba9e4cfb65be441..9cc36e19c4432ecf4d5a4f5eca15504e8f4a133b 100644
--- a/doc/portals_intro.md
+++ b/doc/portals_intro.md
@@ -1,12 +1,12 @@
 # OpenSlice Portals
 
-OpenSlice comprises of a web landing page [(See Demo)](http://portal.openslice.io/) that navigates to the respective Portals:
+OpenSlice comprises of a web landing page (See [Demo](http://portal.openslice.io/)) that navigates to the respective Portals:
 
-- Services Portal [(See Demo)](http://portal.openslice.io/services)
-- NFV Portal [(See Demo)](http://portal.openslice.io/nfvportal)
-- Products Portal [(See Demo)](http://portal.openslice.io/products)
-- Testing Portal [(See Demo)](http://portal.openslice.io/testing)
-- Resources Portal [(See Demo)](http://portal.openslice.io/resources)
+- Services Portal (See [Demo](http://portal.openslice.io/services))
+- NFV Portal (See [Demo](http://portal.openslice.io/nfvportal))
+- Products Portal (See [Demo](http://portal.openslice.io/products))
+- Testing Portal (See [Demo](http://portal.openslice.io/testing))
+- Resources Portal (See [Demo](http://portal.openslice.io/resources))
 
 
 Following you may find the scope each portal focuses on and the main TMF APIs it supports:
diff --git a/doc/service_design/kubernetes/ExposingKubernetesResources.md b/doc/service_design/kubernetes/ExposingKubernetesResources.md
index ade87388eb2de2f30ab269624f72f2b264040071..d196c1790ec7c86d1fd2e5568ec0a0c02bd4ded9 100644
--- a/doc/service_design/kubernetes/ExposingKubernetesResources.md
+++ b/doc/service_design/kubernetes/ExposingKubernetesResources.md
@@ -159,9 +159,10 @@ OpenSlice adds automatically as we see the following characteristics:
 ## Probe further
 
 
- -  See examples of exposing operators via OpenSlice:
- 	- [Exposing Kubernetes Operators as a Service : Offering "Calculator as a Service" through OpenSlice](ExposingCRDs_aaS_Example_Calculator.md)
- -	[Learn more about CRIDGE, the service in OSL that manages CRDs/CRs](CRIDGEforDevelopers_Jenkins_Example.md)
+- See examples of exposing Kubernetes Operators as a Service via OpenSlice:
+    - [Offering "Calculator as a Service"](../examples/ExposingCRDs_aaS_Example_Calculator/ExposingCRDs_aaS_Example_Calculator.md)
+    - [Offering "Helm installation as a Service" (Jenkins example)](../examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md)
+- [Learn more about CRIDGE, the service in OpenSlice that manages CRDs/CRs](../../architecture/CRIDGE/CRIDGEforDevelopers.md)
  	
  	
  	
diff --git a/doc/service_design/kubernetes/helm/design_helmaas.md b/doc/service_design/kubernetes/helm/design_helmaas.md
index 411910eacb6a72b489a9cad5a0a9e7e40248a9de..e4f3d75e9c824079d5a39f63fbe7a1af6019c213 100644
--- a/doc/service_design/kubernetes/helm/design_helmaas.md
+++ b/doc/service_design/kubernetes/helm/design_helmaas.md
@@ -31,7 +31,7 @@ Use OpenSlice to expose them in service catalogs and deploy them in complex scen
 
 ## The installation of HELM charts is based on OpenSlice CRD support
 
-Please read more [here](../ExposingKubernetesResources.md)
+Please read more [here](../ExposingKubernetesResources.md).
 
 
 For installing HELM charts we will use ArgoCD a well known Kubernetes-native continuous deployment (CD) tool 
@@ -57,11 +57,11 @@ Browse to Resource Specifications. You will see an entry like the following:
 
 see image: 
 
-![img01.png](./img01.png)
+![img01.png](../../examples/helmInstallation_aaS_Example_Jenkins/img01.png)
  
 
 
-## What's next
+## Probe further
 
 
-See the [Example: Offer Jenkins as a Service via Openslice](HELM_Installation_aaS_Jenkins_Example.md) 
+See the [Example: Offer Jenkins as a Service via Openslice](../../examples/helmInstallation_aaS_Example_Jenkins/HELM_Installation_aaS_Jenkins_Example.md) 
diff --git a/doc/service_design/lcmrules/intro.md b/doc/service_design/lcmrules/intro.md
index 651f83c8b5526a6775c09e1d1d4ca2f4a5727c17..0fb4cf473803391d7faceef8ad98581637fa5e5f 100644
--- a/doc/service_design/lcmrules/intro.md
+++ b/doc/service_design/lcmrules/intro.md
@@ -91,7 +91,7 @@ See our [LCM Blocks specification](./specification.md)
 
 ## Probe further
 
-* Check our [examples](../examples/intro.md) for more usages
+* Check our [examples](./examples.md) for more usages
 * See next the complete [specification](./specification.md)