20 files changed, 76 insertions, 64 deletions
diff --git a/mcon/U/Csym.U b/mcon/U/Csym.U
index 45ff465..f08a6fa 100644
--- a/mcon/U/Csym.U
+++ b/mcon/U/Csym.U
@@ -32,7 +32,7 @@
 ?LINT:use libc
 ?S:csym:
 ?S:	This shell variable is used internally by Configure to check
-?S:	wether a given C symbol is defined or not. A typical use is:
+?S:	whether a given C symbol is defined or not. A typical use is:
 ?S:		set symbol result [-fva] [previous]
 ?S:		eval $csym
 ?S:	That will set result to 'true' if the function [-f], variable [-v]
diff --git a/mcon/U/Inhdr.U b/mcon/U/Inhdr.U
index 72890e6..5ec252d 100644
--- a/mcon/U/Inhdr.U
+++ b/mcon/U/Inhdr.U
@@ -19,7 +19,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit checks wether a set of header files exists or not.
+?X: This unit checks whether a set of header files exists or not.
 ?X:	If the first header is not found, the function tries to locate
 ?X: the next header, and so on, until one is found or there is no
 ?X: more header in the list.
@@ -34,10 +34,10 @@
 ?V:inhdr
 ?S:inhdr:
 ?S:	This shell variable is used internally by Configure to check
-?S:	wether a set of headers exist or not. A typical use is:
+?S:	whether a set of headers exist or not. A typical use is:
 ?S:		set header i_header [ header2 i_header2 ... ]
 ?S:		eval $inhdr
-?S:	That will print a message, saying wether header was found or
+?S:	That will print a message, saying whether header was found or
 ?S:	not and set i_header* accordingly. If the first header is not
 ?S: found, we try the next one, until the list is empty or one is found.
 ?S:.
diff --git a/mcon/U/Inlibc.U b/mcon/U/Inlibc.U
index 36796ea..2aeb8a8 100644
--- a/mcon/U/Inlibc.U
+++ b/mcon/U/Inlibc.U
@@ -28,10 +28,10 @@
 ?V:inlibc
 ?S:inlibc:
 ?S:	This shell variable is used internally by Configure to check
-?S:	wether a given function is defined or not. A typical use is:
+?S:	whether a given function is defined or not. A typical use is:
 ?S:		set function d_func
 ?S:		eval $inlibc
-?S:	That will print a message, saying wether function was found or
+?S:	That will print a message, saying whether function was found or
 ?S:	not and set d_func accordingly.
 ?S:.
 ?T:was tx sym tres td tu var
diff --git a/mcon/U/Trylink.U b/mcon/U/Trylink.U
index d45ffe2..e38e0b2 100644
--- a/mcon/U/Trylink.U
+++ b/mcon/U/Trylink.U
@@ -43,11 +43,11 @@
 ?V:trylink:cyn
 ?S:trylink:
 ?S:	This shell variable is used internally by Configure to check
-?S:	wether a given function is defined or not. A typical use is:
+?S:	whether a given function is defined or not. A typical use is:
 ?S:		create try.c
 ?S:		set d_func [optional cc flags to try in sequence]
 ?S:		eval $trylink
-?S:	That will print a message, saying wether function was found or
+?S:	That will print a message, saying whether function was found or
 ?S:	not and set d_func accordingly.
 ?S:.
 ?T:var file val nparams msg yes no
diff --git a/mcon/U/Typedef.U b/mcon/U/Typedef.U
index ad39117..b321ced 100644
--- a/mcon/U/Typedef.U
+++ b/mcon/U/Typedef.U
@@ -32,7 +32,7 @@
 ?V:typedef
 ?S:typedef:
 ?S:	This shell variable is used internally by Configure to check
-?S:	wether a given typedef is defined or not. A typical use is:
+?S:	whether a given typedef is defined or not. A typical use is:
 ?S:		set typedef val_t default [includes]
 ?S:		eval $typedef
 ?S:	That will return val_t set to default if the typedef was not found,
diff --git a/mcon/U/d_castneg.U b/mcon/U/d_castneg.U
index 517ac1c..8fd67e3 100644
--- a/mcon/U/d_castneg.U
+++ b/mcon/U/d_castneg.U
@@ -27,7 +27,7 @@
 ?MAKE:	-pick add $@ %<
 ?S:d_castneg:
 ?S:	This variable conditionally defines CASTNEG, which indicates
-?S:	wether the C compiler can cast negative float to unsigned.
+?S:	whether the C compiler can cast negative float to unsigned.
 ?S:.
 ?S:castflags:
 ?S:	This variable contains a flag that precise difficulties the
diff --git a/mcon/U/d_scannl.U b/mcon/U/d_scannl.U
index 4f31596..c16952a 100644
--- a/mcon/U/d_scannl.U
+++ b/mcon/U/d_scannl.U
@@ -26,7 +26,7 @@
 ?MAKE:	-pick add $@ %<
 ?S:d_scannl:
 ?S:	This variable conditionally defines SCAN_NL, which indicates
-?S:	wether the C library routines scanf() and friends can deal with
+?S:	whether the C library routines scanf() and friends can deal with
 ?S:	a '\n' in the input correctly. They do most of the time.
 ?S:.
 ?C:SCAN_NL:
diff --git a/mcon/U/i_inttypes.U b/mcon/U/i_inttypes.U
index fb02d0a..c22fa46 100644
--- a/mcon/U/i_inttypes.U
+++ b/mcon/U/i_inttypes.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit looks wether <inttypes.h> is available or not
+?X: This unit looks whether <inttypes.h> is available or not
 ?X:
 ?MAKE:i_inttypes: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_niin.U b/mcon/U/i_niin.U
index e24cc4a..9229f1b 100644
--- a/mcon/U/i_niin.U
+++ b/mcon/U/i_niin.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit looks wether <netinet/in.h> is available or not
+?X: This unit looks whether <netinet/in.h> is available or not
 ?X:
 ?MAKE:i_niin i_sysin: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_sysmman.U b/mcon/U/i_sysmman.U
index 4b3c9db..9521258 100644
--- a/mcon/U/i_sysmman.U
+++ b/mcon/U/i_sysmman.U
@@ -13,7 +13,7 @@
 ?RCS: patch16: created
 ?RCS:
 ?X:
-?X:	Look wether <sys/mman.h> needs to be included.
+?X:	Look whether <sys/mman.h> needs to be included.
 ?X:
 ?MAKE:i_sysmman: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_sysresrc.U b/mcon/U/i_sysresrc.U
index 69f85f1..8e10d49 100644
--- a/mcon/U/i_sysresrc.U
+++ b/mcon/U/i_sysresrc.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X:	Look wether <sys/resource.h> needs to be included
+?X:	Look whether <sys/resource.h> needs to be included
 ?X:
 ?MAKE:i_sysresrc: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_sysselct.U b/mcon/U/i_sysselct.U
index 7ff37a5..2d4bbef 100644
--- a/mcon/U/i_sysselct.U
+++ b/mcon/U/i_sysselct.U
@@ -16,7 +16,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X:	Look wether <sys/select.h> exists
+?X:	Look whether <sys/select.h> exists
 ?X:
 ?MAKE:i_sysselct: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_systimeb.U b/mcon/U/i_systimeb.U
index 38f7853..132718d 100644
--- a/mcon/U/i_systimeb.U
+++ b/mcon/U/i_systimeb.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit looks wether <sys/timeb.h> should be included
+?X: This unit looks whether <sys/timeb.h> should be included
 ?X: or not when using ftime() (for struct timeb definition).
 ?X:
 ?X:	Force looking for <sys/time.h> for struct timeb.
diff --git a/mcon/U/i_systypes.U b/mcon/U/i_systypes.U
index 3d7fddb..eb626ba 100644
--- a/mcon/U/i_systypes.U
+++ b/mcon/U/i_systypes.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X:	Look wether <sys/types.h> needs to be included.
+?X:	Look whether <sys/types.h> needs to be included.
 ?X:
 ?MAKE:i_systypes: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_sysun.U b/mcon/U/i_sysun.U
index b99f736..cfe2cd9 100644
--- a/mcon/U/i_sysun.U
+++ b/mcon/U/i_sysun.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit looks wether <sys/un.h> is available or not
+?X: This unit looks whether <sys/un.h> is available or not
 ?X:
 ?MAKE:i_sysun: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/i_syswait.U b/mcon/U/i_syswait.U
index 20ff974..82c9566 100644
--- a/mcon/U/i_syswait.U
+++ b/mcon/U/i_syswait.U
@@ -13,7 +13,7 @@
 ?RCS: Baseline for dist 3.0 netwide release.
 ?RCS:
 ?X:
