diff --git a/content/shmem_addr_accessible.tex b/content/shmem_addr_accessible.tex
index 14b837662..0e32d77ad 100644
--- a/content/shmem_addr_accessible.tex
+++ b/content/shmem_addr_accessible.tex
@@ -32,15 +32,7 @@
 }
 
 \apinotes{
-    This routine may be particularly useful for hybrid programming with other
-    communication libraries (such as \ac{MPI}) or parallel languages.  For
-    example, when an \ac{MPI} job uses \ac{MPMD} mode, multiple executable
-    \ac{MPI} programs may use \openshmem routines.  In such cases, static
-    memory, such as a \Cstd global variable, is
-    symmetric between processes running from the same executable file, but is
-    not symmetric between processes running from different executable files.
-    Data allocated from the symmetric heap (e.g., using \FUNC{shmem\_malloc})
-    is symmetric across the same or different executable files.
+    None.
 }
 
 \end{apidefinition}
diff --git a/content/shmem_pe_accessible.tex b/content/shmem_pe_accessible.tex
index 15d6e6c7a..153ecfb21 100644
--- a/content/shmem_pe_accessible.tex
+++ b/content/shmem_pe_accessible.tex
@@ -29,14 +29,7 @@
 }
 
 \apinotes{
-    This routine may be particularly useful for hybrid programming with other
-    communication libraries (such as \ac{MPI}) or parallel languages.  For
-    example, when an \ac{MPI} job uses \ac{MPMD} mode, multiple executable
-    \ac{MPI} programs are executed as part of the same MPI job.  In such cases,
-    \openshmem support may only be available between processes running from the
-    same executable file.  In addition, some environments may allow a hybrid
-    job to span multiple network partitions.  In such scenarios, \openshmem
-    support may only be available between \acp{PE} within the same partition.
+    None.
 }
 
 \end{apidefinition}