[glibc] Fix type typo in “String/Array Conventions” doc

[Paul Eggert <eggert@sourceware.org>]

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d1dcb565a1fb5829f9476a1438c30eccc4027d04

commit d1dcb565a1fb5829f9476a1438c30eccc4027d04
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Wed Nov 8 18:19:08 2023 -0800

    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

Diff:
---
 manual/string.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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