aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2018-08-20 12:27:39 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2018-08-20 14:45:20 +0200
commita12b305997925ca321e7a0d1fc2afb2db1c00b13 (patch)
treefd55d537c186aa6b0c53a31fc195927096b90c38
parenta6425049fa3a95a8f3b7fc12a6f6f00bc3c687a4 (diff)
downloadman-pages-a12b305997925ca321e7a0d1fc2afb2db1c00b13.tar.gz
strcpy.3: Use "destination" consistently (instead of "target" sometimes)
Reported-by: Frank Theile <ftheile@grundfos.com> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man3/strcpy.34
1 files changed, 2 insertions, 2 deletions
diff --git a/man3/strcpy.3 b/man3/strcpy.3
index 02f7bfaa14..f80b5fcf57 100644
--- a/man3/strcpy.3
+++ b/man3/strcpy.3
@@ -146,7 +146,7 @@ One valid (and intended) use of
.BR strncpy ()
is to copy a C string to a fixed-length buffer
while ensuring both that the buffer is not overflowed
-and that unused bytes in the target buffer are zeroed out
+and that unused bytes in the destination buffer are zeroed out
(perhaps to prevent information leaks if the buffer is to be
written to media or transmitted to another process via an
interprocess communication technique).
@@ -195,7 +195,7 @@ but it copies at most
bytes to
.IR dest ,
always adds a terminating null byte,
-and does not pad the target with (further) null bytes.
+and does not pad the destination with (further) null bytes.
This function fixes some of the problems of
.BR strcpy ()
and