Merge pull request #1342 from jsquyres/pr/v2.0.1/README-typo-fixes

README: fix a bunch of typos

Author: jsquyres

README

@@ -410,18 +410,18 @@ General Run-Time Support Notes
   is a shared library), unless using the --prefix or
   --enable-mpirun-prefix-by-default functionality (see below).
 
-- Open MPI's run-time behavior can be customized via MCA ("MPI
-  Component Architecture") parameters (see below for more information
-  on how to get/set MCA parameter values).  Some MCA parameters can be
-  set in a way that renders Open MPI inoperable (see notes about MCA
+- Open MPI's run-time behavior can be customized via MPI Component
+  Architecture (MCA) parameters (see below for more information on how
+  to get/set MCA parameter values).  Some MCA parameters can be set in
+  a way that renders Open MPI inoperable (see notes about MCA
   parameters later in this file).  In particular, some parameters have
   required options that must be included.
 
   - If specified, the "btl" parameter must include the "self"
     component, or Open MPI will not be able to deliver messages to the
     same rank as the sender.  For example: "mpirun --mca btl tcp,self
     ..."
-  - If specified, the "btl_tcp_if_exclude" paramater must include the
+  - If specified, the "btl_tcp_if_exclude" parameter must include the
     loopback device ("lo" on many Linux platforms), or Open MPI will
     not be able to route MPI messages using the TCP BTL.  For example:
     "mpirun --mca btl_tcp_if_exclude lo,eth1 ..."
@@ -488,7 +488,7 @@ MPI Functionality and Features
   by default (it can be disabled via the --disable-libompitrace
   flag).  This library provides a simplistic tracing of select MPI
   function calls via the MPI profiling interface.  Linking it in to
-  your appliation via (e.g., via -lompitrace) will automatically
+  your application via (e.g., via -lompitrace) will automatically
   output to stderr when some MPI functions are invoked:
 
   shell$ cd examples/
@@ -603,9 +603,7 @@ Network Support
   MXM transport.
 
   - "ob1" supports a variety of networks that can be used in
-    combination with each other (per OS constraints; e.g., there are
-    reports that the GM and OpenFabrics kernel drivers do not operate
-    well together):
+    combination with each other:
 
     - OpenFabrics: InfiniBand, iWARP, and RoCE
     - Loopback (send-to-self)
@@ -704,7 +702,7 @@ Open MPI Extensions
     a string that contains what resources a process is bound to.  See
     its man page for more details.
   - cr: Provides routines to access to checkpoint restart routines.
-    See ompi/mpiext/cr/mpiext_cr_c.h for a listing of availble
+    See ompi/mpiext/cr/mpiext_cr_c.h for a listing of available
     functions.
   - cuda: When the library is compiled with CUDA-aware support, it provides
     two things.  First, a macro MPIX_CUDA_AWARE_SUPPORT. Secondly, the
@@ -1046,7 +1044,7 @@ MISCELLANEOUS SUPPORT LIBRARIES
                  installation to use
 
   By default (or if --with-libevent is specified with no VALUE), Open
-  MPI will build and use the copy of libeveny that it has in its
+  MPI will build and use the copy of libevent that it has in its
   source tree.  However, if the VALUE is "external", Open MPI will
   look for the relevant libevent header file and library in default
   compiler / linker locations.  Or, VALUE can be a directory tree
@@ -1412,7 +1410,7 @@ format.  Each of the three numbers has a specific meaning:
     change in the code base and/or end-user functionality, and also
     indicate a break from backwards compatibility.  Specifically: Open
     MPI releases with different major version numbers are not
-    backwards compatibile with each other.
+    backwards compatibale with each other.
 
     CAVEAT: This rule does not extend to versions prior to v1.10.0.
             Specifically: v1.10.x is not guaranteed to be backwards
@@ -1727,7 +1725,7 @@ configure script.  They are not necessary for MPI applications, but
 may be used by applications that use Open MPI's lower layer support
 libraries.
 
-orte:       Open MPI Run-Time Environment applicaions
+orte:       Open MPI Run-Time Environment applications
 opal:       Open Portable Access Layer applications
 
 ===========================================================================
@@ -1845,7 +1843,7 @@ Back-end run-time environment (RTE) component frameworks:
 
 dfs       - Distributed file system
 errmgr    - RTE error manager
-ess       - RTE environment-specfic services
+ess       - RTE environment-specific services
 filem     - Remote file management
 grpcomm   - RTE group communications
 iof       - I/O forwarding
@@ -1874,7 +1872,7 @@ hwloc       - Hardware locality (hwloc) versioning support
 if          - OS IP interface support
 installdirs - Installation directory relocation services
 memchecker  - Run-time memory checking
-memcpy      - Memopy copy support
+memcpy      - Memory copy support
 memory      - Memory management hooks
 mpool       - Memory pooling
 patcher     - Symbol patcher hooks
@@ -1982,7 +1980,7 @@ passed on the mpirun command line will override an environment
 variable; an environment variable will override the system-wide
 defaults.
 
-Each component typically activates itself when relavant.  For example,
+Each component typically activates itself when relevant.  For example,
 the MX component will detect that MX devices are present and will
 automatically be used for MPI communications.  The SLURM component
 will automatically detect when running inside a SLURM job and activate