Merge pull request #1 from bcmIntc/bcmIntc-section-profiler_1

[SHMEM 1.6 Sec 10] Minor grammatical edits

content/profiling_interface.tex

@@ -1,6 +1,6 @@
 The objective of the \openshmem profiling interface is to ensure an
 easy and flexible usage model for profiling (and other similar)
-tool developers to interface their codes into \openshmem
+tool developers to interface their code into \openshmem
 implementations on different platforms. Since \openshmem is a
 machine-independent standard with different implementations, it is
 unreasonable to expect that the authors and developers of profiling
@@ -133,7 +133,7 @@ \subsection{Limitations}
 
 \subsubsection{Multiple Counting}
 \label{sec:pshmem_multiple_count}
-Since some functions in \openshmem library may be implemented
+Since some functions in the \openshmem library may be implemented
 using more basic \openshmem functions, it is possible for these basic
 profiling functions to be called from within an \openshmem function
 that was originally called from a profiling routine. For example,

content/shmem_pcontrol.tex

@@ -29,7 +29,7 @@
   it is impossible to precisely specify the semantics that will be provided by
   calls to \FUNC{shmem\_pcontrol}. This vagueness extends to the number of
   arguments to the function and their datatypes. However, to provide some
-  level of portability of user codes to different profiling libraries, the
+  level of portability of user code to different profiling libraries, the
   following \VAR{level} values are recommended.
 
   \begin{itemize}