docs: trivial: s/--/|mdash|/ in man pages

jsquyres · jsquyres · commit 89dc7a10bb56 · 2023-11-13T15:51:05.000-05:00
No other text or content changes. Signed-off-by: Jeff Squyres <jeff@squyres.com> (cherry picked from commit a57b67b)
diff --git a/docs/building-apps/abi-compatibility.rst b/docs/building-apps/abi-compatibility.rst
@@ -8,7 +8,7 @@ compatibility for the C MPI bindings to the last major Open MPI release. Specifi
 application compiled with Open MPI v4.x can be executed with Open MPI
 |ompi_series| without having to recompile the application.
 
-.. important:: ABI is maintained for *most* of the Fortran MPI bindings, too -- see below for additional information.
+.. important:: ABI is maintained for *most* of the Fortran MPI bindings, too |mdash| see below for additional information.
 
 There are however a few scenarios where an application compiled with
 Open MPI v4.x might not execute correctly with Open MPI 5.0.
diff --git a/docs/developers/prerequisites.rst b/docs/developers/prerequisites.rst
@@ -96,8 +96,8 @@ generate both the HTML version of the documentation (that you are
 reading right now) and the nroff man pages.
 
 Official Open MPI distribution tarballs contain pre-built HTML
-documentation and man pages.  This means that -- similar to the GNU
-Autotools -- end users do not need to have Sphinx installed, but will
+documentation and man pages.  This means that |mdash| similar to the GNU
+Autotools |mdash| end users do not need to have Sphinx installed, but will
 still have both the HTML documentation and man pages installed as part
 of the normal configure / build / install process.
 
diff --git a/docs/developers/rst-for-markdown-expats.rst b/docs/developers/rst-for-markdown-expats.rst
@@ -228,7 +228,7 @@ Comments
         will not be included in the rendered output.
 
         Your comment can even include blank lines.  You terminate a
-        comment -- just like most other things in RST -- by a blank
+        comment |mdash| just like most other things in RST |mdash| by a blank
         line and then outdenting back out to the same column as the
         first ".".
 
diff --git a/docs/developers/source-code.rst b/docs/developers/source-code.rst
@@ -54,7 +54,7 @@ C / C++
   * C99-style mixing declarations are allow allowable (and preferred).
 
 * **ALWAYS** include ``<level>_config.h`` as your first #include file,
-  where ``<level>`` is one of ``ompi``, ``oshmem``, or ``opal`` -- the
+  where ``<level>`` is one of ``ompi``, ``oshmem``, or ``opal`` |mdash| the
   level that you're writing in.  There are very, very few cases where
   this is not true (E.g., some bizarre Windows scenarios).  But in
   99.9999% of cases, this file should be included **first** so that it
@@ -77,7 +77,7 @@ C / C++
   * The GNU Way is to ``#define`` a macro when it is "true" and to
     ``#undef`` it when it is "false".
   * In Open MPI, we **always** ``#define`` a logical macro to be
-    either 0 or 1 -- we never ``#undef`` it.
+    either 0 or 1 |mdash| we never ``#undef`` it.
   * The reason for this is defensive programming: if you are only
     checking if a preprocessor macro is defined (via ``#ifdef FOO`` or
     ``#if defined(FOO)``), you will get no warning when compiling if
diff --git a/docs/features/java.rst b/docs/features/java.rst
@@ -6,7 +6,7 @@ Open MPI Java bindings
 Open MPI |ompi_ver| provides support for Java-based MPI applications.
 
 .. warning:: The Open MPI Java bindings are provided on a
-   "provisional" basis -- i.e., they are not part of the current or
+   "provisional" basis |mdash| i.e., they are not part of the current or
    proposed MPI standards.  Thus, inclusion of Java support is not
    required by the standard.  Continued inclusion of the Java bindings
    is contingent upon active user interest and continued developer
diff --git a/docs/features/ulfm.rst b/docs/features/ulfm.rst
@@ -573,7 +573,7 @@ sign up on the user's mailing list: ulfm+subscribe@googlegroups.com
 
 Because of spam, only subscribers are allowed to post to these lists
 (ensure that you subscribe with and post from exactly the same e-mail
-address -- joe@example.com is considered different than
+address |mdash| joe@example.com is considered different than
 joe@mycomputer.example.com!).  Visit these pages to subscribe to the
 lists: https://groups.google.com/forum/#!forum/ulfm
 
diff --git a/docs/history.rst b/docs/history.rst
@@ -20,13 +20,13 @@ MPI implementation focused on different areas of excellence, we all
 shared the same common core values:
 
 * A full MPI implementation
-* Production quality code -- it has to "just work"
+* Production quality code |mdash| it has to "just work"
 * A desire to explore lots of things that an MPI implementation can do
   that we've never had the time/resources to investigate because we
   are bound to bug fixing, etc.
 
 Hence, we decided to collaborate and pool our resources.  At SC2003,
-we decided to start an entire new code base -- leaving all the cruft
+we decided to start an entire new code base |mdash| leaving all the cruft
 and legacy code of our prior implementations behind.  Take the best,
 leave the rest.  The source tree's first commit was on November 22,
 2003; development work started in earnest on January 5, 2004.  Since
diff --git a/docs/installing-open-mpi/configure-cli-options/installation.rst b/docs/installing-open-mpi/configure-cli-options/installation.rst
@@ -238,7 +238,7 @@ be used with ``configure``:
   Some examples:
 
   #. Default to building all components as static (i.e., as part of
-     the Open MPI core libraries -- no DSOs)::
+     the Open MPI core libraries |mdash| no DSOs)::
 
         shell$ ./configure
 
@@ -304,7 +304,7 @@ be used with ``configure``:
   their Open MPI package, both of which require support libraries
   (``libFOO.so`` and ``libBAR.so``).  If an end user only has BAR
   hardware, they likely only have ``libBAR.so`` available on their
-  systems -- not ``libFOO.so``.  Disabling load errors by default will
+  systems |mdash| not ``libFOO.so``.  Disabling load errors by default will
   prevent the user from seeing potentially confusing warnings about
   the FOO components failing to load because ``libFOO.so`` is not
   available on their systems.
diff --git a/docs/installing-open-mpi/configure-cli-options/misc.rst b/docs/installing-open-mpi/configure-cli-options/misc.rst
@@ -29,7 +29,7 @@ above categories that can be used with ``configure``:
   with different endian representations).  Heterogeneous support is
   disabled by default because it imposes a minor performance penalty.
 
-  .. danger:: The heterogeneous functionality is currently broken --
+  .. danger:: The heterogeneous functionality is currently broken |mdash|
               do not use.
 
 .. _install-wrapper-flags-label:
@@ -40,7 +40,7 @@ above categories that can be used with ``configure``:
 * ``--with-wrapper-ldflags=LDFLAGS``
 * ``--with-wrapper-libs=LIBS``:
   Add the specified flags to the default flags that are used in Open
-  MPI's "wrapper" compilers (e.g., ``mpicc`` -- see below for more
+  MPI's "wrapper" compilers (e.g., ``mpicc`` |mdash| see below for more
   information about Open MPI's wrapper compilers).  By default, Open
   MPI's wrapper compilers use the same compilers used to build Open
   MPI and specify a minimum set of additional flags that are necessary
diff --git a/docs/installing-open-mpi/configure-cli-options/runtime.rst b/docs/installing-open-mpi/configure-cli-options/runtime.rst
@@ -13,7 +13,7 @@ can be used with ``configure``:
   prevents most ``rsh``/``ssh``-based users from needing to modify their
   shell startup files to set the ``PATH`` and/or ``LD_LIBRARY_PATH`` for
   Open MPI on remote nodes.  Note, however, that such users may still
-  desire to set ``PATH`` -- perhaps even in their shell startup files --
+  desire to set ``PATH`` |mdash| perhaps even in their shell startup files |mdash|
   so that executables such as ``mpicc`` and ``mpirun`` can be found
   without needing to type long path names.
 
diff --git a/docs/installing-open-mpi/required-support-libraries.rst b/docs/installing-open-mpi/required-support-libraries.rst
@@ -339,7 +339,7 @@ script deciding the following:
 * The Fortran compiler is ``gfortran`` (which is the
   Homebrew-installed Fortran compiler).
 * There is a suitable system-installed hwloc in ``/usr/local``, which
-  can be found -- by the C compiler/linker -- without specifying any
+  can be found |mdash| by the C compiler/linker |mdash| without specifying any
   additional linker search paths.
 
 The careful reader will realize that the C and Fortran compilers are
@@ -354,8 +354,8 @@ library search paths are different:
 Hence, since the majority of Open MPI's source code base is in C, it
 compiles/links against hwloc successfully.  But when Open MPI's
 Fortran code for the ``mpi_f08`` module is compiled and linked, the
-Homebrew-installed ``gfortran`` -- which does not search
-``/usr/local/lib`` by default -- cannot find ``libhwloc``, and the link
+Homebrew-installed ``gfortran`` |mdash| which does not search
+``/usr/local/lib`` by default |mdash| cannot find ``libhwloc``, and the link
 fails.
 
 There are a few different possible solutions to this issue:
diff --git a/docs/installing-open-mpi/supported-systems.rst b/docs/installing-open-mpi/supported-systems.rst
@@ -59,7 +59,7 @@ interconnects at the time of its release.
 This, unfortunately, does mean that Open MPI removes support for
 networks that are no longer commonly-used in HPC environments.  If you
 still have one of these older interconnects, not all new version of
-Open MPI may support your interconnect -- sorry!  This simply reflects
+Open MPI may support your interconnect |mdash| sorry!  This simply reflects
 the reality of limited development, testing, and maintenance
 resources.
 
diff --git a/docs/launching-apps/scheduling.rst b/docs/launching-apps/scheduling.rst
@@ -96,7 +96,7 @@ while there are still processes to be scheduled, Open MPI will trigger
 an oversubscription condition.
 
 If ``:OVERSUBSCRIBE`` is added as a modifier to the ``--map-by``
