diff --git a/docs/tuning-apps/networking/tcp.rst b/docs/tuning-apps/networking/tcp.rst
index 07dc893e036..0dc1cade211 100644
--- a/docs/tuning-apps/networking/tcp.rst
+++ b/docs/tuning-apps/networking/tcp.rst
@@ -247,20 +247,15 @@ not use specific IP networks |mdash| or not use any IP networks at all
 .. warning:: If you use the ``btl_tcp_if_include`` and
              ``btl_tcp_if_exclude`` MCA parameters to shape the
              behavior of the TCP BTL for MPI communications, you may
-             also need/want to investigate the corresponding MCA
-             parameters ``oob_tcp_if_include`` and
-             ``oob_tcp_if_exclude``, which are used to shape non-MPI
-             TCP-based communication (e.g., communications setup and
-             coordination during ``MPI_INIT`` and ``MPI_FINALIZE``).
-
-.. error:: TODO do corresponding OOB TCP params still exist in PMIx?
-
-Note that Open MPI will still use TCP for control messages, such as
-data between ``mpirun`` and the MPI processes, rendezvous information
-during ``MPI_INIT``, etc.  To disable TCP altogether, you also need to
-disable the ``tcp`` component from the OOB framework.
-
-.. error:: TODO Is this possible in PMIx?  I doubt it...?
+             also need/want to investigate the corresponding PRRTE
+             parameters that control use of network interfaces by the runtime
+             (e.g., communications setup and coordination during
+             ``MPI_INIT`` and ``MPI_FINALIZE``) using the `prte_info <https://docs.prrte.org/en/latest/man/man1/prte_info.1.html>`_
+             and `pmix_info <https://docs.openpmix.org/en/latest/man/man1/pmix_info.1.html>`_ commands.
+
+Note that the Open MPI runtime uses TCP for control messages, such as
+for data exchange between ``mpirun`` and the MPI processes, rendezvous information
+during ``MPI_INIT``, etc. even if the ``tcp`` BTL component is disabled.
 
 /////////////////////////////////////////////////////////////////////////