Changes to manual page

mach/mantra/int/em.1

@@ -1,10 +1,10 @@
 .\" $Header$
-.TH EM 1ACK
+.TH EM 1 "$Revision$"
 .ad
 .SH NAME
 em \- calling program for em interpreters
 .SH SYNOPSIS
-em [-t] [+fcp] [loadfile [args ... ...] ]
+\fBem\fP [-t] [+fcp] [loadfile [args ... ...] ]
 .SH DESCRIPTION
 The loadfile ("e.out" if not specified) is opened to read the first 8 word header.
 The format of this header is explained in e.out(5).
@@ -75,7 +75,7 @@ source line flow data
 last lines executed
 .PD
 .SH "SEE ALSO"
-\fIack\fP(1ACK),
+\fIack\fP(1),
 .SH BUGS
 Most error messages are self explanatory.
 If runtime flags are turned on it is advisable to try again

mach/pdp/int/em.1

@@ -1,10 +1,10 @@
 .\" $Header$
-.TH EM 1ACK
+.TH EM 1 "$Revision$"
 .ad
 .SH NAME
 em \- calling program for em interpreters
 .SH SYNOPSIS
-em [-t] [+fcp] [loadfile [args ... ...] ]
+\fBem\fP [-t] [+fcp] [loadfile [args ... ...] ]
 .SH DESCRIPTION
 The loadfile ("e.out" if not specified) is opened to read the first 8 word header.
 The format of this header is explained in e.out(5).
@@ -28,18 +28,18 @@ an estimate of the number of memory cycles used per source line.
 This option is expensive in time as well as in memory space.
 The result tables made at run time are dumped onto a file named
 em_runinf. This file is converted to human readable format
-by the program eminform(1ACK) which writes the profiling information
+by the program eminform(1) which writes the profiling information
 on a file called em_profile.
 .IP f
 maintain a bit map of all source lines that have been executed.
-This map is written also onto the file em_runinf and can be interpreted by eminform(1ACK) which writes in this case the file em_flow.
+This map is written also onto the file em_runinf and can be interpreted by eminform(1) which writes in this case the file em_flow.
 This option is almost free in time and space.
 .IP c
 count line usage in tables that
 contains for every source line the number of times it
 was entered.
 These tables are also written onto em_runinf.
-Eminform(1ACK) can be used to convert this information into the
+Eminform(1) can be used to convert this information into the
 file em_count.
 Cheap in time, expensive in memory space.
 .PP
@@ -50,7 +50,7 @@ directory ~em/lib/em22/em_????
 If the interpreter exits with a non-zero exit status, then the line numbers
 of the 64 last executed source lines are dumped on the file
 em_runinf
-in the current directory. Eminform(1ACK) writes this information
+in the current directory. Eminform(1) writes this information
 on the human readable file em_last.
 .SH "FILES"
 .IP ~em/lib/em22/em_???? 35
@@ -67,11 +67,10 @@ source line flow data
 last lines executed
 .PD
 .SH "SEE ALSO"
-eminform(1ACK), ack(1ACK),
+eminform(1), ack(1),
 .SH BUGS
 Most error messages are self explanatory.
 The interpreter stops in case of lack of space with an error
 message SEGVIO stack overflow.
 If runtime flags are turned on it is advisable to try again
 with the default options.
-Bugs should be reported to Evert Wattel.

mach/pdp/int/eminform.1

@@ -1,15 +1,15 @@
 .\" $Header$
 .tr ~
-.TH EMINFORM 1ACK
+.TH EMINFORM 1 "$Revision$"
 .ad
 .SH NAME
 eminform \- converts runtime information of interpreted em to
 human readable form.
 .SH SYNOPSIS
-eminform
+\fBeminform\fP
 .SH DESCRIPTION
-The EM interpreter, em(1ACK), has several debugging features built in.
-They can be activated by flag options to em(1ACK).
+The EM interpreter, em(1), has several debugging features built in.
+They can be activated by flag options to em(1).
 The EM interpreter collects the information while it runs the program.
 When the program is terminated, the interpreter dumps this information onto
 a file called em_runinf.
@@ -42,7 +42,7 @@ failed".
 .SH FILES
 em_runinf, em_last, em_flow, em_count, em_profile
 .SH "SEE ALSO"
-ack(1ACK), em(1ACK).
+ack(1), em(1).
 .SH BUGS
 If an entire procedure is not touched, the the file name in
 which this procedure occured is unknown.