[src/trunk]: src/lib/libc/string Grammar

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

details:   https://anonhg.NetBSD.org/src/rev/554feea11d5d
branches:  trunk
changeset: 346832:554feea11d5d
user:      sevan <sevan%NetBSD.org@localhost>
date:      Thu Aug 04 16:36:45 2016 +0000

description:
Grammar

diffstat:

 lib/libc/string/memset.3 |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (21 lines):

diff -r 520e05412d6a -r 554feea11d5d lib/libc/string/memset.3
--- a/lib/libc/string/memset.3  Thu Aug 04 16:22:40 2016 +0000
+++ b/lib/libc/string/memset.3  Thu Aug 04 16:36:45 2016 +0000
@@ -30,7 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"     from: @(#)memset.3     8.1 (Berkeley) 6/4/93
-.\"    $NetBSD: memset.3,v 1.12 2013/06/24 07:56:49 wiz Exp $
+.\"    $NetBSD: memset.3,v 1.13 2016/08/04 16:36:45 sevan Exp $
 .\"
 .Dd June 23, 2013
 .Dt MEMSET 3
@@ -64,7 +64,7 @@
 Note that the compiler may optimize away a call to
 .Fn memset
 if it can prove that the string will not be used by the program again,
-for example if it is allocated on the stack and about to out of scope.
+for example if it is allocated on the stack and about to go out of scope.
 If you want to guarantee that zeros are written to memory, for example
 to sanitize a buffer holding a cryptographic secret, use
 .Xr explicit_memset 3 .