diff --git a/doc/source/support-matrix.ini b/doc/source/support-matrix.ini
index c2b54caad05e..b14797111b30 100644
--- a/doc/source/support-matrix.ini
+++ b/doc/source/support-matrix.ini
@@ -359,7 +359,7 @@ notes=Suspending an instance can be thought of as roughly
   consumes any RAM or CPUs, with its live running state
   having been preserved in a file on disk. It can later
   be restored, at which point it should continue execution
-  where it left off. As with pause, it suffers from the fact
+  where it left off. As with stopping instance CPUs, it suffers from the fact
   that the guest OS will typically be left with a clock that
   is no longer telling correct time. For container based
   virtualization solutions, this operation is particularly
@@ -417,7 +417,7 @@ driver-impl-ironic=complete
 [operation.unpause]
 title=Resume instance CPUs
 status=optional
-notes=See notes for the pause operation
+notes=See notes for the "Stop instance CPUs" operation
 driver-impl-xenserver=complete
 driver-impl-libvirt-kvm-x86=complete
 driver-impl-libvirt-qemu-x86=complete