[PATCH v2] manual: fix spelling typos

[Mike Frysinger <vapier at gentoo dot org>]

I've bracketed the changes to make it easier to pick out.

	enlengthen -> extend
	enlengthened -> extended
	excep[e]tions -> exceptions
	exten[da]ble -> exten[si]ble
	implement[o]r -> implement[e]r
	licen[c]e -> licen[s]e
	optimzed -> optim[i]zed
	overriden -> overrid[d]en
	param[a]ter -> param[e]ter
	signal[l]ed -> signaled
	signal[l]ing -> signaling

Signed-off-by: Mike Frysinger <vapier@gentoo.org>

2012-10-27  Mike Frysinger  <vapier@gentoo.org>

	* manual/arith.texi: Fix spelling typos.
	* manual/contrib.texi: Likewise.
	* manual/crypt.texi: Likewise.
	* manual/filesys.texi: Likewise.
	* manual/llio.texi: Likewise.
	* manual/locale.texi: Likewise.
	* manual/message.texi: Likewise.
	* manual/nss.texi: Likewise.
	* manual/socket.texi: Likewise.
	* manual/stdio.texi: Likewise.
	* manual/string.texi: Likewise.
	* manual/sysinfo.texi: Likewise.
---
v2
	- drop texinfo change
	- fix ChangeLog paths

 manual/arith.texi   | 10 +++++-----
 manual/contrib.texi |  2 +-
 manual/crypt.texi   |  2 +-
 manual/filesys.texi |  2 +-
 manual/llio.texi    |  4 ++--
 manual/locale.texi  |  2 +-
 manual/message.texi | 14 +++++++-------
 manual/nss.texi     |  2 +-
 manual/socket.texi  |  2 +-
 manual/stdio.texi   |  2 +-
 manual/string.texi  |  4 ++--
 manual/sysinfo.texi |  2 +-
 12 files changed, 24 insertions(+), 24 deletions(-)

diff --git a/manual/arith.texi b/manual/arith.texi
index 3f4e56a..6f72b08 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -571,7 +571,7 @@ operation continues with an imprecise small value, or zero if the
 destination precision cannot hold the small exact result.
 
 @item Inexact
-This exception is signalled if a rounded result is not exact (such as
+This exception is signaled if a rounded result is not exact (such as
 when calculating the square root of two) or a result overflows without
 an overflow trap.
 @end table
@@ -801,7 +801,7 @@ may be larger or smaller than the range representable by their return
 type.  These are known as @dfn{domain errors}, @dfn{overflows}, and
 @dfn{underflows}, respectively.  Math functions do several things when
 one of these errors occurs.  In this manual we will refer to the
-complete response as @dfn{signalling} a domain error, overflow, or
+complete response as @dfn{signaling} a domain error, overflow, or
 underflow.
 
 When a math function suffers a domain error, it raises the invalid
@@ -1064,7 +1064,7 @@ occur, you can use the following two functions.
 @comment GNU
 @deftypefun int feenableexcept (int @var{excepts})
 This functions enables traps for each of the exceptions as indicated by
-the parameter @var{except}.  The individual excepetions are described in
+the parameter @var{except}.  The individual exceptions are described in
 @ref{Status bit operations}.  Only the specified exceptions are
 enabled, the status of the other exceptions is not changed.
 
@@ -1076,7 +1076,7 @@ operation was successful, @code{-1} otherwise.
 @comment GNU
 @deftypefun int fedisableexcept (int @var{excepts})
 This functions disables traps for each of the exceptions as indicated by
-the parameter @var{except}.  The individual excepetions are described in
+the parameter @var{except}.  The individual exceptions are described in
 @ref{Status bit operations}.  Only the specified exceptions are
 disabled, the status of the other exceptions is not changed.
 
@@ -1567,7 +1567,7 @@ sign (although not all implementations support it) and this is one of
 the few operations that can tell the difference.
 
 @code{copysign} never raises an exception.
-@c except signalling NaNs
+@c except signaling NaNs
 
 This function is defined in @w{IEC 559} (and the appendix with
 recommended functions in @w{IEEE 754}/@w{IEEE 854}).
diff --git a/manual/contrib.texi b/manual/contrib.texi
index 3052fc1..abc39cf 100644
--- a/manual/contrib.texi
+++ b/manual/contrib.texi
@@ -50,7 +50,7 @@ committee.
 Thomas Bushnell for his contributions to Hurd.
 
 @item
-Liubov Dmitrieva for optimzed string and math functions on x86-64 and
+Liubov Dmitrieva for optimized string and math functions on x86-64 and
 x86.
 
 @item
diff --git a/manual/crypt.texi b/manual/crypt.texi
index ef90590..4d55ce9 100644
--- a/manual/crypt.texi
+++ b/manual/crypt.texi
@@ -48,7 +48,7 @@ to provide a definitive survey of the laws affecting cryptography.
 Instead, this section warns you of some of the known trouble spots; this
 may help you when you try to find out what the laws of your country are.
 
-Some countries require that you have a licence to use, possess, or import
+Some countries require that you have a license to use, possess, or import
 cryptography.  These countries are believed to include Byelorussia,
 Burma, India, Indonesia, Israel, Kazakhstan, Pakistan, Russia, and Saudi
 Arabia.
diff --git a/manual/filesys.texi b/manual/filesys.texi
index 7003f9c..09ef051 100644
--- a/manual/filesys.texi
+++ b/manual/filesys.texi
@@ -770,7 +770,7 @@ of the following categories.  This could be special files, sockets etc.
 The item is a directory.
 @item FTW_NS
 The @code{stat} call failed and so the information pointed to by the
-second paramater is invalid.
+second parameter is invalid.
 @item FTW_DNR
 The item is a directory which cannot be read.
 @item FTW_SL
diff --git a/manual/llio.texi b/manual/llio.texi
index acafed3..4e92e44 100644
--- a/manual/llio.texi
+++ b/manual/llio.texi
@@ -2105,7 +2105,7 @@ by @var{list}.  The operation to be performed is determined by the
 @code{aio_lio_opcode} member in each element of @var{list}.  If this
 field is @code{LIO_READ} a read operation is enqueued, similar to a call
 of @code{aio_read} for this element of the array (except that the way
-the termination is signalled is different, as we will see below).  If
+the termination is signaled is different, as we will see below).  If
 the @code{aio_lio_opcode} member is @code{LIO_WRITE} a write operation
 is enqueued.  Otherwise the @code{aio_lio_opcode} must be @code{LIO_NOP}
 in which case this element of @var{list} is simply ignored.  This
