[src/trunk]: src/lib/libc/stdlib Whitespace improvements.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/e6b31529204c
branches:  trunk
changeset: 782272:e6b31529204c
user:      wiz <wiz%NetBSD.org@localhost>
date:      Wed Oct 24 22:56:27 2012 +0000

description:
Whitespace improvements.

diffstat:

 lib/libc/stdlib/alloca.3 |  9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)

diffs (32 lines):

diff -r 3fceed469e77 -r e6b31529204c lib/libc/stdlib/alloca.3
--- a/lib/libc/stdlib/alloca.3  Wed Oct 24 22:25:49 2012 +0000
+++ b/lib/libc/stdlib/alloca.3  Wed Oct 24 22:56:27 2012 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: alloca.3,v 1.15 2012/10/24 22:25:49 christos Exp $
+.\"    $NetBSD: alloca.3,v 1.16 2012/10/24 22:56:27 wiz Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
 .\"    The Regents of the University of California.  All rights reserved.
@@ -73,10 +73,11 @@
 .Fn alloca
 function is not part of any C standard and its use is not portable.
 .It
-The 
+The
 .Fn alloca
 function should be supplied by the compiler because the compiler is allowed to
-make assumptions about the stack and frame pointers. The libc
+make assumptions about the stack and frame pointers.
+The libc
 .Fn alloca
 implementation cannot account for those assumptions.
 While there is a
@@ -100,7 +101,7 @@
 Since
 .Fn alloca
 modifies the stack at runtime and the stack usage of each function frame
-cannot be predicted, it makes many compiler security features 
+cannot be predicted, it makes many compiler security features
 (such as
 .Xr cc 1
 .Fl fstack-protector )