diff --git a/doc/deploymentK8s.md b/doc/deploymentK8s.md
index b7e06d7b8474cc2de33a1a30a3c17f4c2894b62d..a98560f95e05e5e1213c0b8b0333a33560462f76 100644
--- a/doc/deploymentK8s.md
+++ b/doc/deploymentK8s.md
@@ -22,10 +22,12 @@
     * **Nginx Ingress Controller (Kubernetes Community Edition):**  The ingress resource is configured to use an Nginx type ingress controller. 
       * If you need to expose the message bus service (Artemis), which communicates using the TCP protocol, you must use version **>= 1.9.13** of the Nginx Ingress Controller (a prerequisite for [managing multiple kubernetes clusters](#management-of-multiple-kubernetes-clusters)). This version or higher includes the required functionality to handle TCP services. Otherwise, earlier versions may suffice depending on your configuration.
       * To install or upgrade to the required version, run the following command:
+
       ```bash
       helm upgrade nginx-ingress ingress-nginx/ingress-nginx --namespace ingress \
       --set tcp.61616="<openslice-namespace>/<openslice-helm-release-name>-artemis:61616"
       ```
+
       Replace `<helm-release-name>` with the name of your OpenSlice Helm release.
       * More details regarding the Nginx Ingress Controller (Kubernetes Community Edition) can be found [here](https://kubernetes.github.io/ingress-nginx/deploy/).
     * **Other Ingress Controller:**  For non-Nginx ingress controllers, modify `[repo-root]/kubernetes/helm/openslice/templates/openslice-ingress.yaml` to meet your controller’s requirements.
@@ -152,9 +154,9 @@ By default, the OpenSlice Helm chart also deploys CRIDGE alongside the bundle. T
    
     - If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the `--set-file` option, at the final [deployment process](#deploy-the-helm-chart):
 
-     ```bash
-     --set-file cridge.kubeconfig.raw=path/to/kubeconfig.yaml
-     ```
+    ```bash
+    --set-file cridge.kubeconfig.raw=path/to/kubeconfig.yaml
+    ```
 
     - This method reads the specified kubeconfig file and mounts it into the CRIDGE container during deployment.
 
@@ -162,9 +164,9 @@ By default, the OpenSlice Helm chart also deploys CRIDGE alongside the bundle. T
    
     - Alternatively, you can pass the kubeconfig as a base64-encoded string, during the Helm installation using the `--set` option, at the final [deployment process](#deploy-the-helm-chart):
 
-     ```bash
-     --set cridge.kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"
-     ```
+    ```bash
+    --set cridge.kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"
+    ```
 
     - This method encodes the kubeconfig content and passes it directly to the CRIDGE container.
 
@@ -201,16 +203,20 @@ Similarly, to configure CRIDGE, there are three different ways to provide this k
 
 2. **Passing the Kubeconfig File Using Helm (`--set-file`)**:
     - If you do not wish to manually copy the file, you can pass it directly during the Helm installation using the `--set-file` option:
-     ```bash
-     helm install cridge-release . --set-file kubeconfig.raw=path/to/kubeconfig.yaml
-     ```
+
+    ```bash
+    helm install cridge-release . --set-file kubeconfig.raw=path/to/kubeconfig.yaml
+    ```
+
     - This method reads the specified kubeconfig file and mounts it into the CRIDGE container during deployment.
 
 3. **Passing a Base64-Encoded Kubeconfig Using Helm (`--set`)**:
     - Alternatively, you can pass the kubeconfig as a base64-encoded string:
-     ```bash
-     helm install cridge-release . --set kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"
-     ```
+    
+    ```bash
+    helm install cridge-release . --set kubeconfig.base64="$(base64 path/to/kubeconfig.yaml)"
+    ```
+    
     - This method encodes the kubeconfig content and passes it directly to the CRIDGE container.
 
 > **Note:** Regardless of the method you choose, if you're using a non-standard kubeconfig file name, make sure to adjust the references or rename the file as needed.