docs: clarify "legacy" vs. "current"

Use the word "legacy" when referring to MPI-1-specific behavior, and
"current" when comparing to today's behavior.

Signed-off-by: Jeff Squyres <jeff@squyres.com>

Author: jsquyres

docs/man-openmpi/man3/MPI_Type_create_resized.3.rst

@@ -77,7 +77,7 @@ of the data type when used in communication operations, with *count* >
 NOTE
 ----
 
-Use of :ref:`MPI_Type_create_resized` is strongly recommended over the old
+Use of :ref:`MPI_Type_create_resized` is strongly recommended over the legacy
 MPI-1 functions :ref:`MPI_Type_extent` and :ref:`MPI_Type_lb`.
 
 

docs/man-openmpi/man3/MPI_Type_get_contents.3.rst

@@ -118,7 +118,7 @@ arguments are of type ``INTEGER(KIND=MPI_ADDRESS_KIND)``. The call
 ``INTEGER(KIND=MPI_ADDRESS_KIND)``. This is true even if the old MPI-1 calls
 were used. Thus, the location of values returned can be thought of as
 being returned by the C bindings. It can also be determined by examining
-the new MPI-2 calls for data-type constructors for the deprecated MPI-1
+the current MPI calls for datatype constructors for the deprecated MPI-1
 calls that involve addresses.
 
 

docs/man-openmpi/man3/MPI_Type_get_extent.3.rst

@@ -81,7 +81,7 @@ MPI_UNDEFINED.
 NOTE
 ----
 
-Use of :ref:`MPI_Type_get_extent` is strongly recommended over the old MPI-1
+Use of :ref:`MPI_Type_get_extent` is strongly recommended over the legacy MPI-1
 functions :ref:`MPI_Type_extent` and :ref:`MPI_Type_lb`.