Unresolved issues of team_ptr and multi-init

content/shmem_team_ptr.tex

@@ -37,6 +37,9 @@
     when it can be accessed using memory loads and stores.  Otherwise, a null
     pointer is returned.
 
+    If \VAR{team} compares equal to \LibConstRef{SHMEM\_TEAM\_WORLD}, then
+    the behavior is identical to that of \FUNC{shmem\_ptr} with same \VAR{dest}
+    and \VAR{pe} arguments.
     If \VAR{team} compares equal to \LibConstRef{SHMEM\_TEAM\_INVALID},
     then a null pointer is returned.
     If \VAR{team} is otherwise invalid, the behavior is undefined.

content/threads_intro.tex

@@ -29,10 +29,10 @@
 
 \begin{enumerate}
 \item
-In the \CONST{SHMEM\_THREAD\_FUNNELED}, \CONST{SHMEM\_THREAD\_SERIALIZED}, and
-\CONST{SHMEM\_THREAD\_MULTIPLE} thread levels, the \FUNC{shmem\_init\_thread} and
-\FUNC{shmem\_finalize} calls must be invoked by the same thread.
-
+In the \CONST{SHMEM\_THREAD\_FUNNELED} and \CONST{SHMEM\_THREAD\_SERIALIZED}
+thread levels, all invocations of \FUNC{shmem\_init\_thread} and
+\FUNC{shmem\_finalize} must be made by the same thread.
+ 
 \item
 Any \openshmem operation initiated by a thread is considered an action of the
 \ac{PE} as a whole. The symmetric heap and symmetric variables scope are not