about summary refs log tree commit diff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2023-11-08 18:19:08 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2023-11-08 18:20:09 -0800
commitd1dcb565a1fb5829f9476a1438c30eccc4027d04 (patch)
tree08e03b8fdf2997ab01c8f69230e63ec28e70485c
parentf8cfb6836e8d91bb789b2e7fd65338d6f5bd459c (diff)
downloadglibc-d1dcb565a1fb5829f9476a1438c30eccc4027d04.tar.gz
glibc-d1dcb565a1fb5829f9476a1438c30eccc4027d04.tar.xz
glibc-d1dcb565a1fb5829f9476a1438c30eccc4027d04.zip
Fix type typo in “String/Array Conventions” doc
* manual/string.texi (String/Array Conventions):
Fix typo reported by Alejandro Colomar <alx@kernel.org> in:
https://sourceware.org/pipermail/libc-alpha/2023-November/152646.html
-rw-r--r--manual/string.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/manual/string.texi b/manual/string.texi
index 4149d54ee7..6853e6655a 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -178,7 +178,7 @@ beginning with @samp{mem} and @samp{wmem} (such as @code{memcpy} and
 @code{wmemcpy}) and invariably take an argument which specifies the size
 (in bytes and wide characters respectively) of the block of memory to
 operate on.  The array arguments and return values for these functions
-have type @code{void *} or @code{wchar_t}.  As a matter of style, the
+have type @code{void *} or @code{wchar_t *}.  As a matter of style, the
 elements of the arrays used with the @samp{mem} functions are referred
 to as ``bytes''.  You can pass any kind of pointer to these functions,
 and the @code{sizeof} operator is useful in computing the value for the