diff --git a/xml/admin_saltcluster.xml b/xml/admin_saltcluster.xml
index 3c3a0243..e3c90d70 100644
--- a/xml/admin_saltcluster.xml
+++ b/xml/admin_saltcluster.xml
@@ -1176,33 +1176,28 @@ OSD_ID HOST STATE PG_COUNT REPLACE FORCE STARTED_
For example:
&prompt.cephuser;ceph orch osd rm 4 --replace
-
- Replacing an OSD is identical to removing an OSD (see
- for more details) with the exception
- that the OSD is not permanently removed from the CRUSH hierarchy and is
- assigned a destroyed flag instead.
-
-
- The destroyed flag is used to determined OSD IDs that
- will be reused during the next OSD deployment. Newly added disks that match
- the &drvgrps; specification (see for more
- details) will be assigned OSD IDs of their replaced counterpart.
-
-
-
- Appending the option will not execute the
- actual replacement, but will preview the steps that would normally happen.
-
-
-
-
- In the case of replacing an OSD after a failure, we highly recommend
- triggering a deep scrub of the placement groups. See
- for more details.
-
-
- Run the following command to initiate a deep scrub:
-
+
+ Replacing an OSD is identical to removing an OSD (see
+ for more details) with the
+ exception that the OSD is not permanently removed from the CRUSH
+ hierarchy and is assigned a destroyed flag instead.
+
+
+ The destroyed flag is used to determined OSD IDs
+ that will be reused during the next OSD deployment. Newly added disks
+ that match the &drvgrps; specification (see
+ for more details) will be assigned OSD
+ IDs of their replaced counterpart.
+
+
+
+ In the case of replacing an OSD after a failure, we highly recommend
+ triggering a deep scrub of the placement groups. See
+ for more details.
+
+
+ Run the following command to initiate a deep scrub:
+ &prompt.cephuser;ceph osd deep-scrub osd.OSD_NUMBER