@@ -2389,7 +2389,7 @@ None of the requests from the @var{list} completed in the time specified
 by @var{timeout}.
 @item EINTR
 A signal interrupted the @code{aio_suspend} function.  This signal might
-also be sent by the AIO implementation while signalling the termination
+also be sent by the AIO implementation while signaling the termination
 of one of the requests.
 @item ENOSYS
 The @code{aio_suspend} function is not implemented.
diff --git a/manual/locale.texi b/manual/locale.texi
index 2f10fcd..3dca89f 100644
--- a/manual/locale.texi
+++ b/manual/locale.texi
@@ -401,7 +401,7 @@ as far as the system follows the Unix standards.
 
 Together with the @code{setlocale} function the @w{ISO C} people
 invented the @code{localeconv} function.  It is a masterpiece of poor
-design.  It is expensive to use, not extendable, and not generally
+design.  It is expensive to use, not extensible, and not generally
 usable as it provides access to only @code{LC_MONETARY} and
 @code{LC_NUMERIC} related information.  Nevertheless, if it is
 applicable to a given situation it should be used since it is very
diff --git a/manual/message.texi b/manual/message.texi
index f65123c..bb28717 100644
--- a/manual/message.texi
+++ b/manual/message.texi
@@ -25,7 +25,7 @@ industry decisions and therefore not necessarily based on reasonable
 decisions.
 
 As mentioned above the message catalog handling provides easy
-extendibility by using external data files which contain the message
+extendability by using external data files which contain the message
 translations.  I.e., these files contain for each of the messages used
 in the program a translation for the appropriate language.  So the tasks
 of the message handling functions are
@@ -1485,12 +1485,12 @@ family.  But in two places the string passed into the function would be
 @code{Open}.  The translations might not be the same and therefore we
 are in the dilemma described above.
 
-One solution to this problem is to artificially enlengthen the strings
+One solution to this problem is to artificially extend the strings
 to make them unambiguous.  But what would the program do if no
-translation is available?  The enlengthened string is not what should be
+translation is available?  The extended string is not what should be
 printed.  So we should use a little bit modified version of the functions.
 
-To enlengthen the strings a uniform method should be used.  E.g., in the
+To extend the strings a uniform method should be used.  E.g., in the
 example above the strings could be chosen as
 
 @smallexample
