summary refs log tree commit diff
path: root/manual
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-05-30 09:07:13 +0000
committerUlrich Drepper <drepper@redhat.com>1999-05-30 09:07:13 +0000
commit0ea554bf8158e381c067062b011f12368c036b8f (patch)
treef27a9be78d5f9700562de6a2512974f2a0c94ea2 /manual
parentfc0a2d72e5d12276e97f6b581a54561c239872f8 (diff)
downloadglibc-0ea554bf8158e381c067062b011f12368c036b8f.tar.gz
glibc-0ea554bf8158e381c067062b011f12368c036b8f.tar.xz
glibc-0ea554bf8158e381c067062b011f12368c036b8f.zip
Update.
1999-05-30  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* manual/stdio.texi: Fix some typos.
Diffstat (limited to 'manual')
-rw-r--r--manual/stdio.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/manual/stdio.texi b/manual/stdio.texi
index 9cf4c9fb68..8c6c009c4c 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -1620,7 +1620,7 @@ In practice, it is often easier just to use @code{asprintf}, below.
 @strong{Attention:} In the GNU C library version 2.0 the return value
 is the number of characters stored, not including the terminating null.
 If this value equals @code{@var{size} - 1}, then there was not enough
-space in @var{s} for all the output.  This change was neccessary with
+space in @var{s} for all the output.  This change was necessary with
 the adoption of snprintf by ISO C9x.
 @end deftypefun
 
@@ -2211,7 +2211,7 @@ width.  The value is @code{'0'} if the @samp{0} flag was specified, and
 Now let's look at how to define the handler and arginfo functions
 which are passed as arguments to @code{register_printf_function}.
 
-@strong{Compatibility Note:} The interface change in the GNU libc
+@strong{Compatibility Note:} The interface changed in the GNU libc
 version 2.0.  Previously the third argument was of type
 @code{va_list *}.
 
@@ -4353,7 +4353,7 @@ form.  The string must contain two fields, separated by a colon
 produced no output since the class with the numeric value @code{6} is
 not defined.  Although a class with numeric value @code{5} is also not
 defined by default, the call the @code{addseverity} introduces it and
-the second call to @code{fmtmsg} produces the above outout.
+the second call to @code{fmtmsg} produces the above output.
 
 When we change the environment of the program to contain
 @code{SEV_LEVEL=XXX,6,NOTE} when running it we get a different result: