Input file is alsaucm.1 Output from "mandoc -T lint alsaucm.1": (shortened list) 1 input text line longer than 80 bytes: ALSA Use Case Interf... 1 input text line longer than 80 bytes: The master use case ... 1 input text line longer than 80 bytes: Use Case Interface: ... 1 input text line longer than 80 bytes: files. An audio use ... 6 skipping paragraph macro: sp after SH 2 whitespace at end of input line Remove trailing space with: sed -e 's/ *$//' -.-. Output from "test-groff -mandoc -t -ww -z alsaucm.1": (shortened list) 2 trailing space in the line Remove trailing space with: sed -e 's/ *$//' -.-. Show if generated from reStructuredText Who is actually generating this man page? Debian or upstream? Is the generating software out of date? 1:.\" Man page generated from reStructuredText. -.-. Remove space characters (whitespace) at the end of lines. Use "git apply ... --whitespace=fix" to fix extra space issues, or use global configuration "core.whitespace". Number of lines affected is 2 -.-. Remove space in the first column, if not indented. Use ".in +n" and ".in" to end it; ".nf" and ".fi" to end it, for an extra indention. alsaucm.1:40: from the command line. alsaucm.1:237: -.-. Strings longer than 3/4 of a standard line length (80) Use "\:" to split the string at the end of an output line, for example a long URL (web address) 39 Interface 149 ALSA Use Case Interface 237 285 Use Case Interface: -.-. Add a "\&" (or a comma (Oxford comma)) after "e.g." and "i.e.", or use English words (man-pages(7)). Abbreviation points should be marked as such and protected against being interpreted as an end of sentence, if they are not, and that independent of the current place on the line. 59:The verb describes the use case action i.e. a phone call, listening to music, 61:and playback hardware i.e. headphones, phone handset, bluetooth headset, etc. 216:supported use cases, e.g. -.-. Wrong distance between sentences in the input file. Separate the sentences and subordinate clauses; each begins on a new line. See man-pages(7) ("Conventions for source file layout") and "info groff" ("Input Conventions"). The best procedure is to always start a new sentence on a new line, at least, if you are typing on a computer. Remember coding: Only one command ("sentence") on each (logical) line. E-mail: Easier to quote exactly the relevant lines. Generally: Easier to edit the sentence. Patches: Less unaffected text. Search for two adjacent words is easier, when they belong to the same line, and the same phrase. The amount of space between sentences in the output can then be controlled with the ".ss" request. Mark a final abbreviation point as such by suffixing it with "\&". Some sentences (etc.) do not begin on a new line. Split (sometimes) lines after a punctuation mark; before a conjunction. N.B. The number of lines affected can be too large to be in a patch. Lines with only one (or two) space(s) between sentences could be split, so latter sentences begin on a new line. Use #!/usr/bin/sh sed -e '/^\./n' \ -e 's/$[[:alpha:]]$\. */\1.\n/g' $1 to split lines after a sentence period. Check result with the difference between the formatted outputs. See also the attachment "general.bugs" 57:files. An audio use case can be defined by a \fBverb\fP and \fBdevice\fP parameter. 60:recording a conversation etc. The device describes the physical audio capture -.-. Split lines longer than 80 characters into two or more lines. Appropriate break points are the end of a sentence and a subordinate clause; after punctuation marks. Add "\:" to split the string for the output, "\" in the source. Line 57, length 83 files. An audio use case can be defined by a \fBverb\fP and \fBdevice\fP parameter. Line 114, length 81 \fB_devices[/{verb}]\fP \- get list of supported devices (in pair device+comment) Line 116, length 87 \fB_modifiers[/{verb}]\fP \- get list of supported modifiers (in pair modifier+comment) Line 137, length 82 \fB_conflictingdevs/{modifier}|{device}[/{verb}]\fP \- list of conflicting devices Line 149, length 87 ALSA Use Case Interface Line 212, length 91 The master use case files for each supported sound card are in \fB/usr/share/alsa/ucm\fP\&. Line 285, length 88 Use Case Interface: -.-. Put a parenthetical sentence, phrase on a separate line, if not part of a code. See man-pages(7), item "semantic newline". alsaucm.1:38:alsaucm (ALSA Use Case Manager) is a program to use the ALSA Use Case alsaucm.1:79:batch mode (use \fB\(aq\-\(aq\fP for the stdin input) alsaucm.1:112:\fB_verbs\fP \- get verb list (in pair verb+comment) alsaucm.1:114:\fB_devices[/{verb}]\fP \- get list of supported devices (in pair device+comment) alsaucm.1:116:\fB_modifiers[/{verb}]\fP \- get list of supported modifiers (in pair modifier+comment) -.-. No need for '\&' to be in front of a period (.), if there is a character in front of it. Remove with "sed -e 's/\\&\././g'". 95:valid names are sound card names as listed in \fB/usr/share/alsa/ucm\fP\&. 212:The master use case files for each supported sound card are in \fB/usr/share/alsa/ucm\fP\&. 234:\fB/usr/share/alsa/ucm/PandaBoard/hifi\fP\&. -.-. Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z ": an.tmac::30: style: .TH missing fourth argument; consider package/project name and version (e.g., "groff 1.23.0") an.tmac::40: style: 1 leading space(s) on input line an.tmac::237: style: 1 leading space(s) on input line troff::237: warning: trailing space in the line troff::285: warning: trailing space in the line -.-. Spelling: switche -> switch -.- Generally: Split (sometimes) lines after a punctuation mark; before a conjunction.