@@ -1527,7 +1527,7 @@ for the Menu entries and therefore contains a @code{|} character.  We
 simply search for the last occurrence of this character and return a
 pointer to the character following it.  That's it!
 
-If one now consistently uses the enlengthened string form and replaces
+If one now consistently uses the extended string form and replaces
 the @code{gettext} calls with calls to @code{sgettext} (this is normally
 limited to very few places in the GUI implementation) then it is
 possible to produce a program which can be internationalized.
@@ -1562,7 +1562,7 @@ with the second part which is:
 @item
 There is no way the C library can contain a version which can work
 everywhere.  The problem is the selection of the character to separate
-the prefix from the actual string in the enlenghtened string.  The
+the prefix from the actual string in the extended string.  The
 examples above used @code{|} which is a quite good choice because it
 resembles a notation frequently used in this context and it also is a
 character not often used in message strings.
@@ -1574,7 +1574,7 @@ why the @file{iso646.h} file exists in @w{ISO C} programming environments).
 @end itemize
 
 There is only one more comment to make left.  The wrapper function above
-require that the translations strings are not enlengthened themselves.
+require that the translations strings are not extended themselves.
 This is only logical.  There is no need to disambiguate the strings
 (since they are never used as keys for a search) and one also saves
 quite some memory and disk space by doing this.
diff --git a/manual/nss.texi b/manual/nss.texi
index 29fa4cc..57bd35a 100644
--- a/manual/nss.texi
+++ b/manual/nss.texi
@@ -515,7 +515,7 @@ here only important to remember that adding another database is
 independent from adding another service because a service need not
 support all databases or lookup functions.
 
-A designer/implementor of a new service is therefore free to choose the
+A designer/implementer of a new service is therefore free to choose the
 databases s/he is interested in and leave the rest for later (or
 completely aside).
 
diff --git a/manual/socket.texi b/manual/socket.texi
index b12c591..89cc1b6 100644
--- a/manual/socket.texi
+++ b/manual/socket.texi
@@ -1292,7 +1292,7 @@ parameters.
 A pointer to the buffer, in which the result is stored, is available in
 @code{*@var{result}} after the function call successfully returned.  If
 an error occurs or if no entry is found, the pointer @code{*@var{result}}
-is a null pointer.  Success is signalled by a zero return value.  If the
+is a null pointer.  Success is signaled by a zero return value.  If the
 function failed the return value is an error number.  In addition to the
 errors defined for @code{gethostbyname} it can also be @code{ERANGE}.
 In this case the call should be repeated with a larger buffer.
diff --git a/manual/stdio.texi b/manual/stdio.texi
index be769a5..a6d3a2c 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -5127,7 +5127,7 @@ Display the message in standard error.
 Display the message on the system console.
 @end vtable
 
-The erroneous piece of the system can be signalled by exactly one of the
+The erroneous piece of the system can be signaled by exactly one of the
 following values which also is bitwise ORed with the
 @var{classification} parameter to @code{fmtmsg}:
 
diff --git a/manual/string.texi b/manual/string.texi
index 2844bc6..b697360 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -2145,7 +2145,7 @@ The GNU version of the @code{basename} function returns the last
 component of the path in @var{filename}.  This function is the preferred
 usage, since it does not modify the argument, @var{filename}, and
 respects trailing slashes.  The prototype for @code{basename} can be
-found in @file{string.h}.  Note, this function is overriden by the XPG
+found in @file{string.h}.  Note, this function is overridden by the XPG
 version, if @file{libgen.h} is included.
 
 Example of using GNU @code{basename}:
@@ -2291,7 +2291,7 @@ that described in @xref{Cryptographic Functions}.
 
 To store or transfer binary data in environments which only support text
 one has to encode the binary data by mapping the input bytes to
-characters in the range allowed for storing or transfering.  SVID
+characters in the range allowed for storing or transferring.  SVID
 systems (and nowadays XPG compliant systems) provide minimal support for
 this task.
 
diff --git a/manual/sysinfo.texi b/manual/sysinfo.texi
index 1733bc3..389c055 100644
--- a/manual/sysinfo.texi
+++ b/manual/sysinfo.texi
@@ -226,7 +226,7 @@ associated data type are declared in the header file
 
 As a bonus, @code{uname} also gives some information identifying the
 particular system your program is running on.  This is the same information
-which you can get with functions targetted to this purpose described in
+which you can get with functions targeted to this purpose described in
 @ref{Host Identification}.
 
 
-- 
1.7.12