-?X: This unit looks wether <sys/wait.h> is available or not
+?X: This unit looks whether <sys/wait.h> is available or not
 ?X:
 ?MAKE:i_syswait: Inhdr
 ?MAKE:	-pick add $@ %<
diff --git a/mcon/U/nis.U b/mcon/U/nis.U
index 06e4c47..7332545 100644
--- a/mcon/U/nis.U
+++ b/mcon/U/nis.U
@@ -165,4 +165,16 @@ case "$passcat" in
 '') passcat=':'
 	$test -f /etc/passwd && passcat='cat /etc/passwd';;
 esac
+case "$hostcat" in
+'') hostcat='cat /etc/hosts';;
+*)  ;;
+esac
+case "$groupcat" in
+'') groupcat='cat /etc/group';;
+*)  ;;
+esac
+case "$passcat" in
+'') passcat='cat /etc/passwd';;
+*)  ;;
+esac
 
diff --git a/mcon/man/mconfig.SH b/mcon/man/mconfig.SH
index e749330..bf49fe9 100755
--- a/mcon/man/mconfig.SH
+++ b/mcon/man/mconfig.SH
@@ -23,7 +23,7 @@ $spitshell >metaconfig.$manext <<!GROK!THIS!
 ''' $Id$
 '''
 '''  Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
-'''  
+'''
 '''  You may redistribute only under the terms of the Artistic Licence,
 '''  as specified in the README file that comes with the distribution.
 '''  You may reuse parts of this distribution only within the terms of
@@ -304,7 +304,7 @@ formats allowed:
 ?X: A contrived example
 ?X:
 ?MAKE:d_one two: three +four Five
-?MAKE:	-pick add \$@ %<
+?MAKE:	\-pick add \$@ %<
 ?Y:DEFAULT
 ?S:d_one:
 ?S:	First shell symbol, conditionally defines ONE.
@@ -365,10 +365,10 @@ of general interest.
 .PP
 Notes for writing .U files:
 .IP * 5
-Always use "rm -f" because there are systems where rm is interactive by
+Always use "rm \-f" because there are systems where rm is interactive by
 default.
 .IP *
-Do not use "set -- ..." because '--' does not work with every shell. Use
+Do not use "set \-\- ..." because '\-\-' does not work with every shell. Use
 "set x ...; shift".
 .IP *
 Do not use "unset ENV" since unset is not fully portable.  Say "ENV=''"
@@ -377,7 +377,7 @@ instead.
 Always use echo " " (with a space) because of Eunice systems.
 .IP *
 Only use \fBtest\fR with \-r, \-w, \-f or \-d since those are the only
-portable switches. In particular, avoid "test -x".
+portable switches. In particular, avoid "test \-x".
 .IP *
 Use only programs that came with V7, so that you know everyone has them.
 .IP *
@@ -417,7 +417,7 @@ Use the \fI\$_o\fR and \fI\$_a\fR variables instead (see Unix.U).
 .IP *
 When doing a compile-link-execute test, always write it like this:
 .Ex
-\$\&cc \$\&ccflags \$\&ldflags try.c -o try \$\&libs
+\$\&cc \$\&ccflags \$\&ldflags try.c \-o try \$\&libs
 .Ef
 because some systems require that linking flags be specified before
 the compiled target (with the exception of trailing linking libraries).
@@ -443,7 +443,7 @@ he is going to use the final product on.
 Metaconfig reserves the following names in your directory, and if you use such
 a name it may get clobbered or have other unforeseen effects:
 .Ex
