Close 2831, which noted that the man page is confusing. I have edited

it slightly differently than Mike originally suggested after
consulting with him and others.

share/man/man3/end.3

@@ -1,4 +1,4 @@
-.\"	$NetBSD: end.3,v 1.5 1996/03/01 00:17:49 jtc Exp $
+.\"	$NetBSD: end.3,v 1.6 1996/10/16 17:20:30 perry Exp $
 .\"
 .\" Copyright (c) 1986
 .\"	The Regents of the University of California.  All rights reserved.
@@ -33,7 +33,7 @@
 .\"
 .\"	@(#)end.3	6.4 (Berkeley) 1/24/94
 .\"
-.Dd January 24, 1994
+.Dd October 16, 1996
 .Dt END 3
 .Os
 .Sh NAME
@@ -46,21 +46,38 @@
 .Vt extern etext;
 .Vt extern edata;
 .Sh DESCRIPTION
-The global variables
+The globals
 .Va end , etext
 and
 .Va edata
-correspond to the
+are program segment end addresses.
-the next address following 
+.Pp
-the end of the text segment,
+.Va etext
-the end of initialized data segment and 
+is the first address after the end of the text segment.
-the end of the data segment
+.Pp
-.Pq Tn BSS .
+.Va edata
+is the first address after the end of the initialized data segment.
+.Pp
+.Va end
+is the first address after the end of the data segment
+.Pq Tn BSS
+when the program is loaded.  Use the
+.Xr sbrk 2
+.\".Fn sbrk 0
+system call with zero as its argument to find the current end of the
+data segment.
 .Sh SEE ALSO
-.Xr brk 2 ,
+.Xr sbrk 2 ,
-.Xr malloc 3
+.Xr malloc 3 ,
+.Xr a.out 5
 .Sh HISTORY
-A
+An
 .Nm end
-manual appeared in
+manual page appeared in
 .At v6 .
+.Sh BUGS
+Traditionally, no variable existed that pointed to the start of the
+text segment because the text segment always started at address
+zero. Although it is no longer valid to make this assumption, no
+variable similar to the ones documented above exists to point to the
+start of the text segment.