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, 8 insertions, 8 deletions

diff --git a/bin/kill/kill.1 b/bin/kill/kill.1
index 71e3fc41882..20389e0ab88 100644
--- a/bin/kill/kill.1
+++ b/bin/kill/kill.1
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: kill.1,v 1.32 2009/01/06 23:29:03 jmc Exp $
+.\"	$OpenBSD: kill.1,v 1.33 2009/01/06 23:56:18 jmc Exp $
 .\"	$NetBSD: kill.1,v 1.8 1995/09/07 06:30:26 jtc Exp $
 .\"
 .\" Copyright (c) 1980, 1990, 1993
@@ -130,13 +130,6 @@ A signal number of 0
 .Pq Li kill \-0 pid
 checks the validity of a certain PID, to see if it exists.
 An exit code of 0 means that the specified process exists.
-.Pp
-.Nm
-also exists as a built-in to
-.Xr csh 1
-and
-.Xr ksh 1 ,
-though with a different syntax.
 .Sh EXAMPLES
 Forcibly terminate process ID 1234:
 .Pp
@@ -161,6 +154,13 @@ The
 utility is compliant with the
 .St -p1003.1-2004
 specification.
+.Pp
+.Nm
+also exists as a built-in to
+.Xr csh 1
+and
+.Xr ksh 1 ,
+though with a different syntax.
 .Sh HISTORY
 A
 .Nm