[PATCH 08/14] man/tset.1: Slightly recast.

[G. Branden Robinson]

Also protect file name literals from hyphenation.
---
 man/tset.1 | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/man/tset.1 b/man/tset.1
index a1220771..a8387eae 100644
--- a/man/tset.1
+++ b/man/tset.1
@@ -85,9 +85,9 @@ .SS tset - initialization
 .PP
 3. (BSD systems only.) The terminal type associated with the standard
 error output device in the \fI/etc/ttys\fP file.
-(On System\-V-like Unices and systems using that convention,
+(On System\ V hosts and systems using that convention,
 \fBgetty\fP(1) does this job by setting
-\fITERM\fP according to the type passed to it by \fI/etc/inittab\fP.)
+\fITERM\fP according to the type passed to it by \fI\%/etc/inittab\fP.)
 .PP
 4. The default terminal type, \*(``unknown\*('',
 is not suitable for curses applications.
@@ -326,12 +326,14 @@ .SH PORTABILITY
 In fact, the commonly-used \fBreset\fP utility
 is always an alias for \fBtset\fP.
 .PP
-The \fB@TSET@\fP utility provides for backward-compatibility with BSD
-environments (under most modern Unices, \fB/etc/inittab\fP and \fBgetty\fP(1)
-can set \fITERM\fP appropriately for each dial-up line;
-this obviates what was \fB@TSET@\fP's most important use).
-This implementation behaves like 4.4BSD
-\fBtset\fP, with a few exceptions specified here.
+The \fB\%@TSET@\fP utility provides backward compatibility with BSD
+environments;
+under most modern Unices,
+\fI\%/etc/inittab\fP and \fBgetty\fP(1) can set \fITERM\fP appropriately
+for each dial-up line,
+obviating what was \fB\%@TSET@\fP's most important use.
+This implementation behaves like 4.4BSD \fBtset\fP,
+with a few exceptions we shall consider now.
 .PP
 A few options are different
 because the \fI\%TERMCAP\fP variable
-- 
2.30.2

signature.asc
Description: PGP signature