From 2547ac0438ec0374f75227f60a35b11ad9a986a4 Mon Sep 17 00:00:00 2001
From: Conway Zhang <56783384+aierate@users.noreply.github.com>
Date: Wed, 6 Nov 2024 18:31:29 +0800
Subject: [PATCH] HDDS-11652. Fix SCM start command in SCM-HA doc (#7398)

---
 hadoop-hdds/docs/content/feature/SCM-HA.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/hadoop-hdds/docs/content/feature/SCM-HA.md b/hadoop-hdds/docs/content/feature/SCM-HA.md
index cc42500e0c3..333c908275d 100644
--- a/hadoop-hdds/docs/content/feature/SCM-HA.md
+++ b/hadoop-hdds/docs/content/feature/SCM-HA.md
@@ -96,7 +96,7 @@ Second and third nodes should be *bootstrapped* instead of init. These clusters
 ozone scm --bootstrap
 ```
 
-Note: both commands perform one-time initialization.  SCM still needs to be started by running `ozone scm --daemon start`.
+Note: both commands perform one-time initialization.  SCM still needs to be started by running `ozone --daemon start scm`.
 
 ## Auto-bootstrap
 
@@ -121,7 +121,7 @@ Note: SCM still needs to be started after the init/bootstrap process.
 ```
 ozone scm --init
 ozone scm --bootstrap
-ozone scm --daemon start
+ozone --daemon start scm
 ```
 
 For Docker/Kubernetes, use `ozone scm` to start it in the foreground.