diff --git a/artiq/master/scheduler.py b/artiq/master/scheduler.py
index 2ae575c95..842fda853 100644
--- a/artiq/master/scheduler.py
+++ b/artiq/master/scheduler.py
@@ -446,6 +446,9 @@ class Scheduler:
         whether returning control to the host and pausing would have an effect,
         in order to avoid the cost of switching kernels in the common case
         where ``pause`` does nothing.
+
+        This function does not have side effects, and does not have to be
+        followed by a call to ``pause``.
         """
         for pipeline in self._pipelines.values():
             if rid in pipeline.pool.runs:
diff --git a/doc/manual/management_system.rst b/doc/manual/management_system.rst
index bb51aa699..c28e612cf 100644
--- a/doc/manual/management_system.rst
+++ b/doc/manual/management_system.rst
@@ -72,7 +72,9 @@ To check whether ``pause()`` would in fact *not* return immediately, use :meth:`
 
 The experiment must place the hardware in a safe state and disconnect from the core device (typically, by using ``self.core.comm.close()``) before calling ``pause``.
 
-Accessing the ``pause`` method is done through a virtual device called ``scheduler`` that is accessible to all experiments. The scheduler virtual device is requested like regular devices using ``get_device`` or ``attr_device``.
+Accessing the ``pause`` and ``check_pause`` methods is done through a virtual device called ``scheduler`` that is accessible to all experiments. The scheduler virtual device is requested like regular devices using ``get_device`` or ``attr_device``.
+
+``check_pause`` can be called (via RPC) from a kernel, but ``pause`` must not.
 
 Multiple pipelines
 ------------------