Suggested v1.6 doc-edits throughout the spec

content/collective_intro.tex

@@ -19,7 +19,7 @@
 \end{enumerate}
 
 Concurrent accesses to symmetric memory by an \openshmem collective
-routine and any other means of access---where at least one updates the
+routine and any other means of access---where at least one PE updates the
 symmetric memory---results in undefined behavior.
 Since \acp{PE} can enter and exit collectives at different times,
 accessing such memory remotely may require additional synchronization.

content/memmgmt_intro.tex

@@ -3,7 +3,7 @@
 symmetric data objects in the symmetric heap.
 
 The symmetric memory allocation routines differ from the private heap
-allocation routines in that they must be called by all \acp{PE} in a
+allocation routines in that they must be called by all \acp{PE} in
 the world team.  When specified, each of these routines includes at
 least one call to a procedure that is semantically equivalent to
 \FUNC{shmem\_barrier\_all}.  This ensures that all \acp{PE}

content/teams_intro.tex

@@ -21,7 +21,7 @@ \subsubsection*{Predefined and Application-Defined Teams}
 portion of an application.
 Any team successfully created by a \FUNC{shmem\_team\_split\_*}
 routine is valid until it is destroyed.
-All valid teams have a least one member.
+All valid teams have at least one member.
 
 \subsubsection*{Team Handles}
 
@@ -84,7 +84,7 @@ \subsubsection*{Team Creation}
 
 \acp{PE} in a newly created team are consecutively numbered starting with
 \ac{PE} number 0. \acp{PE} are ordered by their \ac{PE} number in
-the parent team. Team relative \ac{PE}
+the parent team. Team-relative \ac{PE}
 numbers can be used for point-to-point operations through team-based
 contexts (see Section~\ref{sec:ctx}) or using the translation routine
 \FUNC{shmem\_team\_translate\_pe}.