Another round of man page cleanups from Debian mantainer Manuel

Prinz. Many thanks! This commit was SVN r23445.
2010-07-20 14:07:18 +00:00 · 2010-07-20 14:07:18 +00:00 · 64cb8f5d7f
--- a/ompi/mca/crcp/ompi_crcp.7in
+++ b/ompi/mca/crcp/ompi_crcp.7in
@ -8,8 +8,8 @@
 .\" **************************
 .SH NAME
 .
-Open MPI MCA Checkpoint/Restart Coordination Protocol (CRCP) Framework \- Overview of Open MPI's CRCP 
-framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
+OMPI_CRCP \- Open MPI MCA Checkpoint/Restart Coordination Protocol (CRCP) Framework:
+Overview of Open MPI's CRCP framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
 .
 .\" **************************
 .\"    Description Section
--- a/ompi/mpi/man/man3/MPI_Comm_split.3in
+++ b/ompi/mpi/man/man3/MPI_Comm_split.3in
@ -35,7 +35,7 @@ color
 Control of subset assignment (nonnegative integer).
 .TP 1i
 key
-Control of rank assigment (integer).
+Control of rank assignment (integer).

 .SH OUTPUT PARAMETERS
 .ft R
--- a/ompi/mpi/man/man3/MPI_Grequest_start.3in
+++ b/ompi/mpi/man/man3/MPI_Grequest_start.3in
@ -135,7 +135,7 @@ In C++, the cancel function is
               bool \fIcomplete\fP);
 .fi
 .sp
-The \fIcancel_fn\fP function is invoked to start the cancelation of a generalized request. It is called by MPI_Request_cancel(request). MPI passes to the callback function complete=true if MPI_Grequest_complete has already been called on the request, and complete=false otherwise. 
+The \fIcancel_fn\fP function is invoked to start the cancellation of a generalized request. It is called by MPI_Request_cancel(request). MPI passes to the callback function complete=true if MPI_Grequest_complete has already been called on the request, and complete=false otherwise.

 .SH FORTRAN 77 NOTES
 .ft R
