i saw the previous was wrong as soon as i committed it: put the

built-in blurb in STANDARDS; we did once have a COMPATIBILITY section
which we merged with STANDARDS, so i think this is appropriate. it
certainly feels better than adding single sentences randomly to the
end of text bodies.

1 files changed, 6 insertions, 6 deletions

diff --git a/bin/test/test.1 b/bin/test/test.1
index e07b20ecc85..0edc9ba4f34 100644
--- a/bin/test/test.1
+++ b/bin/test/test.1
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: test.1,v 1.24 2009/01/06 23:43:08 jmc Exp $
+.\"	$OpenBSD: test.1,v 1.25 2009/01/06 23:56:18 jmc Exp $
 .\"	$NetBSD: test.1,v 1.6 1995/03/21 07:04:03 cgd Exp $
 .\"
 .\" Copyright (c) 1991, 1993
@@ -291,11 +291,6 @@ True if
 .Ar expression
 is true.
 .El
-.Pp
-.Nm
-also exists as a built-in to
-.Xr ksh 1 ,
-though with a different syntax.
 .Sh GRAMMAR AMBIGUITY
 The
 .Nm
@@ -341,3 +336,8 @@ The primaries
 and
 .Cm \*(Gt
 are extensions to that specification.
+.Pp
+.Nm
+also exists as a built-in to
+.Xr ksh 1 ,
+though with a different syntax.