-.MT/*
+ \.MT/*
 Configure
 Wanted
 Obsolete
@@ -459,9 +459,9 @@ UU/*
 config.sh
 config.h
 .Ef
-'''
-''' O p t i o n s
-'''
+.\"
+.\" O p t i o n s
+.\"
 .SH OPTIONS
 The following options are recognized by \fImetaconfig\fR:
 .TP 15
@@ -514,7 +514,7 @@ not be lost when facing a new distribution.
 .TP
 \fB\-L\fI dir\fR
 Override default library location. Normally only useful for metaconfig
-maintainers to locally use the units being developped instead of the
+maintainers to locally use the units being developed instead of the
 publicly available ones. The \fIdir\fR specified is the one containing the
 units \fIU\fR directory.
 .TP
@@ -548,7 +548,7 @@ If this option is not supplied, any \fI$exclusions_file\fR variable in
 This (long) section is an introduction to \fImetaconfig\fR, in which we will
 learn all the basics. If you already know how to use \fImetaconfig\fR, you
 may safely skip to the next section.
-'''
+.\"
 .SS Overview
 .PP
 Usually when you want to get some source package to compile on a given
@@ -563,8 +563,8 @@ some standard trial, guessing and messing around with system includes and
 types.
 .PP
 However, despite all his talent, the author cannot possibly know that
-some system has a broken system call, or that some sytem structure lacks
-one otherwise standard field, or simply wheter a given include file exists
+some system has a broken system call, or that some system structure lacks
+one otherwise standard field, or simply whether a given include file exists
 or not. And I'm not considering the implicit assumptions, like the type
 returned by the \fImalloc()\fR function or the presence of the \fIrename()\fR
 system call to name a few. But that knowledge is necessary to achieve real
@@ -601,7 +601,7 @@ unit being responsible for defining a small number of shell and/or C
 symbols. Units are assembled together at the final stage, honoring
 the dependency graph (one unit may need the result of several other
 units which are then placed before in the script).
-'''
+.\"
 .SS Symbols
 .PP
 Symbols are the most important thing in the \fImetaconfig\fR world. They
@@ -626,7 +626,7 @@ paragraph could sound. In a C file, you need to include the Configure-produced
 \fIconfig.h\fR file, and you must wrap your shell script or Makefile in a .SH
 file and you may reference the shell symbol only in the variable
 substitution part of that .SH file. More on this later.
-'''
+.\"
 .SS Source Files
 .PP
 Symbols may only appear in a limited set of source files, because
@@ -644,7 +644,7 @@ substitutions apply. Actually, \fIconfig.h\fR is produced by running the
 \fImetaconfig\fR-produced \fIconfig_h.SH\fR file, again using variable
 substitution. So we're going to look at that a little more closely since
 this is the heart of the whole \fIconfiguration\fR scheme...
-'''
+.\"
 .SS Variable Substitution
 .PP
 There is shell construct called \fIhere document\fR which enables a
@@ -661,7 +661,7 @@ unless the identifier is surrounded by single quotes. For instance:
 .Ex
 var='first'
 tar='second'
-echo "--> first here document:"
+echo "\--> first here document:"
 cat <<EOM
 var='\$var'
 tar='\$\&tar'
@@ -685,7 +685,7 @@ echo \$\&tar
 .Ef
 The first here document has its content interpreted whilst the second
 one is output as-is. Both are useful in a .SH script, as we are about to see.
-'''
+.\"
 .SS Using .SH Scripts
 .PP
 A .SH script is usually produced by running the \fIMakeSH\fR script other
@@ -824,7 +824,7 @@ stored as a 64 bits quantity, \fIconfig.sh\fR will set \fIintsize\fR to
 On this machine, the int type is 8 bytes
 .Ef
 which is correct. Congratulations! We have just configured a shell script!!
-'''
+.\"
 .SS Producing config.h
 .PP
 We can now have a look at the way \fIconfig.h\fR is produced out of
@@ -922,7 +922,7 @@ multiple inclusions of this file. Then comes the heart of the file...
 .PP
 It helps to know that \fI\$d_*\fR and \fI\$i_*\fR variables are set to
 either '\fIdefine\fR' or '\fIundef\fR' by \fIConfigure\fR, depending on
-wether a function or an include file is present on the system or not.
+whether a function or an include file is present on the system or not.
 That means the:
 .Ex
 #\$\&d_bcopy HAS_BCOPY /**/
@@ -978,7 +978,7 @@ configured C code, since \fImetaconfig\fR will know that you need
 those symbols and will generate a suitable \fIconfig_h.SH\fR file as
 well as all the necessary code in \fIConfigure\fR to compute a
 proper value for them (by assigning values to associated shell variables).
-'''
+.\"
 .SS Running Metaconfig
 .PP
 Let's focus on the \fImetaconfig\fR program for a while to understand how
@@ -1039,7 +1039,7 @@ required are removed and a second Makefile is generated. This time, we know
 about all the units and their respective orders, optional units having been
 removed and default values computed for their shell symbols. The \fIConfigure\fR
 script can then be generated, along with \fIconfig_h.SH\fR. We're done.
-'''
+.\"
 .SS Conventions
 .PP
 Proper conventions needs to be followed to make the whole process sound.