--- a/ompi/mpi/man/man3/MPI_Intercomm_create.3in
+++ b/ompi/mpi/man/man3/MPI_Intercomm_create.3in
@ -26,7 +26,7 @@ MPI_INTERCOMM_CREATE(\fILOCAL_COMM, LOCAL_LEADER, PEER_COMM,
 Intercomm Intracomm::Create_intercomm(int \fIlocal_leader\fP, const 
 	Comm& \fIpeer_comm\fP, int \fIremote_leader\fP, int \fItag\fP) const

-.SH INPUT PARAMTERS
+.SH INPUT PARAMETERS
 .ft R
 .TP 1i
 local_comm
--- a/ompi/mpi/man/man3/MPI_Keyval_create.3in
+++ b/ompi/mpi/man/man3/MPI_Keyval_create.3in
@ -76,7 +76,7 @@ Fortran; MPI_NULL_COPY_FN is a function that does nothing other than return flag
 .SH NOTES
 Key values are global (available for any and all communicators).
 .sp
-There are subtle differences between C and Fortran that require that the copy_fn be written in the same language that MPI_Keyval_create is called from. This should not be a problem for most users; only programers using both Fortran and C in the same program need to be sure that they follow this rule. 
+There are subtle differences between C and Fortran that require that the copy_fn be written in the same language that MPI_Keyval_create is called from. This should not be a problem for most users; only programmers using both Fortran and C in the same program need to be sure that they follow this rule.
 .sp
 Even though both formal arguments attribute_val_in
 and attribute_val_out are of type void*, their usage differs. The C copy function is passed by MPI in attribute_val_in the value of the attribute, and in attribute_val_out the address of the attribute, so as to allow the function to return the (new) attribute value. The use of type void* for both is to avoid messy type casts.  
--- a/opal/mca/crs/opal_crs.7in
+++ b/opal/mca/crs/opal_crs.7in
@ -14,8 +14,8 @@
 .\" **************************
 .SH NAME
 .
-Open PAL MCA Checkpoint/Restart Service (CRS) \- Overview of Open PAL's CRS 
-framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#. 
+OPAL_CRS \- Open PAL MCA Checkpoint/Restart Service (CRS): Overview of Open PAL's
+CRS framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#.
 .
 .\" **************************
 .\"    Description Section
--- a/opal/tools/opal-checkpoint/opal-checkpoint.1in
+++ b/opal/tools/opal-checkpoint/opal-checkpoint.1in
@ -27,7 +27,7 @@ program their respective tools should be used.
 .SH SYNOPSIS
 .
 .B opal-checkpoint
-.R [ options ]
+.B [ options ]
 .B <PID>
 .
 .\" **************************
--- a/opal/tools/opal-restart/opal-restart.1in
+++ b/opal/tools/opal-restart/opal-restart.1in
@ -27,7 +27,7 @@ program their respective tools should be used.
 .SH SYNOPSIS
 .
 .B opal-restart
-.R [ options ]
+.B [ options ]
 .B <SNAPSHOT HANDLE>
 .
 .\" **************************
@ -63,7 +63,7 @@ The location of the local snapshot reference.
 .TP
 .B -s | --self
 Restart this process using the \fIself\fR CRS component. This component is a
-special case, all other CRS components are automaticly detected.
+special case, all other CRS components are automatically detected.
 .
 .
 .TP
--- a/orte/mca/filem/orte_filem.7in
+++ b/orte/mca/filem/orte_filem.7in
@ -13,8 +13,8 @@
 .\" **************************
 .SH NAME
 .
-Open RTE MCA File Management (FileM) Framework \- Overview of Open RTE's FileM 
-framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
+ORTE_FILEM \- Open RTE MCA File Management (FileM) Framework: Overview of Open RTE's
+FileM framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
 .
 .\" **************************
 .\"    Description Section
--- a/orte/mca/snapc/orte_snapc.7in
+++ b/orte/mca/snapc/orte_snapc.7in
@ -13,8 +13,8 @@
 .\" **************************
 .SH NAME
 .
-Open RTE MCA Snapshot Coordination (SnapC) Framework \- Overview of Open RTE's SnapC 
-framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
+ORTE_SNAPC \- Open RTE MCA Snapshot Coordination (SnapC) Framework: Overview of
+Open RTE's SnapC framework, and selected modules.  #PACKAGE_NAME# #PACKAGE_VERSION#
 .
 .\" **************************
 .\"    Description Section
--- a/orte/tools/orte-checkpoint/orte-checkpoint.1in
+++ b/orte/tools/orte-checkpoint/orte-checkpoint.1in
@ -28,7 +28,7 @@ identical behavior.
 .SH SYNOPSIS
 .
 .B ompi-checkpoint
-.R [ options ]
+.B [ options ]
 .B <PID_OF_MPIRUN>
 .
 .\" **************************
--- a/orte/tools/orte-iof/orte-iof.1in
+++ b/orte/tools/orte-iof/orte-iof.1in
@ -27,7 +27,7 @@ identical behavior.
 .SH SYNOPSIS
 .
 .B ompi-iof
-.R [ options ]
+.B [ options ]
 .
 .\" **************************
 .\"    Options Section
--- a/orte/tools/orte-ps/orte-ps.1in
+++ b/orte/tools/orte-ps/orte-ps.1in
@ -28,7 +28,7 @@ identical behavior.
 .SH SYNOPSIS
 .
 .B ompi-ps
-.R [ options ]
+.B [ options ]
 .
 .\" **************************
 .\"    Options Section
--- a/orte/tools/orte-restart/orte-restart.1in
+++ b/orte/tools/orte-restart/orte-restart.1in
@ -28,7 +28,7 @@ identical behavior.
 .SH SYNOPSIS
 .
 .B ompi-restart
-.R [ options ]
+.B [ options ]
 .B <GLOBAL SNAPSHOT HANDLE>
 .
 .\" **************************
--- a/orte/tools/orterun/orterun.1in
+++ b/orte/tools/orterun/orterun.1in
@ -715,7 +715,7 @@ in a round-robin fashion.
 The \fI-nolocal\fP option prevents any processes from being mapped onto the
 local host (in this case node aa).  While \fImpirun\fP typically consumes
 few system resources, \fI-nolocal\fP can be helpful for launching very
-large jobs where \fImpirun\fP may actually need to use noticable amounts
+large jobs where \fImpirun\fP may actually need to use noticeable amounts
 of memory and/or processing time.
 .
 .PP
--- a/orte/util/hostfile/orte_hosts.7in
+++ b/orte/util/hostfile/orte_hosts.7in
@ -11,7 +11,8 @@
 .\" **************************
 .SH NAME
 .
-OpenRTE Hostfile and HOST Behavior \- Overview of OpenRTE's support for user-supplied hostfiles and comma-delimited lists of hosts
+ORTE_HOSTS \- OpenRTE Hostfile and HOST Behavior: Overview of OpenRTE's support for user-supplied
+hostfiles and comma-delimited lists of hosts
 .
 .\" **************************
 .\"    Description Section