diff --git a/docs/deploying_clearml/enterprise_deploy/appgw_install_compose_hosted.md b/docs/deploying_clearml/enterprise_deploy/appgw_install_compose_hosted.md
index ad6ce13e..edda145e 100644
--- a/docs/deploying_clearml/enterprise_deploy/appgw_install_compose_hosted.md
+++ b/docs/deploying_clearml/enterprise_deploy/appgw_install_compose_hosted.md
@@ -10,7 +10,7 @@ The AI Application Gateway enables external access  to ClearML tasks, and applic
 require HTTP or TCP access. The gateway is configured with an endpoint or external address, making these services 
 accessible from the user's machine, outside the workload nodes’ network.
 
-This guide details the installation of the App Gateway Router for ClearML users who use ClearML's SaaS control 
+This guide details the installation of the App Gateway Router for ClearML users who use ClearML's hosted control 
 plane while hosting their own workload nodes.
 
 ## Requirements
diff --git a/docs/deploying_clearml/enterprise_deploy/change_artifact_links.md b/docs/deploying_clearml/enterprise_deploy/change_artifact_links.md
index 34e67d5c..e8492c18 100644
--- a/docs/deploying_clearml/enterprise_deploy/change_artifact_links.md
+++ b/docs/deploying_clearml/enterprise_deploy/change_artifact_links.md
@@ -29,17 +29,18 @@ script changes the values in the databases, and can't be undone.
 ## Fixing MongoDB links
 
 1. Access the `apiserver` Docker container:  
-  * In `docker-compose:`
+
+   * In `docker-compose:`
     
-     ```commandline
-     sudo docker exec -it allegro-apiserver /bin/bash
-      ```
+      ```commandline
+      sudo docker exec -it allegro-apiserver /bin/bash
+       ```
     
-  * In Kubernetes:
+   * In Kubernetes:
    
-     ```commandline
-     kubectl exec -it -n clearml <clearml-apiserver-pod-name> -- bash
-     ```
+      ```commandline
+      kubectl exec -it -n clearml <clearml-apiserver-pod-name> -- bash
+      ```
 
 1. Navigate to the script location in the `upgrade` folder:
 
diff --git a/docs/deploying_clearml/enterprise_deploy/k8s.md b/docs/deploying_clearml/enterprise_deploy/k8s.md
index 3a217321..e237919b 100644
--- a/docs/deploying_clearml/enterprise_deploy/k8s.md
+++ b/docs/deploying_clearml/enterprise_deploy/k8s.md
@@ -66,13 +66,13 @@ imageCredentials:
 clearml:
  cookieDomain: "<BASE_DOMAIN>"
  # Set values for improved security
- apiserverKey: ""
- apiserverSecret: ""
- fileserverKey: ""
- fileserverSecret: ""
- secureAuthTokenSecret: ""
- testUserKey: ""
- testUserSecret: ""
+ apiserverKey: "<GENERATED_API_SERVER_KEY>"
+ apiserverSecret: "<GENERATED_API_SERVER_SECRET>"
+ fileserverKey: "<GENERATED_FILE_SERVER_KEY>"
+ fileserverSecret: "<GENERATED_FILE_SERVER_SECRET>"
+ secureAuthTokenSecret: "<GENERATED_AUTH_TOKEN_SECRET>"
+ testUserKey: "<GENERATED_TEST_USER_KEY>"
+ testUserSecret: "<GENERATED_TEST_USER_SECRET>"
 
 
 apiserver:
diff --git a/docs/deploying_clearml/enterprise_deploy/multi_tenant_k8s.md b/docs/deploying_clearml/enterprise_deploy/multi_tenant_k8s.md
index 25803059..8b1473f5 100644
--- a/docs/deploying_clearml/enterprise_deploy/multi_tenant_k8s.md
+++ b/docs/deploying_clearml/enterprise_deploy/multi_tenant_k8s.md
@@ -565,7 +565,7 @@ curl $APISERVER_URL/system.create_company \
 ### Limit Features for all Users
 
 This Helm Chart value in the `overrides.yaml` will have priority over all tenants, and will limit the features 
-available to any user in the system. This means that even if the feature is enabled for the tenant, if it;s not in this 
+available to any user in the system. This means that even if the feature is enabled for the tenant, if it's not in this 
 list, the user will not see it.
 
 Example: all users will only have the `applications` feature enabled.