@@ -1069,7 +1069,7 @@ answer in \fI\$dflt\fR and places the user answer in \fI\$ans\fR. This is
 not documented in this manual page: you have to go and look at the unit
 itself to understand which variables are used and how the unit is to be
 used.
-'''
+.\"
 .SS Using The Glossary
 .PP
 The Glossary file is automatically produced by the \fImakegloss\fR script,
@@ -1084,7 +1084,7 @@ about \fImetaconfig\fR to do so quickly and efficiently. However, never
 forget to properly document your work in the ?S: and ?C: lines, or other
 people will not be able to reuse it. Remember about the time where you
 had only the Glossary and this manual page to get started.
-'''
+.\"
 .SS Conclusion
 .PP
 Now that you know the \fImetaconfig\fR basics, you should read the
@@ -1095,7 +1095,7 @@ commands you are allowed to use.
 .SH REFERENCE
 This section documents the internals of \fImetaconfig\fR, basically the
 unit syntax, the special units you should know about and the hint files.
-'''
+.\"
 .SS General Unit Syntax
 .PP
 A metaconfig unit is divided into two distinct parts. The header section
@@ -1303,7 +1303,7 @@ hints that can be used.
 ?INIT:\fIinitialization code\fR
 The initialization code specified by this line will be loaded at the top
 of the \fIConfigure\fR script provided the unit is needed.
-'''
+.\"
 .SS C Symbol Aliasing
 .PP
 Sometimes it is not possible to rely on \fImetaconfig\fR's own default
@@ -1383,7 +1383,7 @@ It simply tries to compile a sample C program using the \fIconst\fR keyword.
 If it can, then it will define \fI\$\&d_const\fR via the \fI\$\&setvar\fR
 fonction (defined by the \fISetvar.U\fR unit). See the paragraph about
 special units for more details.
-'''
+.\"
 .SS Make Commands
 .PP
 On the ?MAKE: command line, you may write a shell command to be executed as-is
@@ -1448,7 +1448,7 @@ As a side note, \fImetaconfig\fR generates a \fI-cond\fR command internally
 to deal with conditional dependencies. You should not use it by yourself,
 but you will see it if scanning the generated \fIMakefile\fR in the \fI.MT\fR
 directory.
-'''
+.\"
 .SS Hardwired Macros
 .PP
 The following macros are recognized by the \fIwipe\fR command and subsituted
@@ -1491,7 +1491,7 @@ which is replaced at Configure-generation time by the value of \fIvariable\fR
 taken from your \fI.package\fR file. Eventually, the old hardwired macro
 format will disappear, and <\$baserev> will replace <BASEREV> in all the
 supplied units.
-'''
+.\"
 .SS Special Units
 .PP
 The following special units are used to factorize code and provide higher
@@ -1520,7 +1520,7 @@ check whether a given C symbol is defined or not. A typical use is:
 set symbol result [-fva] [previous]
 eval \$\&csym
 .Ef
-That will set the \fIresult\fR variable to 'true' if the 
+That will set the \fIresult\fR variable to 'true' if the
 function [-f],
 variable [-v] or
 array [-a]
@@ -1655,7 +1655,7 @@ argument specifies the file to be located, the second argument is what
 will be returned if the search fails, and the reamining arguments are a
 list of directories where the file is to be searched. For instance:
 .Ex
-dflt=\`./loc sendmail.cf X /usr/lib /var/adm/sendmail /lib\`
+dflt=\`./loc sendmail.cf X /usr/lib /var/lib/sendmail /lib\`
 .Ef
 would set \fI\$dflt\fR to \fIX\fR if no \fIsendmail.cf\fR file was found
 under the listed directories, or something like \fI/usr/lib/sendmail.cf\fR
@@ -1731,7 +1731,7 @@ to an empty string if the prefix changed, to \fI\$var\fR otherwise.
 .TP
 Prefixup.U
 The intent of thit unit is similar to that of Prefixit.U, i.e. it helps
-fixing the default string to accomodate prefix changes. However, the shell
+fixing the default string to accommodate prefix changes. However, the shell
 variable \fI\$prefixup\fR, when evaluated, will only restore ~name expansions,
 should prefix use such an escape mechanism. Use it as:
 .Ex
@@ -1781,7 +1781,7 @@ This unit produces the \fIwhoa\fR script, which emits a warning when the
 its old previous value held in \fI\$was\fR. Upon return, \fI\$td\fR and
 \fI\$tu\fR hold the proper value to \fIdefine\fR or \fIundef\fR the variable.
 See examples in \fIInlibc.U\fR.
-'''
+.\"
 .SS Builtin Pre-processor
 .PP
 Each unit to be included in \fIConfigure\fR is ran through a built-in