-option (e.g., ``mpirun --map-by node:OVERSUBSCRIBE ...`` -- :ref:`see
+option (e.g., ``mpirun --map-by node:OVERSUBSCRIBE ...`` |mdash| :ref:`see
 this section <running-mpi-apps-oversubscribing-label>` for more
 details), Open MPI will continue to loop through the list of nodes
 again and try to schedule one more process to each node until all
diff --git a/docs/launching-apps/troubleshooting.rst b/docs/launching-apps/troubleshooting.rst
@@ -22,7 +22,7 @@ why this can happen.
 
   .. code-block:: c
 
-     /* This is a Linux example -- the issue is similar/the same on other
+     /* This is a Linux example |mdash| the issue is similar/the same on other
         operating systems */
      handle = dlopen("libmpi.so", RTLD_NOW | RTLD_LOCAL);
 
diff --git a/docs/man-openmpi/man1/mpirun.1.rst b/docs/man-openmpi/man1/mpirun.1.rst
@@ -105,8 +105,8 @@ are slightly different than PRRTE's CLI commands.
 
 .. include:: /schizo-ompi-rst-content/schizo-ompi-cli.rstxt
 
-OPTIONS (OLD / HARD-CODED CONTENT -- TO BE AUDITED
---------------------------------------------------
+OPTIONS (OLD / HARD-CODED CONTENT |mdash| TO BE AUDITED
+-------------------------------------------------------
 
 .. admonition:: This is old content
    :class: error
@@ -1548,7 +1548,7 @@ variables.  The ``--mca`` settings similarly override MCA parameters
 set in the ``$OPAL_PREFIX/etc/openmpi-mca-params.conf`` or
 ``$HOME/.openmpi/mca-params.conf`` file.
 
-Unknown ``<key>`` arguments are still set as environment variable --
+Unknown ``<key>`` arguments are still set as environment variable |mdash|
 they are not checked (by mpirun) for correctness.  Illegal or
 incorrect ``<value>`` arguments may or may not be reported |mdash| it
 depends on the specific MCA module.
diff --git a/docs/man-openmpi/man1/ompi-wrapper-compiler.1.rst b/docs/man-openmpi/man1/ompi-wrapper-compiler.1.rst
@@ -137,7 +137,7 @@ link MPI applications that use any/all of the MPI Fortran bindings:
 Open MPI was installed with support for each of these Fortran
 bindings). Specifically: it is no longer necessary to use different
 wrapper compilers for applications that use ``mpif.h``
-vs. applications that use the ``mpi`` module -- just use ``mpifort``
+vs. applications that use the ``mpi`` module |mdash| just use ``mpifort``
 for all Fortran MPI applications.
 
 Note, however, that the Fortran compiler may require additional
diff --git a/docs/man-openmpi/man1/ompi_info.1.rst b/docs/man-openmpi/man1/ompi_info.1.rst
@@ -123,7 +123,7 @@ The three categories are:
    used to tweak MPI application performance. This even includes
    parameters that control resource exhaustion levels (e.g., number of
    free list entries, size of buffers, etc.), and could be considered
-   "correctness" parameters if they're set too low. But, really --
+   "correctness" parameters if they're set too low. But, really |mdash|
    they're tuning parameters.
 
 #. **Open MPI developer**: Parameters in this category either don't
@@ -133,7 +133,7 @@ The three categories are:
 And within each category, there are three sub-categories:
 
 #. **Basic**: This sub-category is for parameters that everyone in
-   this category will want to see -- even less-advanced end users,
+   this category will want to see |mdash| even less-advanced end users,
    application tuners, and new OMPI developers.
 
 #. **Detailed**: This sub-category is for parameters that are
diff --git a/docs/man-openmpi/man3/MPI_Address.3.rst b/docs/man-openmpi/man3/MPI_Address.3.rst
@@ -6,7 +6,7 @@ MPI_Address
 
 .. include_body
 
-:ref:`MPI_Address` |mdash| Gets the address of a location in memory -- |deprecated_favor| :ref:`MPI_Get_address`.
+:ref:`MPI_Address` |mdash| Gets the address of a location in memory |mdash| |deprecated_favor| :ref:`MPI_Get_address`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_Attr_delete.3.rst b/docs/man-openmpi/man3/MPI_Attr_delete.3.rst
@@ -6,7 +6,7 @@ MPI_Attr_delete
 
 .. include_body
 
-:ref:`MPI_Attr_delete` |mdash| Deletes attribute value associated with a key -- |deprecated_favor| :ref:`MPI_Comm_delete_attr`.
+:ref:`MPI_Attr_delete` |mdash| Deletes attribute value associated with a key |mdash| |deprecated_favor| :ref:`MPI_Comm_delete_attr`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_Attr_get.3.rst b/docs/man-openmpi/man3/MPI_Attr_get.3.rst
@@ -6,7 +6,7 @@ MPI_Attr_get
 
 .. include_body
 
-:ref:`MPI_Attr_get` |mdash| Retrieves attribute value by key -- |deprecated_favor| :ref:`MPI_Comm_get_attr`.
+:ref:`MPI_Attr_get` |mdash| Retrieves attribute value by key |mdash| |deprecated_favor| :ref:`MPI_Comm_get_attr`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_Attr_put.3.rst b/docs/man-openmpi/man3/MPI_Attr_put.3.rst
@@ -6,7 +6,7 @@ MPI_Attr_put
 
 .. include_body
 
-:ref:`MPI_Attr_put` |mdash| Stores attribute value associated with a key -- |deprecated_favor| :ref:`MPI_Comm_set_attr`.
+:ref:`MPI_Attr_put` |mdash| Stores attribute value associated with a key |mdash| |deprecated_favor| :ref:`MPI_Comm_set_attr`.
 
 
 
diff --git a/docs/man-openmpi/man3/MPI_Comm_spawn_multiple.3.rst b/docs/man-openmpi/man3/MPI_Comm_spawn_multiple.3.rst
@@ -63,7 +63,7 @@ Fortran 2008 Syntax
 
 INPUT PARAMETERS
 ----------------
-* ``count``: Number of commands (positive integer, significant to MPI only at *root* -- see NOTES).
+* ``count``: Number of commands (positive integer, significant to MPI only at *root* |mdash| see NOTES).
 * ``array_of_commands``: Programs to be executed (array of strings, significant only at *root*).
 * ``array_of_argv``: Arguments for *commands* (array of array of strings, significant only at *root*).
 * ``array_of_maxprocs``: Maximum number of processes to start for each command (array of integers, significant only at *root*).
diff --git a/docs/man-openmpi/man3/MPI_Errhandler_create.3.rst b/docs/man-openmpi/man3/MPI_Errhandler_create.3.rst
@@ -6,7 +6,7 @@ MPI_Errhandler_create
 
 .. include_body
 
-:ref:`MPI_Errhandler_create` |mdash| Creates an MPI-style error handler -- |deprecated_favor| :ref:`MPI_Comm_create_errhandler`.
+:ref:`MPI_Errhandler_create` |mdash| Creates an MPI-style error handler |mdash| |deprecated_favor| :ref:`MPI_Comm_create_errhandler`.
 
 
 
diff --git a/docs/man-openmpi/man3/MPI_Errhandler_get.3.rst b/docs/man-openmpi/man3/MPI_Errhandler_get.3.rst
@@ -6,7 +6,7 @@ MPI_Errhandler_get
 
 .. include_body
 
-:ref:`MPI_Errhandler_get` |mdash| Gets the error handler for a communicator -- |deprecated_favor| :ref:`MPI_Comm_get_errhandler`.
+:ref:`MPI_Errhandler_get` |mdash| Gets the error handler for a communicator |mdash| |deprecated_favor| :ref:`MPI_Comm_get_errhandler`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_Errhandler_set.3.rst b/docs/man-openmpi/man3/MPI_Errhandler_set.3.rst
@@ -6,7 +6,7 @@ MPI_Errhandler_set
 
 .. include_body
 
-:ref:`MPI_Errhandler_set` |mdash| Sets the error handler for a communicator -- |deprecated_favor| :ref:`MPI_Comm_set_errhandler`.
+:ref:`MPI_Errhandler_set` |mdash| Sets the error handler for a communicator |mdash| |deprecated_favor| :ref:`MPI_Comm_set_errhandler`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_File_set_view.3.rst b/docs/man-openmpi/man3/MPI_File_set_view.3.rst
@@ -76,7 +76,7 @@ DESCRIPTION
 -----------
 
 The :ref:`MPI_File_set_view` routine changes the process's view of the data in
-the file -- the beginning of the data accessible in the file through
+the file |mdash| the beginning of the data accessible in the file through
 that view is set to *disp;* the type of data is set to *etype;* and the
 distribution of data to processes is set to *filetype.* In addition,
 :ref:`MPI_File_set_view` resets the independent file pointers and the shared
diff --git a/docs/man-openmpi/man3/MPI_Gather.3.rst b/docs/man-openmpi/man3/MPI_Gather.3.rst
@@ -175,7 +175,7 @@ Example 1: Gather 100 ints from every process in group to root.
 
    MPI_Gather( sendarray, 100, MPI_INT, rbuf, 100, MPI_INT, root, comm);
 
-Example 2: Previous example modified -- only the root allocates memory
+Example 2: Previous example modified |mdash| only the root allocates memory
 for the receive buffer.
 
 .. code-block:: c
diff --git a/docs/man-openmpi/man3/MPI_Group_difference.3.rst b/docs/man-openmpi/man3/MPI_Group_difference.3.rst
@@ -60,11 +60,11 @@ DESCRIPTION
 
 The set-like operations are defined as follows:
 
-* union -- All elements of the first group (group1), followed by all
+* union |mdash| All elements of the first group (group1), followed by all
    elements of second group (group2) that are not in the first group
-* intersect -- all elements of the first group that are also in the
+* intersect |mdash| all elements of the first group that are also in the
    second group, ordered as in first group
-* difference -- all elements of the first group that are not in the
+* difference |mdash| all elements of the first group that are not in the
    second group, ordered as in the first group
 
 Note that for these operations the order of processes in the output
diff --git a/docs/man-openmpi/man3/MPI_Group_intersection.3.rst b/docs/man-openmpi/man3/MPI_Group_intersection.3.rst
@@ -61,11 +61,11 @@ DESCRIPTION
 
 The set-like operations are defined as follows:
 
-* union -- All elements of the first group (group1), followed by all
+* union |mdash| All elements of the first group (group1), followed by all
    elements of second group (group2) not in first.
-* intersect -- all elements of the first group that are also in the
+* intersect |mdash| all elements of the first group that are also in the
    second group, ordered as in first group.
-* difference -- all elements of the first group that are not in the
+* difference |mdash| all elements of the first group that are not in the
    second group, ordered as in the first group.
 
 Note that for these operations the order of processes in the output
diff --git a/docs/man-openmpi/man3/MPI_Group_union.3.rst b/docs/man-openmpi/man3/MPI_Group_union.3.rst
@@ -62,11 +62,11 @@ DESCRIPTION
 
 The set-like operations are defined as follows:
 
- o    union -- All elements of the first group (group1), followed by all elements of second group (group2) not in first.
+ o    union |mdash| All elements of the first group (group1), followed by all elements of second group (group2) not in first.
 
- o    intersect -- all elements of the first group that are also in the second group, ordered as in first group.
+ o    intersect |mdash| all elements of the first group that are also in the second group, ordered as in first group.
 
- o    difference -- all elements of the first group that are not in the second group, ordered as in the first group.
+ o    difference |mdash| all elements of the first group that are not in the second group, ordered as in the first group.
 
 Note that for these operations the order of processes in the output
 group is determined primarily by order in the first group (if possible)
diff --git a/docs/man-openmpi/man3/MPI_Keyval_create.3.rst b/docs/man-openmpi/man3/MPI_Keyval_create.3.rst
@@ -6,7 +6,7 @@ MPI_Keyval_create
 
 .. include_body
 
-:ref:`MPI_Keyval_create` |mdash| Generates a new attribute key -- |deprecated_favor| :ref:`MPI_Comm_create_keyval`.
+:ref:`MPI_Keyval_create` |mdash| Generates a new attribute key |mdash| |deprecated_favor| :ref:`MPI_Comm_create_keyval`.
 
 
 SYNTAX
diff --git a/docs/man-openmpi/man3/MPI_Keyval_free.3.rst b/docs/man-openmpi/man3/MPI_Keyval_free.3.rst
@@ -6,7 +6,7 @@ MPI_Keyval_free
 
 .. include_body
 
-:ref:`MPI_Keyval_free` |mdash| Frees attribute key for communicator cache attribute -- |deprecated_favor| :ref:`MPI_Comm_free_keyval`.
+:ref:`MPI_Keyval_free` |mdash| Frees attribute key for communicator cache attribute |mdash| |deprecated_favor| :ref:`MPI_Comm_free_keyval`.
 
 SYNTAX
 ------
diff --git a/docs/man-openmpi/man3/MPI_Recv_init.3.rst b/docs/man-openmpi/man3/MPI_Recv_init.3.rst
@@ -76,7 +76,7 @@ Creates a persistent communication request for a receive operation. The
 argument *buf* is marked as OUT because the user gives permission to
 write on the receive buffer by passing the argument to :ref:`MPI_Recv_init`.
 
-A persistent communication request is inactive after it is created -- no
+A persistent communication request is inactive after it is created |mdash| no
 active communication is attached to the request.
 
 A communication (send or receive) that uses a persistent request is
diff --git a/docs/man-openmpi/man3/MPI_Request_free.3.rst b/docs/man-openmpi/man3/MPI_Request_free.3.rst
@@ -68,13 +68,13 @@ Once a request is freed by a call to :ref:`MPI_Request_free`, it is not
 possible to check for the successful completion of the associated
 communication with calls to :ref:`MPI_Wait` or :ref:`MPI_Test`. Also, if an error
 occurs subsequently during the communication, an error code cannot be
-returned to the user -- such an error must be treated as fatal.
+returned to the user |mdash| such an error must be treated as fatal.
 Questions arise as to how one knows when the operations have completed
 when using :ref:`MPI_Request_free`. Depending on the program logic, there may
 be other ways in which the program knows that certain operations have
 completed and this makes usage of :ref:`MPI_Request_free` practical. For
 example, an active send request could be freed when the logic of the
-program is such that the receiver sends a reply to the message sent --
+program is such that the receiver sends a reply to the message sent |mdash|
 the arrival of the reply informs the sender that the send has completed
 and the send buffer can be reused. An active receive request should
 never be freed, as the receiver will have no way to verify that the
diff --git a/docs/man-openmpi/man3/MPI_Type_create_hindexed.3.rst b/docs/man-openmpi/man3/MPI_Type_create_hindexed.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_create_struct.3.rst b/docs/man-openmpi/man3/MPI_Type_create_struct.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_extent.3.rst b/docs/man-openmpi/man3/MPI_Type_extent.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_hindexed.3.rst b/docs/man-openmpi/man3/MPI_Type_hindexed.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_hvector.3.rst b/docs/man-openmpi/man3/MPI_Type_hvector.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_indexed.3.rst b/docs/man-openmpi/man3/MPI_Type_indexed.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_lb.3.rst b/docs/man-openmpi/man3/MPI_Type_lb.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_struct.3.rst b/docs/man-openmpi/man3/MPI_Type_struct.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Type_ub.3.rst b/docs/man-openmpi/man3/MPI_Type_ub.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Waitany.3.rst b/docs/man-openmpi/man3/MPI_Waitany.3.rst
diff --git a/docs/man-openmpi/man3/MPI_Waitsome.3.rst b/docs/man-openmpi/man3/MPI_Waitsome.3.rst
diff --git a/docs/man-openshmem/man1/oshmem-wrapper-compiler.1.rst b/docs/man-openshmem/man1/oshmem-wrapper-compiler.1.rst
diff --git a/docs/news/news-v1.x.rst b/docs/news/news-v1.x.rst
diff --git a/docs/news/news-v2.x.rst b/docs/news/news-v2.x.rst
diff --git a/docs/news/news-v4.1.x.rst b/docs/news/news-v4.1.x.rst
diff --git a/docs/release-notes/general.rst b/docs/release-notes/general.rst
diff --git a/docs/validate.rst b/docs/validate.rst

-Original file line number
+Diff line change
 Because of spam, only subscribers are allowed to post to these lists
 (ensure that you subscribe with and post from exactly the same e-mail
 -address -- [email protected] is considered different than
 +address |mdash| [email protected] is considered different than
 [email protected]!).  Visit these pages to subscribe to the
 lists: https://groups.google.com/forum/#!forum/ulfm