[PATCH 1.5.20] documentation typos

[Nicolas Kaiser]

Some documentation typos.

Cheers, n.
---
 doc/libtool.info |   16 ++++++++--------
 doc/libtool.texi |   16 ++++++++--------
 2 files changed, 16 insertions(+), 16 deletions(-)

diff -urpN libtool-1.5.20.orig/doc/libtool.info libtool-1.5.20/doc/libtool.info
--- libtool-1.5.20.orig/doc/libtool.info        2005-08-31 20:33:39.000000000 
+0200
+++ libtool-1.5.20/doc/libtool.info     2005-12-14 15:52:18.000000000 +0100
@@ -959,10 +959,10 @@ and accepts the following options:
 
 `--mode=MODE'
      Use MODE as the operation mode.  If not specified, an attempt is
-     made to inferr the operation mode from the MODE-ARGS.  Not
+     made to infer the operation mode from the MODE-ARGS.  Not
      specifying the MODE is currently deprecated, as there are too many
      situations where it is not possible to guess.  Future versions of
-     Libtool will require that MODE be explicity set.
+     Libtool will require that MODE be explicitly set.
 
      MODE must be set to one of the following:
 
@@ -1028,7 +1028,7 @@ linker flags with `-Wl,FLAG' and `-Xlink
 compile specific flags using `-Wc,FLAG' and `-Xcompiler FLAG'.
 
    If both PIC and non-PIC objects are being built, libtool will
-normally supress the compiler output for the PIC object compilation to
+normally suppress the compiler output for the PIC object compilation to
 save showing very similar, if not identical duplicate output for each
 object.  If the `-no-suppress' option is given in compile mode, libtool
 will show the compiler output for both objects.
@@ -2788,7 +2788,7 @@ multi-threaded environment.
      function which will be called at the start of parts of the libltdl
      implementation code which require a mutex lock.
 
-     Because libltdl is inherantly recursive, it is important that the
+     Because libltdl is inherently recursive, it is important that the
      locking mechanism employed by these callback functions are
      reentrant, or else strange problems will occur.
 
@@ -2810,14 +2810,14 @@ multi-threaded environment.
      The type of a matching callback function to retrieve the last
      stored error message from thread local storage.
 
-     When regeistered correctly this function will be used by
+     When registered correctly this function will be used by
      `lt_dlerror())' from all threads to retrieve error messages for the
      client.
 
  -- Function: int lt_dlmutex_register (lt_dlmutex_lock *LOCK,
           lt_dlmutex_unlock *UNLOCK, lt_dlmutex_set_error *SETERROR,
           lt_dlmutex_geterror *GETERROR)
-     Use this function to register one of each of function ttypes
+     Use this function to register one of each of function types
      described above in preparation for multi-threaded use of libltdl.
      All arguments must be valid non-`NULL' function addresses, or else
      all `NULL' to return to single threaded operation.
@@ -3010,7 +3010,7 @@ The following types are defined in `ltdl
  -- Type: int lt_module_close (lt_user_data LOADER_DATA,
           lt_module MODULE)
      The type of the unloader function for a user defined module loader.
-     Implementatation of such a function should attempt to release any
+     Implementation of such a function should attempt to release any
      resources tied up by the MODULE module, and then unload it from
      memory.  If the function fails for some reason, set the error
      message with `lt_dlseterror' and return non-zero.
@@ -3149,7 +3149,7 @@ loaders:
 
  -- Function: int lt_dlseterror (int ERRORCODE)
      When writing your own module loaders, you should use this function
-     to raise errors so that they are propogated through the
+     to raise errors so that they are propagated through the
      `lt_dlerror' interface. All of the standard errors used by libltdl
      are declared in `ltdl.h', or you can add more of your own with
      `lt_dladderror'.  This function returns 0 on success.
diff -urpN libtool-1.5.20.orig/doc/libtool.texi libtool-1.5.20/doc/libtool.texi
--- libtool-1.5.20.orig/doc/libtool.texi        2005-08-31 20:25:28.000000000 
+0200
+++ libtool-1.5.20/doc/libtool.texi     2005-12-14 15:54:14.000000000 +0100
@@ -1085,10 +1085,10 @@ displayed.
 
 @item address@hidden
 Use @var{mode} as the operation mode.  If not specified, an attempt is
-made to inferr the operation mode from the @var{mode-args}.  Not specifying
+made to infer the operation mode from the @var{mode-args}.  Not specifying
 the @var{mode} is currently deprecated, as there are too many situations
 where it is not possible to guess.  Future versions of Libtool will require
-that @var{mode} be explicity set.
+that @var{mode} be explicitly set.
 
 @var{mode} must be set to one of the following:
 
@@ -1157,7 +1157,7 @@ You can also pass compile specific flags
 and @samp{-Xcompiler @var{flag}}.
 
 If both PIC and non-PIC objects are being built, libtool will normally
-supress the compiler output for the PIC object compilation to save
+suppress the compiler output for the PIC object compilation to save
 showing very similar, if not identical duplicate output for each
 object.  If the @samp{-no-suppress} option is given in compile mode,
 libtool will show the compiler output for both objects.
@@ -3086,7 +3086,7 @@ This is the type of a function pointer h
 which will be called at the start of parts of the libltdl implementation
 code which require a mutex lock.
 
-Because libltdl is inherantly recursive, it is important that the
+Because libltdl is inherently recursive, it is important that the
 locking mechanism employed by these callback functions are reentrant, or
 else strange problems will occur.
 @end deftypefn
@@ -3110,13 +3110,13 @@ error message passed in thread local sto
 The type of a matching callback function to retrieve the last stored
 error message from thread local storage.
 
-When regeistered correctly this function will be used by
+When registered correctly this function will be used by
 @code{lt_dlerror())} from all threads to retrieve error messages for the
 client.
 @end deftypefn
 
 @deftypefn {Function} int lt_dlmutex_register (@w{lt_dlmutex_lock 
address@hidden, @w{lt_dlmutex_unlock address@hidden, @w{lt_dlmutex_set_error 
address@hidden, @w{lt_dlmutex_geterror address@hidden)}
-Use this function to register one of each of function ttypes described
+Use this function to register one of each of function types described
 above in preparation for multi-threaded use of libltdl.  All arguments
 must be valid address@hidden function addresses, or else all
 @code{NULL} to return to single threaded operation.
@@ -3319,7 +3319,7 @@ return @code{NULL}, and set the error me
 
 @deftypefn {Type} int lt_module_close (@w{lt_user_data @var{loader_data},} 
@w{lt_module @var{module}})
 The type of the unloader function for a user defined module loader.
-Implementatation of such a function should attempt to release
+Implementation of such a function should attempt to release
 any resources tied up by the @var{module} module, and then unload it
 from memory.  If the function fails for some reason, set the error
 message with @code{lt_dlseterror} and return non-zero.
@@ -3481,7 +3481,7 @@ if (myerror < 0)
 
 @deftypefun int lt_dlseterror (@w{int @var{errorcode}})
 When writing your own module loaders, you should use this function to
-raise errors so that they are propogated through the @code{lt_dlerror}
+raise errors so that they are propagated through the @code{lt_dlerror}
 interface. All of the standard errors used by libltdl are declared in
 @file{ltdl.h}, or you can add more of your own with
 @code{lt_dladderror}.  This function returns 0 on success.