diff --git a/doc/source/user/usage.rst b/doc/source/user/usage.rst
index c06d3fbbf..d0e6c8f4f 100644
--- a/doc/source/user/usage.rst
+++ b/doc/source/user/usage.rst
@@ -26,12 +26,12 @@ Node States
 * The nodes should be moved to ``MANAGEABLE`` provision state before
   introspection (requires *python-ironicclient* of version 0.5.0 or newer)::
 
-    ironic node-set-provision-state <UUID> manage
+    openstack baremetal node manage <node>
 
 * After successful introspection and before deploying nodes should be made
   available to Nova, by moving them to ``AVAILABLE`` state::
 
-    ironic node-set-provision-state <UUID> provide
+    openstack baremetal node provide <node>
 
   .. note::
     Due to how Nova interacts with Ironic driver, you should wait 1 minute
diff --git a/doc/source/user/workflow.rst b/doc/source/user/workflow.rst
index c92ea7b87..8030a8d08 100644
--- a/doc/source/user/workflow.rst
+++ b/doc/source/user/workflow.rst
@@ -6,8 +6,9 @@ Workflow
 
 Usual hardware introspection flow is as follows:
 
-* Operator enrolls nodes into Ironic_ e.g. via ironic CLI command.
-  Power management credentials should be provided to Ironic at this step.
+* Operator enrolls nodes into Ironic_ e.g. via `openstack baremetal CLI`_
+  command. Power management credentials should be provided to Ironic at this
+  step.
 
 * Nodes are put in the correct state for introspection as described in
   :ref:`node states <node_states>`.
@@ -81,3 +82,4 @@ The diagram also shows events that trigger state transitions.
    :alt: ironic-inspector state machine diagram
 
 .. _Ironic: https://wiki.openstack.org/wiki/Ironic
+.. _openstack baremetal CLI: https://docs.openstack.org/python-ironicclient/latest/cli/osc_plugin_cli.html