diff --git a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc
index 154d6d207..647799c1c 100644
--- a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc
+++ b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc
@@ -675,7 +675,7 @@ To back up your database(s), you install the _neo4j-admin_ Helm chart using the
 +
 [source, shell, role='noheader']
 ----
-helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
+helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
 ----
 +
 The _neo4j/neo4j-admin_ Helm chart installs a cronjob that launches a pod based on the job schedule.
@@ -847,7 +847,7 @@ resources:
 +
 [source, shell, role='noheader']
 ----
-helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
+helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
 ----
 . Monitor the pod logs using `kubectl logs pod/<neo4j-aggregate-backup-pod-name>` to check the progress of the aggregate backup operation.
 . Verify that the aggregated backup file has replaced your backup chain in the cloud provider bucket or on-premises storage.