Unify wording for LC_CTYPE in ENVIRONMENT:

* Consistently use "character encoding locale" as suggested by stsp@.
* Resolve various gratuitious wording variations.
OK jmc@.

1 files changed, 9 insertions, 4 deletions

diff --git a/usr.bin/uniq/uniq.1 b/usr.bin/uniq/uniq.1
index d7e275372e2..1c3f10cad8d 100644
--- a/usr.bin/uniq/uniq.1
+++ b/usr.bin/uniq/uniq.1
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: uniq.1,v 1.18 2015/12/19 10:21:01 schwarze Exp $
+.\"	$OpenBSD: uniq.1,v 1.19 2016/10/24 13:46:58 schwarze Exp $
 .\"	$NetBSD: uniq.1,v 1.5 1994/12/06 07:51:15 jtc Exp $
 .\"
 .\" Copyright (c) 1991, 1993
@@ -33,7 +33,7 @@
 .\"
 .\"     @(#)uniq.1	8.1 (Berkeley) 6/6/93
 .\"
-.Dd $Mdocdate: December 19 2015 $
+.Dd $Mdocdate: October 24 2016 $
 .Dt UNIQ 1
 .Os
 .Sh NAME
@@ -117,10 +117,15 @@ denotes the standard input or the standard output
 .Sh ENVIRONMENT
 .Bl -tag -width LC_CTYPE
 .It Ev LC_CTYPE
-The character set
+The character encoding
 .Xr locale 1 .
-Determines which groups of bytes are treated as characters
+It decides which byte sequences form characters
 and which characters are considered blank.
+If unset or set to
+.Qq C ,
+.Qq POSIX ,
+or an unsupported value, each byte is treated as a character,
+and only space and tab are considered blank.
 .El
 .Sh EXIT STATUS
 .Ex -std uniq