kill.2: Small improvements to text on historical rules for permissions

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

1 files changed, 4 insertions, 3 deletions

diff --git a/man2/kill.2 b/man2/kill.2
index b843366a..c840cce7 100644
--- a/man2/kill.2
+++ b/man2/kill.2
@@ -96,6 +96,7 @@ In the case of
 .B SIGCONT
 it suffices when the sending and receiving
 processes belong to the same session.
+(Historically, the rules were different; see NOTES.)
 .SH RETURN VALUE
 On success (at least one signal was sent), zero is returned.
 On error, \-1 is returned, and
@@ -150,11 +151,11 @@ to send a signal to another process.
 .\" In the 0.* kernels things chopped and changed quite
 .\" a bit - MTK, 24 Jul 02
 In kernels 1.0 to 1.2.2, a signal could be sent if the
-effective user ID of the sender matched that of the receiver,
-or the real user ID of the sender matched that of the receiver.
+effective user ID of the sender matched effective user ID of the target,
+or the real user ID of the sender matched the real user ID of the target.
 From kernel 1.2.3 until 1.3.77, a signal could be sent if the
 effective user ID of the sender matched either the real or effective
-user ID of the receiver.
+user ID of the target.
 The current rules, which conform to POSIX.1-2001, were adopted
 in kernel 1.3.78.
 .SH BUGS