diff --git a/applications/container_registry.md b/applications/container_registry.md
index 29f905ea..afe49726 100644
--- a/applications/container_registry.md
+++ b/applications/container_registry.md
@@ -1,8 +1,9 @@
 # Container Registry
 
-## Login in UI
+We use **Zot Registry** - a lightweight, OCI-native container image registry - as repository for storing and managing container images within EOxHub Workspaces.
+You can easily push your custom images to Zot and pull them directly into your **Argo Workflows**.
 
-The credentials can be found in the secret **registry-login** in the [credentials manager](./secret_manager.md) or your workspace.
+The login credentials can be found in the secret **registry-login** in the [credentials manager](./secret_manager.md) of your workspace.
 
 ```{figure} assets/credentials-manager/registry-credentials-detail.png
 ---
@@ -11,13 +12,15 @@ name: registry-credentials-detail
 Credential 'registry-login' contains the login information for the container registry: registry server FQDN (URL), username & password
 ```
 
-## Upload images to registry
+### Upload images to registry
+
+Authenticate with the endpoint and push your locally built images using standard tools like Docker or Podman, e.g.:
 
 1. Login
     ```shell
-    docker login -u <username> registry.[workspace-name].[cluster].eox.at  # e.g. registry.hub-test-ws1.hub-test.eox.at
+    docker login -u <username> registry.[workspace-name].[cluster].eox.at
+    # Type in the password when asked.  
     ```
-   Type in the password when asked.  
 
 2. Tag your image
     ```shell
@@ -30,4 +33,11 @@ Credential 'registry-login' contains the login information for the container reg
     docker push registry.[workspace-name].[cluster].eox.at/my-image:latest
     ```
 
-After a successful upload, the image is visible in the UI and in the file browser, and can be used in Argo Workflows, etc.
\ No newline at end of file
+After a successful upload, the image is visible in the UI and in the file browser.
+
+### Reference in Argo
+Update your Argo Workflow templates to point to the Zot registry URL in your `container` or `script` definitions.
+
+---
+
+> Official documentation: https://zotregistry.dev
\ No newline at end of file
diff --git a/inject-scripts.js b/inject-scripts.js
index 7f3c4643..b909a272 100644
--- a/inject-scripts.js
+++ b/inject-scripts.js
@@ -22,7 +22,8 @@ const SERVICE_MAPPING = {
     "Credentials Manager": ["credentials-manager"],
     "eoAPI": ["eoapi-rw-stac", "eoapi-rw-raster", "eoapi-rw-vector", ],
     "Dask Dashboard": ["dask-gateway-dashboard"],
-    "Publishing Dashboard": ["eodash"]
+    "Publishing Dashboard": ["eodash"],
+    "Container Registry": ["zot"]
 };
 
 // APPS THAT SHOULD NOT BE GREYED OUT, JUST WARNED