temp: possible doc changes?

doc/config.rst

@@ -132,6 +132,8 @@ option, or coverage.py will produce very wrong results.
 .. _gevent: http://www.gevent.org/
 .. _eventlet: http://eventlet.net/
 
+See :ref:subprocess: for details of multi-process measurement.
+
 Before version 4.2, this option only accepted a single string.
 
 .. versionadded:: 4.0

doc/subprocess.rst

@@ -25,17 +25,24 @@ the name of the :ref:`configuration file <config>` to use.
 
 .. note::
 
-    If you have subprocesses because you are using :mod:`multiprocessing
+    If you have subprocesses created with :mod:`multiprocessing
     <python:multiprocessing>`, the ``--concurrency=multiprocessing``
     command-line option should take care of everything for you.  See
     :ref:`cmd_run` for details.
 
+.. note::
+
+    Stopping a multiprocessing process with :meth:`terminate
+    <python:multiprocessing.Process.terminate>` or :meth:`kill
+    <python:multiprocessing.Process.kill>` will prevent recording data from the
+    stopped process.  Those methods don't run clean-up code in the process.
+
 When using this technique, be sure to set the parallel option to true so that
 multiple coverage.py runs will each write their data to a distinct file.
 
 
-Configuring Python for sub-process coverage
--------------------------------------------
+Configuring Python for sub-process measurement
+----------------------------------------------
 
 Measuring coverage in sub-processes is a little tricky.  When you spawn a
 sub-process, you are invoking Python to run your program.  Usually, to get