[PATCH] docs: Update qmp scripts path

[Shivang Upadhyay <shivangu@linux.ibm.com>]

Qmp scripts are essentially removed from scripts directory as per commit
b08e111b1e1 ("scripts: nudge users to use 'run' script for scripts that
import qemu.qmp"). Scripts essentially redirect to run build/run script.
Reflecting the same changes on docs.

Signed-off-by: Shivang Upadhyay <shivangu@linux.ibm.com>
---
 docs/devel/build-system.rst            |  2 +-
 docs/interop/live-block-operations.rst | 10 +++++-----
 docs/system/arm/cpu-features.rst       |  5 +++--
 docs/system/devices/usb.rst            |  2 +-
 4 files changed, 10 insertions(+), 9 deletions(-)

diff --git a/docs/devel/build-system.rst b/docs/devel/build-system.rst
index 71331e64ac..052eac7c51 100644
--- a/docs/devel/build-system.rst
+++ b/docs/devel/build-system.rst
@@ -521,7 +521,7 @@ Built by configure:
   before running the requested command. Pass the command to run as
   args, for example::
 
-    $ ./build/run ./script/qmp/qmp-shell-wrap qemu-system-x86_64
+    $ ./build/run qmp-shell-wrap qemu-system-x86_64
 
   will use the ``python3`` binary and site-packages from the local
   venv to run ``qmp-shell-wrap`` and spawn the QEMU emulator from
diff --git a/docs/interop/live-block-operations.rst b/docs/interop/live-block-operations.rst
index 6b549ede7c..f8beb66275 100644
--- a/docs/interop/live-block-operations.rst
+++ b/docs/interop/live-block-operations.rst
@@ -152,12 +152,12 @@ of QEMU 2.9, accept ``node-name`` parameter) when performing various
 block operations.
 
 To interact with the QEMU instance launched above, we will use the
-``qmp-shell`` utility (located at: ``qemu/scripts/qmp``, as part of the
-QEMU source directory), which takes key-value pairs for QMP commands.
-Invoke it as below (which will also print out the complete raw JSON
-syntax for reference -- examples in the following sections)::
+``qmp-shell`` utility (available via the ``run`` script in the build
+directory after running configure), which takes key-value pairs for QMP
+commands.  Invoke it as below (which will also print out the complete raw
+JSON syntax for reference -- examples in the following sections)::
 
-    $ ./qmp-shell -v -p /tmp/qmp-sock
+    $ $builddir/run qmp-shell -v -p /tmp/qmp-sock
     (QEMU)
 
 .. note::
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index 10b0eff27e..c56f5fe208 100644
--- a/docs/system/arm/cpu-features.rst
+++ b/docs/system/arm/cpu-features.rst
@@ -36,8 +36,9 @@ CPU Feature Probing
 
 Determining which CPU features are available and functional for a given
 CPU type is possible with the ``query-cpu-model-expansion`` QMP command.
-Below are some examples where ``scripts/qmp/qmp-shell`` (see the top comment
-block in the script for usage) is used to issue the QMP commands.
+Below are some examples where ``qmp-shell`` (available via
+``$builddir/run qmp-shell`` after running configure) is used to issue the
+QMP commands.
 
 1. Determine which CPU features are available for the ``max`` CPU type
    (Note, we started QEMU with qemu-system-aarch64, so ``max`` is
diff --git a/docs/system/devices/usb.rst b/docs/system/devices/usb.rst
index dc694d23c2..7e2a303f41 100644
--- a/docs/system/devices/usb.rst
+++ b/docs/system/devices/usb.rst
@@ -258,7 +258,7 @@ device visible to the guest. The workflow looks like this:
 #. ``device-add usb-bot,id=foo``
 #. ``device-add scsi-{hd,cd},bus=foo.0,lun=0``
 #. optionally add more devices (luns 1 ... 15)
-#. ``scripts/qmp/qom-set foo.attached = true``
+#. ``$builddir/run qom-set foo.attached = true``
 
 .. _host_005fusb_005fdevices:
 
-- 
2.54.0