diff --git a/tools/wmc/wmc.man.in b/tools/wmc/wmc.man.in
index e5eb3172320..890f71690fd 100644
--- a/tools/wmc/wmc.man.in
+++ b/tools/wmc/wmc.man.in
@@ -1,9 +1,9 @@
-.\" -*- nroff -*-
 .TH WMC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual"
 .SH NAME
 wmc \- Wine Message Compiler
 .SH SYNOPSIS
-.BI "wmc " "[options] " "[inputfile]"
+.B wmc
+.RI [ options ]\ [ inputfile ]
 .SH DESCRIPTION
 .B wmc
 compiles messages from
@@ -11,15 +11,15 @@ compiles messages from
 into FormatMessage[AW] compatible format encapsulated in a resourcescript
 format.
 .B wmc
-outputs the data either in a standard \fB.bin\fR formatted binary
+outputs the data either in a standard \fI.bin\fR formatted binary
 file, or can generated inline resource data.
 .PP
 .B wmc
-takes only one \fBinputfile\fR as argument (see \fBBUGS\fR). The
-\fBinputfile\fR normally has extension \fB.mc\fR. The messages are read from
+takes only one \fIinputfile\fR as argument (see \fBBUGS\fR). The
+\fIinputfile\fR normally has extension \fI.mc\fR. The messages are read from
 standard input if no inputfile is given. If the outputfile is not specified
-with \fI-o\fR, then \fBwmc\fR will write the output to \fBinputfile.{rc,h}\fR.
-The outputfile is named \fBwmc.tab.{rc,h}\fR if no inputfile was given.
+with \fB-o\fR, then \fBwmc\fR will write the output to \fIinputfile.{rc,h}\fR.
+The outputfile is named \fIwmc.tab.{rc,h}\fR if no inputfile was given.
 .SH OPTIONS
 .TP
 .BI \-B\  x
@@ -55,7 +55,7 @@ Set the output format. Supported formats are \fBrc\fR (the default),
 .BI \-P\  directory
 Enable the generation of resource translations based on po files
 loaded from the specified directory. That directory must follow the
-gettext convention, in particular in must contain one .po file for
+gettext convention, in particular in must contain one \fI.po\fR file for
 each language, and a LINGUAS file listing the available languages.
 .TP
 .B \-u
@@ -74,30 +74,30 @@ Print version end exit.
 Enable pedantic warnings.
 .SH EXTENSIONS
 The original syntax is extended to support codepages more smoothly. Normally,
-codepages are based on the DOS\-codepage from the language setting. The
+codepages are based on the DOS codepage from the language setting. The
 original syntax only allows the destination codepage to be set. However, this
 is not enough for non\-DOS systems which do not use unicode source-files.
 .PP
-A new keyword \fICodepages\fR is introduced to set both input and output
+A new keyword \fBCodepages\fR is introduced to set both input and output
 codepages to anything one wants for each language. The syntax is similar to
 the other constructs:
 .PP
 Codepages '=' '(' language '=' cpin ':' cpout ... ')'
 .PP
 The \fIlanguage\fR is the numerical language\-ID or the alias set with
-LanguageNames. The input\-codepage \fIcpin\fR and output\-codepage
-\fIcpout\fR are the numerical codepage\-IDs. There can be multiple mapping
+LanguageNames. The input codepage \fIcpin\fR and output codepage
+\fIcpout\fR are the numerical codepage IDs. There can be multiple mappings
 within the definition and the definition may occur more than once.
 .SH AUTHORS
 .B wmc
 was written by Bertho A. Stultiens.
 .SH BUGS
-The message compiler should be able to have multiple inputfiles and combine
-them into one outputfile. This would enable the splitting of languages into
+The message compiler should be able to have multiple input files and combine
+them into one output file. This would enable the splitting of languages into
 separate files.
 .PP
 Unicode detection of the input is suboptimal, to say the least. It should
-recognize byte\-order\-marks (BOM) and decide what to do.
+recognize byte order marks (BOM) and decide what to do.
 .PP
 Decimal output is completely lacking. Don't know whether it should be
 implemented because it is a, well, non-informative format change. It is