Merge pull request #9 from davidozog/sec/collectives-team_intro_edits

Teams and collectives intro edits

content/collective_intro.tex

@@ -33,21 +33,17 @@ \subsubsection*{Team-based collectives}
 or \LibConstRef{SHMEM\_TEAM\_INVALID} is passed to a team-based collective
 routine, the behavior is undefined.
 
-Team objects encapsulate the per \ac{PE} system resources required to complete
-team-based collective routines.
-All \openshmem teams-based collective calls are blocking routines which may use those
-system resources. On completion of a team-based collective call, the \ac{PE} may
-immediately call another collective on that same team without any other intervening
-synchronization across the team.
+All \openshmem teams-based collective operations are blocking routines.  On
+return from a team-based collective call, the \ac{PE} may immediately call
+another collective operation on that same team.
+Team-based collectives must occur in the same
+program order across all \acp{PE} in a team.
 
 While \openshmem routines provide thread support according to the
 thread-support level provided at initialization (see
 Section~\ref{subsec:thread_support}), team-based collective routines
 may not be called simultaneously by multiple threads on a given team.
 
-Collective operations are matched across a given team based on ordering. So for a given team,
-collectives must occur in the same order across all PEs in a team.
-
 The team-based collective routines defined in the \openshmem Specification are:
 
 \begin{itemize}

content/teams_intro.tex

@@ -60,7 +60,7 @@ \subsubsection*{Collective Ordering}
 collective operations on a team, the collective operations---along with any
 relevant team based resources---are matched across the \acp{PE} in the team
 based on ordering of collective routine calls. It is the responsibility
-of the \openshmem program to ensure the same ordering of collective routine calls
+of the user to ensure that team-based collectives occur in the same program order
 across all \acp{PE} in a team.
 
 A full discussion of collective semantics follows in Section~\ref{subsec:coll}.