@@ -1881,7 +1881,7 @@ done
 .Ef
 and have an extra loop trying two successive values for the \fIs_timezone\fR
 variable, but only if needed.
-'''
+.\"
 .SS Obsolete Symbols
 .PP
 Obsolete symbols are preserved to ease the transition with older
@@ -1895,7 +1895,7 @@ The lifetime for obsolete symbols is one full revision, i.e. they will
 be removed when the next base revision is issued (patch upgrades do not
 count of course). Therefore, it is wise to translate your sources and
 start using the new symbols as soon as possible.
-'''
+.\"
 .SS Configure Hints
 .PP
 It may happen that the internal configuration logic makes the wrong choices.
@@ -1945,7 +1945,7 @@ Note that you don't have to provide \fIall\fR the hints known by
 possible choice. The heuristic tests ran to compute the possible hint
 candidates are flaky. If you have new values or different tests, please send
 them to me...
-'''
+.\"
 .SS Overriding Choices
 .PP
 If you create a \fIconfig.over\fR file in the top level directory,
@@ -1956,7 +1956,7 @@ you a chance to patch the values stored in there.
 This is distinct from the hints approach in that it is a local file, which
 the user is free to create for his own usage. You should not provide such
 a file yourself, but let the user know about this possibility.
-'''
+.\"
 .SS Configure Options
 .PP
 The \fIConfigure\fR script may be called with some options specified on the
@@ -2028,7 +2028,7 @@ possible to use '\fB-U\fI symbol\fR' which will set \fIsymbol\fR to 'undef'.
 Print the version number of the \fImetaconfig\fR that generated this
 .I Configure
 script and exit.
-'''
+.\"
 .SS Running Environment
 Upon starting, \fIConfigure\fR creates a local \fIUU\fR directory and runs
 from there. The directory is removed when Configure ends, but this means
@@ -2057,7 +2057,7 @@ When running \fIConfigure\fR remotely, the .SH files are extracted in the
 build directory, not in the source tree. However, it requires some kind of
 a \fImake\fR support to be able to compile things in a build directory whilst
 the sources lie elsewhere.
-'''
+.\"
 .SS Using Magic Redefinitions
 .PP
 By making use of the \fB\-M\fR switch, some magic remappings may take place
@@ -2077,7 +2077,7 @@ on \fImemcpy()\fR if no \fIbcopy()\fR is available locally, or transform
 bother about the \fIHAS_VFORK\fR symbol.
 .PP
 This configuration magic is documented in the Glossary file.
-'''
+.\"
 .SS Unit Templates
 .PP
 There is a set of unit templates in the \fImetaconfig\fR source directory,
diff --git a/mcon/man/mlint.SH b/mcon/man/mlint.SH
index 8910b88..4f4177a 100755
--- a/mcon/man/mlint.SH
+++ b/mcon/man/mlint.SH
@@ -23,7 +23,7 @@ $spitshell >metalint.$manext <<!GROK!THIS!
 ''' $Id$
 '''
 '''  Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
-'''  
+'''
 '''  You may redistribute only under the terms of the Artistic Licence,
 '''  as specified in the README file that comes with the distribution.
 '''  You may reuse parts of this distribution only within the terms of
@@ -104,7 +104,7 @@ Silent mode.
 .TP
 \fB\-L\fI dir\fR
 Override default library location. Normally only useful for metaconfig
-maintainers to locally check the units being developped instead of the
+maintainers to locally check the units being developed instead of the
 publicly available ones. The \fIdir\fR specified is the one containing the
 units \fIU\fR directory.
 .TP
diff --git a/mcon/man/mxref.SH b/mcon/man/mxref.SH
index 491bf1d..359f959 100755
--- a/mcon/man/mxref.SH
+++ b/mcon/man/mxref.SH
@@ -23,7 +23,7 @@ $spitshell >metaxref.$manext <<!GROK!THIS!
 ''' $Id$
 '''
 '''  Copyright (c) 1991-1997, 2004-2006, Raphael Manfredi
-'''  
+'''
 '''  You may redistribute only under the terms of the Artistic Licence,
 '''  as specified in the README file that comes with the distribution.
 '''  You may reuse parts of this distribution only within the terms of