diff --git a/docs/src/how-to/administrate/backup-disaster-recovery.md b/docs/src/how-to/administrate/backup-disaster-recovery.md
index d714036be8f..43f2e19833f 100644
--- a/docs/src/how-to/administrate/backup-disaster-recovery.md
+++ b/docs/src/how-to/administrate/backup-disaster-recovery.md
@@ -73,7 +73,7 @@ Make sure (while connected via ssh) your Cassandra installation is doing well wi
 
 or (in newer versions)
 
-    nodetool ::FFFF:127.0.0.1 status
+    nodetool -h ::FFFF:127.0.0.1 status
 
 You should see a list of nodes like this:
 
diff --git a/docs/src/how-to/administrate/cassandra.rst b/docs/src/how-to/administrate/cassandra.rst
index 3ecc423ea5a..180a8f2a8c7 100644
--- a/docs/src/how-to/administrate/cassandra.rst
+++ b/docs/src/how-to/administrate/cassandra.rst
@@ -19,7 +19,7 @@ or if you are running a newer version of wire-server (altough it should be backw
 
 .. code:: sh 
 
-  ssh <ip of cassandra node> /opt/cassandra/bin/nodetool ::FFFF:127.0.0.1 status
+  ssh <ip of cassandra node> /opt/cassandra/bin/nodetool -h ::FFFF:127.0.0.1 status
 
 You should see a list of nodes like this:
 
@@ -55,7 +55,7 @@ For maintenance you may need to restart the cluster.
 
 On each server one by one:
 
-1. check your cluster is healthy: ``nodetool status`` or ``nodetool ::FFFF:127.0.0.1 status`` (in newer versions)
+1. check your cluster is healthy: ``nodetool status`` or ``nodetool -h ::FFFF:127.0.0.1 status`` (in newer versions)
 2. ``nodetool drain && systemctl stop cassandra`` (to stop accepting writes and flush data to disk; then stop the process)
 3. do any operation you need, if any
 4. Start the cassandra daemon process: ``systemctl start cassandra``