This is the mail archive of the glibc-cvs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

GNU C Library master sources branch master updated. glibc-2.24-240-g5455692


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  5455692aaf604e68d974524f18fc7bbcc97598f2 (commit)
       via  be20861940d4415ce2e7d047b4bb7206f54bf171 (commit)
       via  6d2857d35053fe117a49c73c06d22627b8ca38e3 (commit)
       via  b55a155f005366b5a6c886a2e4c57707b341b619 (commit)
       via  ae996b9f39750ec2ad9808b7a13f09135833cd12 (commit)
       via  8e52276ef42434493936d851c201bc6d01e36c9a (commit)
       via  a309449484161647ac93278706adb90086e05e30 (commit)
       via  db5e4e881f25e2adff96f070e5c97f1a27e5abe4 (commit)
       via  b8867dabdf8193ca49ddc2ee5bb617b0a39e183f (commit)
       via  d80cf4a6be1e913b4c9d1f64772ff2bb4e3391af (commit)
       via  61547c480f25f224fb6847d52b6d3555b9906f98 (commit)
       via  9e302f97d4e4f61935e9d4e7d3175bf70578274c (commit)
       via  d72457974ddff7a4f73969246b87fe184840d40e (commit)
       via  9cbcfebd024344e9be096869f08ee5474b881cbb (commit)
       via  954cbda0faae0f8e5d47b3a536ef37d8fb2c2626 (commit)
       via  16c7d1ec26ecf4cbd3a128a23cf2a8ab495a89b8 (commit)
       via  a96ce75c8ed589573e4fa1295c16c61f06bac336 (commit)
       via  d3e22d596db768cfa0282176467fcf1c2e286560 (commit)
       via  9269924c829e766ce43f8b2cf7460d622522b2a9 (commit)
       via  e4fd1876e91bca446115edc40de0d03d00dd7483 (commit)
       via  60843ffbc2bb732ceea98673b8a6d39748d96e4a (commit)
       via  56e74aef9ca5a25735fdef78ef9fefe5f6ae990b (commit)
       via  dc40b233526bb97b120636ad37f3b0f5d168e732 (commit)
       via  b57dd24684173a707c682ce9f249d549df5a66d8 (commit)
       via  4ffa3672e174534916e2ec27fd2cfed4dcc70b22 (commit)
       via  9739d2d501123ad2be48057a33c9f6b610a9c95e (commit)
       via  c703cd7abbdbe7847562cebb48a1c5cca57dde63 (commit)
      from  ba4e688461a0e3171a6c515040ec9200319070b6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=5455692aaf604e68d974524f18fc7bbcc97598f2

commit 5455692aaf604e68d974524f18fc7bbcc97598f2
Author: Siddhesh Poyarekar <siddhesh@sourceware.org>
Date:   Thu Oct 6 12:36:25 2016 +0530

    Manual typos: System Databases and Name Service Switch
    
           * manual/nss.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 88c83f6..34f3bf4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,9 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
+	    Siddhesh Poyarekar  <siddhesh@sourceware.org>
+
+	* manual/nss.texi: Fix typos in the manual.
+
+2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
 	* manual/contrib.texi: Fix typos in the manual.
 
diff --git a/manual/nss.texi b/manual/nss.texi
index e6bfd96..058b9ae 100644
--- a/manual/nss.texi
+++ b/manual/nss.texi
@@ -12,7 +12,7 @@ Network Information Service (NIS) and the Domain Name Service (DNS))
 became popular, and were hacked into the C library, usually with a fixed
 search order.
 
-@Theglibc{} contains a cleaner solution of this problem.  It is
+@Theglibc{} contains a cleaner solution to this problem.  It is
 designed after a method used by Sun Microsystems in the C library of
 @w{Solaris 2}.  @Theglibc{} follows their name and calls this
 scheme @dfn{Name Service Switch} (NSS).
@@ -46,7 +46,7 @@ The modules can be updated separately.
 The C library image is smaller.
 @end enumerate
 
-To fulfill the first goal above the ABI of the modules will be described
+To fulfill the first goal above, the ABI of the modules will be described
 below.  For getting the implementation of a new service right it is
 important to understand how the functions in the modules get called.
 They are in no way designed to be used by the programmer directly.
@@ -106,7 +106,7 @@ There will be some more added later (@code{automount}, @code{bootparams},
 @cindex @file{nsswitch.conf}
 Somehow the NSS code must be told about the wishes of the user.  For
 this reason there is the file @file{/etc/nsswitch.conf}.  For each
-database this file contain a specification how the lookup process should
+database, this file contains a specification of how the lookup process should
 work.  The file could look like this:
 
 @example
@@ -141,7 +141,7 @@ the reaction on lookup result like @code{[NOTFOUND=return]}.
 The above example file mentions five different services: @code{files},
 @code{db}, @code{dns}, @code{nis}, and @code{nisplus}.  This does not
 mean these
-services are available on all sites and it does also not mean these are
+services are available on all sites and neither does it mean these are
 all the services which will ever be available.
 
 In fact, these names are simply strings which the NSS code uses to find
@@ -323,8 +323,8 @@ and the default value for the three databases above is
 @code{compat [NOTFOUND=return] files}.
 
 For all other databases the default value is
-@code{nis [NOTFOUND=return] files}.  This solution give the best
-chance to be correct since NIS and file based lookup is used.
+@code{nis [NOTFOUND=return] files}.  This solution gives the best
+chance to be correct since NIS and file based lookups are used.
 
 @cindex optimizing NSS
 A second point is that the user should try to optimize the lookup
@@ -360,7 +360,7 @@ interested in this topic should read about Dynamic Linking.
 @subsection The Naming Scheme of the NSS Modules
 
 @noindent
-The name of each function consist of various parts:
+The name of each function consists of various parts:
 
 @quotation
        _nss_@var{service}_@var{function}
@@ -393,7 +393,7 @@ functions.  I.e., if the user would call the @code{gethostbyname_r}
 function this also would end in the above function.  For all user
 interface functions the C library maps this call to a call to the
 reentrant function.  For reentrant functions this is trivial since the
-interface is (nearly) the same.  For the non-reentrant version The
+interface is (nearly) the same.  For the non-reentrant version the
 library keeps internal buffers which are used to replace the user
 supplied buffer.
 
@@ -423,7 +423,7 @@ not starting with @file{lib} but don't tell this to anybody.}
 Now we know about the functions contained in the modules.  It is now
 time to describe the types.  When we mentioned the reentrant versions of
 the functions above, this means there are some additional arguments
-(compared with the standard, non-reentrant version).  The prototypes for
+(compared with the standard, non-reentrant versions).  The prototypes for
 the non-reentrant and reentrant versions of our function above are:
 
 @smallexample
@@ -475,7 +475,7 @@ necessary the source code should be examined to learn about the details.
 
 In case the interface function has to return an error it is important
 that the correct error code is stored in @code{*@var{errnop}}.  Some
-return status value have only one associated error code, others have
+return status values have only one associated error code, others have
 more.
 
 @multitable @columnfractions .3 .2 .50
@@ -506,7 +506,7 @@ These are proposed values.  There can be other error codes and the
 described error codes can have different meaning.  @strong{With one
 exception:} when returning @code{NSS_STATUS_TRYAGAIN} the error code
 @code{ERANGE} @emph{must} mean that the user provided buffer is too
-small.  Everything is non-critical.
+small.  Everything else is non-critical.
 
 In statically linked programs, the main application and NSS modules do
 not share the same thread-local variable @code{errno}, which is the
@@ -667,7 +667,7 @@ This function simply closes all files which are still open or removes
 buffer caches.  If there are no files or buffers to remove this is again
 a simple noop.
 
-There normally is no return value different to @var{NSS_STATUS_SUCCESS}.
+There normally is no return value other than @var{NSS_STATUS_SUCCESS}.
 
 @item enum nss_status _nss_@var{database}_get@var{db}ent_r (@var{STRUCTURE} *result, char *buffer, size_t buflen, int *errnop)
 Since this function will be called several times in a row to retrieve
@@ -701,7 +701,7 @@ more entries.  When the last entry was read it should return
 @code{NSS_STATUS_NOTFOUND}.  When the buffer given as an argument is too
 small for the data to be returned @code{NSS_STATUS_TRYAGAIN} should be
 returned.  When the service was not formerly initialized by a call to
-@code{_nss_@var{DATABASE}_set@var{db}ent} all return value allowed for
+@code{_nss_@var{DATABASE}_set@var{db}ent} all return values allowed for
 this function can also be returned here.
 
 @item enum nss_status _nss_@var{DATABASE}_get@var{db}by@var{XX}_r (@var{PARAMS}, @var{STRUCTURE} *result, char *buffer, size_t buflen, int *errnop)
@@ -712,17 +712,17 @@ interface functions.  All arguments given to the non-reentrant version
 are here described by @var{PARAMS}.
 
 The result must be stored in the structure pointed to by @var{result}.
-If there is additional data to return (say strings, where the
+If there are additional data to return (say strings, where the
 @var{result} structure only contains pointers) the function must use the
-@var{buffer} or length @var{buflen}.  There must not be any references
+@var{buffer} of length @var{buflen}.  There must not be any references
 to non-constant global data.
 
 The implementation of this function should honor the @var{stayopen}
 flag set by the @code{set@var{DB}ent} function whenever this makes sense.
 
-Before the function returns the implementation should store the value of
-the local @var{errno} variable in the variable pointed to be
-@var{errnop}.  This is important to guarantee the module working in
+Before the function returns, the implementation should store the value of
+the local @var{errno} variable in the variable pointed to by
+@var{errnop}.  This is important to guarantee the module works in
 statically linked programs.
 
 Again, this function takes an additional last argument for the

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=be20861940d4415ce2e7d047b4bb7206f54bf171

commit be20861940d4415ce2e7d047b4bb7206f54bf171
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:30:03 2016 +0530

    Manual typos: Contributors to
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/contrib.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 39aa215..88c83f6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/contrib.texi: Fix typos in the manual.
+
 	* manual/maint.texi: Fix typos in the manual.
 
 	* manual/install.texi: Fix typos in the manual.
diff --git a/manual/contrib.texi b/manual/contrib.texi
index c1b0245..c1cea97 100644
--- a/manual/contrib.texi
+++ b/manual/contrib.texi
@@ -159,7 +159,7 @@ Ultrix 4 (@code{mips-dec-ultrix4}) and the port to the DEC Alpha
 running OSF/1 (@code{alpha-dec-osf1}).
 
 @item
-Mark Kettenis for implementing the @code{utmpx} interface and an utmp
+Mark Kettenis for implementing the @code{utmpx} interface and a utmp
 daemon, and for a Hesiod NSS module.
 
 @item
@@ -183,7 +183,7 @@ Jeff Law for various fixes.
 
 @item
 Doug Lea for contributing the memory allocation functions
-functions @code{malloc}, @code{realloc} and @code{free} and related
+@code{malloc}, @code{realloc} and @code{free} and related
 code.
 
 @item
@@ -358,7 +358,7 @@ package by Arthur David Olson and his many contributors.
 
 @item
 Some of the support code for Mach is taken from Mach 3.0 by CMU;
-the file if_ppp.h is also copyright by CMU, but under a different license;
+the file @file{if_ppp.h} is also copyright by CMU, but under a different license;
 see the file @file{LICENSES} for the text of the licenses.
 
 @item

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=6d2857d35053fe117a49c73c06d22627b8ca38e3

commit 6d2857d35053fe117a49c73c06d22627b8ca38e3
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:29:11 2016 +0530

    Manual typos: Library Maintenance
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/maint.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 8b91b32..39aa215 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/maint.texi: Fix typos in the manual.
+
 	* manual/install.texi: Fix typos in the manual.
 	* INSTALL: Regenerated.
 
diff --git a/manual/maint.texi b/manual/maint.texi
index 862b49d..473ab16 100644
--- a/manual/maint.texi
+++ b/manual/maint.texi
@@ -152,7 +152,7 @@ functions should be called @file{sys/platform/@var{name}.h}.
 
 @item
 Each header file's name should include the platform name, to avoid
-users thinking there is anything in common between different the
+users thinking there is anything in common between the different
 header files for different platforms.  For example, a
 @file{sys/platform/@var{arch}.h} name such as
 @file{sys/platform/ppc.h} is better than @file{sys/platform.h}.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=b55a155f005366b5a6c886a2e4c57707b341b619

commit b55a155f005366b5a6c886a2e4c57707b341b619
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:28:45 2016 +0530

    Manual typos: Installing
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/install.texi: Fix typos in the manual.
    	* INSTALL: Regenerated.

diff --git a/ChangeLog b/ChangeLog
index 78ee06d..8b91b32 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/install.texi: Fix typos in the manual.
+	* INSTALL: Regenerated.
+
 	* manual/lang.texi: Fix typos in the manual.
 
 	* manual/probes.texi: Fix typos in the manual.
diff --git a/INSTALL b/INSTALL
index ec3445f..51f26bf 100644
--- a/INSTALL
+++ b/INSTALL
@@ -155,8 +155,8 @@ will be used, and CFLAGS sets optimization options for the compiler.
      can configure with '--disable-werror'.
 
 '--disable-mathvec'
-     By default for x86_64, the GNU C Library is built with vector math
-     library.  Use this option to disable vector math library.
+     By default for x86_64, the GNU C Library is built with the vector
+     math library.  Use this option to disable the vector math library.
 
 '--build=BUILD-SYSTEM'
 '--host=HOST-SYSTEM'
@@ -193,8 +193,8 @@ will be used, and CFLAGS sets optimization options for the compiler.
 
    To build the library and related programs, type 'make'.  This will
 produce a lot of output, some of which may look like errors from 'make'
-but isn't.  Look for error messages from 'make' containing '***'.  Those
-indicate that something is seriously wrong.
+but aren't.  Look for error messages from 'make' containing '***'.
+Those indicate that something is seriously wrong.
 
    The compilation process can take a long time, depending on the
 configuration and the speed of your machine.  Some complex modules may
diff --git a/manual/install.texi b/manual/install.texi
index 79ee45f..663f8d5 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -186,8 +186,8 @@ new warnings cause the build with @option{-Werror} to fail), you can
 configure with @option{--disable-werror}.
 
 @item --disable-mathvec
-By default for x86_64, @theglibc{} is built with vector math library.
-Use this option to disable vector math library.
+By default for x86_64, @theglibc{} is built with the vector math library.
+Use this option to disable the vector math library.
 
 @item --build=@var{build-system}
 @itemx --host=@var{host-system}
@@ -225,7 +225,7 @@ information for @theglibc{}.
 
 To build the library and related programs, type @code{make}.  This will
 produce a lot of output, some of which may look like errors from
-@code{make} but isn't.  Look for error messages from @code{make}
+@code{make} but aren't.  Look for error messages from @code{make}
 containing @samp{***}.  Those indicate that something is seriously wrong.
 
 The compilation process can take a long time, depending on the

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=ae996b9f39750ec2ad9808b7a13f09135833cd12

commit ae996b9f39750ec2ad9808b7a13f09135833cd12
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:27:48 2016 +0530

    Manual typos: C Language Facilities in the Library
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/lang.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index ae6d121..78ee06d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/lang.texi: Fix typos in the manual.
+
 	* manual/probes.texi: Fix typos in the manual.
 
 	* manual/threads.texi: Fix typos in the manual.
diff --git a/manual/lang.texi b/manual/lang.texi
index ae7d5be..6281840 100644
--- a/manual/lang.texi
+++ b/manual/lang.texi
@@ -560,7 +560,7 @@ recommend instead adding a prototype for the function you are calling.
 The result of subtracting two pointers in C is always an integer, but the
 precise data type varies from C compiler to C compiler.  Likewise, the
 data type of the result of @code{sizeof} also varies between compilers.
-ISO defines standard aliases for these two types, so you can refer to
+ISO C defines standard aliases for these two types, so you can refer to
 them in a portable fashion.  They are defined in the header file
 @file{stddef.h}.
 @pindex stddef.h
@@ -1143,7 +1143,7 @@ macros are supposed to be at least @code{10}.
 @comment ISO
 @item FLT_MIN_EXP
 This is the smallest possible exponent value for type @code{float}.
-More precisely, is the minimum negative integer such that the value
+More precisely, it is the minimum negative integer such that the value
 @code{FLT_RADIX} raised to this power minus 1 can be represented as a
 normalized floating point number of type @code{float}.
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=8e52276ef42434493936d851c201bc6d01e36c9a

commit 8e52276ef42434493936d851c201bc6d01e36c9a
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:26:35 2016 +0530

    Manual typos: Internal probes
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/probes.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 1212e9d..ae6d121 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/probes.texi: Fix typos in the manual.
+
 	* manual/threads.texi: Fix typos in the manual.
 
 	* manual/debug.texi: Fix typos in the manual.
diff --git a/manual/probes.texi b/manual/probes.texi
index 7dd56d8..237a918 100644
--- a/manual/probes.texi
+++ b/manual/probes.texi
@@ -121,7 +121,7 @@ This occurs within
 point to the same arena.  In this configuration, this will usually only
 occur once per thread.  The exception is when a thread first selected
 the main arena, but a subsequent allocation from it fails: then, and
-only then, may we switch to another arena to retry that allocations, and
+only then, may we switch to another arena to retry that allocation, and
 for further allocations within that thread.
 @end deftp
 
@@ -163,7 +163,7 @@ parameter.
 @end deftp
 
 @deftp Probe memory_mallopt_trim_threshold (int @var{$arg1}, int @var{$arg2}, int @var{$arg3})
-This probe is triggere shortly after the @code{memory_mallopt} probe,
+This probe is triggered shortly after the @code{memory_mallopt} probe,
 when the parameter to be changed is @code{M_TRIM_THRESHOLD}.  Argument
 @var{$arg1} is the requested value, @var{$arg2} is the previous value of
 this @code{malloc} parameter, and @var{$arg3} is nonzero if dynamic

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=a309449484161647ac93278706adb90086e05e30

commit a309449484161647ac93278706adb90086e05e30
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:26:06 2016 +0530

    Manual typos: POSIX Threads
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/threads.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index e057500..1212e9d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/threads.texi: Fix typos in the manual.
+
 	* manual/debug.texi: Fix typos in the manual.
 
 	* manual/crypt.texi: Fix typos in the manual.
diff --git a/manual/threads.texi b/manual/threads.texi
index 00cc725..d7fac82 100644
--- a/manual/threads.texi
+++ b/manual/threads.texi
@@ -4,7 +4,7 @@
 @c %MENU% POSIX Threads
 @cindex pthreads
 
-This chapter describes the @glibcadj{} POSIX Thread implementation.
+This chapter describes the @glibcadj{} POSIX Threads implementation.
 
 @menu
 * Thread-specific Data::          Support for creating and

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=db5e4e881f25e2adff96f070e5c97f1a27e5abe4

commit db5e4e881f25e2adff96f070e5c97f1a27e5abe4
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:25:38 2016 +0530

    Manual typos: Debugging support
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/debug.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 461c5a5..e057500 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/debug.texi: Fix typos in the manual.
+
 	* manual/crypt.texi: Fix typos in the manual.
 
 	* manual/conf.texi: Fix typos in the manual.
diff --git a/manual/debug.texi b/manual/debug.texi
index 25492c3..ac5121b 100644
--- a/manual/debug.texi
+++ b/manual/debug.texi
@@ -90,12 +90,12 @@ contains a printable representation of the corresponding element of
 determined), an offset into the function, and the actual return address
 (in hexadecimal).
 
-Currently, the function name and offset only be obtained on systems that
+Currently, the function name and offset can only be obtained on systems that
 use the ELF binary format for programs and libraries.  On other systems,
 only the hexadecimal return address will be present.  Also, you may need
 to pass additional flags to the linker to make the function names
 available to the program.  (For example, on systems using GNU ld, you
-must pass (@code{-rdynamic}.)
+must pass @code{-rdynamic}.)
 
 The return value of @code{backtrace_symbols} is a pointer obtained via
 the @code{malloc} function, and it is the responsibility of the caller

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=b8867dabdf8193ca49ddc2ee5bb617b0a39e183f

commit b8867dabdf8193ca49ddc2ee5bb617b0a39e183f
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:25:00 2016 +0530

    Manual typos: DES Encryption and Password Handling
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/crypt.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index b5e779a..461c5a5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/crypt.texi: Fix typos in the manual.
+
 	* manual/conf.texi: Fix typos in the manual.
 
 	* manual/sysinfo.texi: Fix typos in the manual.
diff --git a/manual/crypt.texi b/manual/crypt.texi
index 659688b..9f44740 100644
--- a/manual/crypt.texi
+++ b/manual/crypt.texi
@@ -307,7 +307,7 @@ defined in @file{crypt.h}.
 
 @comment rpc/des_crypt.h
 @comment SUNRPC
-@deftypefun int ecb_crypt (char *@var{key}, char *@var{blocks}, unsigned @var{len}, unsigned @var{mode})
+@deftypefun int ecb_crypt (char *@var{key}, char *@var{blocks}, unsigned int @var{len}, unsigned int @var{mode})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 
 The function @code{ecb_crypt} encrypts or decrypts one or more blocks
@@ -320,7 +320,7 @@ least-significant bit of @code{key[7]}.  The @var{key} should have the
 correct parity.
 
 @var{len} is the number of bytes in @var{blocks}.  It should be a
-multiple of 8 (so that there is a whole number of blocks to encrypt).
+multiple of 8 (so that there are a whole number of blocks to encrypt).
 @var{len} is limited to a maximum of @code{DES_MAXDATA} bytes.
 
 The result of the encryption replaces the input in @var{blocks}.
@@ -390,7 +390,7 @@ This macro returns 1 if @var{err} is a `success' result code from
 
 @comment rpc/des_crypt.h
 @comment SUNRPC
-@deftypefun int cbc_crypt (char *@var{key}, char *@var{blocks}, unsigned @var{len}, unsigned @var{mode}, char *@var{ivec})
+@deftypefun int cbc_crypt (char *@var{key}, char *@var{blocks}, unsigned int @var{len}, unsigned int @var{mode}, char *@var{ivec})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 
 The function @code{cbc_crypt} encrypts or decrypts one or more blocks
@@ -409,7 +409,7 @@ Usually, @var{ivec} is set to 8 random bytes before encryption starts.
 Then the 8 random bytes are transmitted along with the encrypted data
 (without themselves being encrypted), and passed back in as @var{ivec}
 for decryption.  Another possibility is to set @var{ivec} to 8 zeroes
-initially, and have the first the block encrypted consist of 8 random
+initially, and have the first block encrypted consist of 8 random
 bytes.
 
 Otherwise, all the parameters are similar to those for @code{ecb_crypt}.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=d80cf4a6be1e913b4c9d1f64772ff2bb4e3391af

commit d80cf4a6be1e913b4c9d1f64772ff2bb4e3391af
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:24:07 2016 +0530

    Manual typos: System Configuration Parameters
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/conf.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 602c1b9..b5e779a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/conf.texi: Fix typos in the manual.
+
 	* manual/sysinfo.texi: Fix typos in the manual.
 
 	* manual/users.texi: Fix typos in the manual.
diff --git a/manual/conf.texi b/manual/conf.texi
index 82a8766..78b7a4d 100644
--- a/manual/conf.texi
+++ b/manual/conf.texi
@@ -148,7 +148,7 @@ should always be defined even if there is no specific imposed limit.
 POSIX defines certain system-specific options that not all POSIX systems
 support.  Since these options are provided in the kernel, not in the
 library, simply using @theglibc{} does not guarantee any of these
-features is supported; it depends on the system you are using.
+features are supported; it depends on the system you are using.
 
 @pindex unistd.h
 You can test for the availability of a given option using the macros in
@@ -466,7 +466,7 @@ Inquire about the parameter corresponding to @code{_POSIX_AIO_MAX}.
 @comment unistd.h
 @comment POSIX.1
 @item _SC_AIO_PRIO_DELTA_MAX
-Inquire the value by which a process can decrease its asynchronous I/O
+Inquire about the value by which a process can decrease its asynchronous I/O
 priority level from its own scheduling priority.  This corresponds to the
 run-time invariant value @code{AIO_PRIO_DELTA_MAX}.
 
@@ -573,7 +573,7 @@ Inquire about the parameter corresponding to @code{_POSIX_PII_OSI_M}.
 @comment unistd.h
 @comment POSIX.1g
 @item _SC_T_IOV_MAX
-Inquire the value of the value associated with the @code{T_IOV_MAX}
+Inquire about the value associated with the @code{T_IOV_MAX}
 variable.
 
 @comment unistd.h
@@ -888,7 +888,7 @@ Inquire about the number of bits in a variable of a register word.
 @comment unistd.h
 @comment X/Open
 @item _SC_MB_LEN_MAX
-Inquire the maximum length of a multi-byte representation of a wide
+Inquire about the maximum length of a multi-byte representation of a wide
 character value.
 
 @comment unistd.h
@@ -1553,7 +1553,7 @@ the collating sequence for a locale.
 @comment limits.h
 @comment POSIX.2
 @deftypevr Macro int EXPR_NEST_MAX
-The maximum number of expressions that can be nested within parenthesis
+The maximum number of expressions that can be nested within parentheses
 by the @code{expr} utility.
 @end deftypevr
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=61547c480f25f224fb6847d52b6d3555b9906f98

commit 61547c480f25f224fb6847d52b6d3555b9906f98
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:23:27 2016 +0530

    Manual typos: System Management
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/sysinfo.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 826c1cd..602c1b9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/sysinfo.texi: Fix typos in the manual.
+
 	* manual/users.texi: Fix typos in the manual.
 
 	* manual/job.texi: Fix typos in the manual.
diff --git a/manual/sysinfo.texi b/manual/sysinfo.texi
index 1fbfb95..65ee7cf 100644
--- a/manual/sysinfo.texi
+++ b/manual/sysinfo.texi
@@ -36,7 +36,7 @@ computer networks were an issue, it's just a word like @samp{chicken}.
 
 But any system attached to the Internet or any network like it conforms
 to a more rigorous naming convention as part of the Domain Name System
-(DNS).  In DNS, every host name is composed of two parts:
+(DNS).  In the DNS, every host name is composed of two parts:
 @cindex DNS
 @cindex Domain Name System
 
@@ -53,7 +53,7 @@ You will note that ``hostname'' looks a lot like ``host name'', but is
 not the same thing, and that people often incorrectly refer to entire
 host names as ``domain names.''
 
-In DNS, the full host name is properly called the FQDN (Fully Qualified
+In the DNS, the full host name is properly called the FQDN (Fully Qualified
 Domain Name) and consists of the hostname, then a period, then the
 domain name.  The domain name itself usually has multiple components
 separated by periods.  So for example, a system's hostname may be
@@ -61,7 +61,7 @@ separated by periods.  So for example, a system's hostname may be
 its FQDN (which is its host name) is @samp{chicken.ai.mit.edu}.
 @cindex FQDN
 
-Adding to the confusion, though, is that DNS is not the only name space
+Adding to the confusion, though, is that the DNS is not the only name space
 in which a computer needs to be known.  Another name space is the
 NIS (aka YP) name space.  For NIS purposes, there is another domain
 name, which is called the NIS domain name or the YP domain name.  It
@@ -71,7 +71,7 @@ need not have anything to do with the DNS domain name.
 @cindex NIS domain name
 @cindex YP domain name
 
-Confusing things even more is the fact that in DNS, it is possible for
+Confusing things even more is the fact that in the DNS, it is possible for
 multiple FQDNs to refer to the same system.  However, there is always
 exactly one of them that is the true host name, and it is called the
 canonical FQDN.
@@ -97,7 +97,7 @@ by calling these functions.
 This function returns the host name of the system on which it is called,
 in the array @var{name}.  The @var{size} argument specifies the size of
 this array, in bytes.  Note that this is @emph{not} the DNS hostname.
-If the system participates in DNS, this is the FQDN (see above).
+If the system participates in the DNS, this is the FQDN (see above).
 
 The return value is @code{0} on success and @code{-1} on failure.  In
 @theglibc{}, @code{gethostname} fails if @var{size} is not large
@@ -172,7 +172,7 @@ The specifics of this function are analogous to @code{gethostname}, above.
 @cindex NIS domain name
 @cindex YP domain name
 
-@code{getdomainname} sets the NIS (aka YP) domain name of the system
+@code{setdomainname} sets the NIS (aka YP) domain name of the system
 on which it is called.  Note that this is not the more popular DNS
 domain name.  Set that with @code{sethostname}.
 
@@ -295,7 +295,7 @@ This is the host name of this particular computer.  In @theglibc{},
 the value is the same as that returned by @code{gethostname};
 see @ref{Host Identification}.
 
-@ gethostname() is implemented with a call to uname().
+@code{gethostname} is implemented with a call to @code{uname}.
 
 @item char domainname[]
 This is the NIS or YP domain name.  It is the same value returned by
@@ -317,9 +317,9 @@ use of the rest of the structure.
 @c proc_uname and then gethostname.
 The @code{uname} function fills in the structure pointed to by
 @var{info} with information about the operating system and host machine.
-A non-negative value indicates that the data was successfully stored.
+A non-negative return value indicates that the data was successfully stored.
 
-@code{-1} as the value indicates an error.  The only error possible is
+@code{-1} as the return value indicates an error.  The only error possible is
 @code{EFAULT}, which we normally don't mention as it is always a
 possibility.
 @end deftypefun
@@ -373,7 +373,7 @@ necessary filesystems.  The information about all the filesystems
 actually mounted is normally kept in a file named either
 @file{/var/run/mtab} or @file{/etc/mtab}.  Both files share the same
 syntax and it is crucial that this syntax is followed all the time.
-Therefore it is best to never directly write the files.  The functions
+Therefore it is best to never directly write to the files.  The functions
 described in this section can do this and they also provide the
 functionality to convert the external textual representation to the
 internal representation.
@@ -392,7 +392,7 @@ files as described herein.
 @vindex MNTTAB
 @vindex MOUNTED
 The filenames given above should never be used directly.  The portable
-way to handle these file is to use the macro @code{_PATH_FSTAB},
+way to handle these files is to use the macros @code{_PATH_FSTAB},
 defined in @file{fstab.h}, or @code{_PATH_MNTTAB}, defined in
 @file{mntent.h} and @file{paths.h}, for @file{fstab}; and the macro
 @code{_PATH_MOUNTED}, also defined in @file{mntent.h} and
@@ -458,9 +458,9 @@ possible values:
 
 @vtable @code
 @item FSTAB_RW
-The filesystems gets mounted with read and write enabled.
+The filesystem gets mounted with read and write enabled.
 @item FSTAB_RQ
-The filesystems gets mounted with read and write enabled.  Write access
+The filesystem gets mounted with read and write enabled.  Write access
 is restricted by quotas.
 @item FSTAB_RO
 The filesystem gets mounted read-only.
@@ -470,7 +470,7 @@ This is not a real filesystem, it is a swap device.
 This entry from the @file{fstab} file is totally ignored.
 @end vtable
 
-Testing for equality with these value must happen using @code{strcmp}
+Testing for equality with these values must happen using @code{strcmp}
 since these are all strings.  Comparing the pointer will probably always
 fail.
 
@@ -594,7 +594,7 @@ The following functions and data structure access the @file{mtab} file.
 @comment mntent.h
 @comment BSD
 @deftp {Data Type} {struct mntent}
-This structure is used with the @code{getmntent}, @code{getmntent_t},
+This structure is used with the @code{getmntent}, @code{getmntent_r},
 @code{addmntent}, and @code{hasmntopt} functions.
 
 @table @code
@@ -619,7 +619,7 @@ list of the symbols provided in @file{mntent.h}.
 
 @vtable @code
 @item MNTTYPE_IGNORE
-This symbol expands to @code{"ignore"}.  The value is sometime used in
+This symbol expands to @code{"ignore"}.  The value is sometimes used in
 @file{fstab} files to make sure entries are not used without removing them.
 @item MNTTYPE_NFS
 Expands to @code{"nfs"}.  Using this macro sometimes could make sense
@@ -650,7 +650,7 @@ default.
 Expands to @code{"ro"}.  See the @code{FSTAB_RO} value, it means the
 filesystem is mounted read-only.
 @item MNTOPT_RW
-Expand to @code{"rw"}.  See the @code{FSTAB_RW} value, it means the
+Expands to @code{"rw"}.  See the @code{FSTAB_RW} value, it means the
 filesystem is mounted with read and write permissions.
 @item MNTOPT_SUID
 Expands to @code{"suid"}.  This means that the SUID bit (@pxref{How
@@ -681,7 +681,7 @@ which is uninteresting for all programs beside @code{dump}.
 For accessing the @file{mtab} file there is again a set of three
 functions to access all entries in a row.  Unlike the functions to
 handle @file{fstab} these functions do not access a fixed file and there
-is even a thread safe variant of the get function.  Beside this @theglibc
+is even a thread safe variant of the get function.  Besides this @theglibc{}
 contains functions to alter the file and test for specific options.
 
 @comment mntent.h
@@ -702,7 +702,7 @@ parameter for @code{fopen} (@pxref{Opening Streams}) can be chosen.  If
 the file is opened for writing the file is also allowed to be empty.
 
 If the file was successfully opened @code{setmntent} returns a file
-descriptor for future use.  Otherwise the return value is @code{NULL}
+handle for future use.  Otherwise the return value is @code{NULL}
 and @code{errno} is set accordingly.
 @end deftypefun
 
@@ -730,13 +730,13 @@ is @math{0}.
 @c    malloc dup @ascuheap @acsmem
 @c  getmntent_r dup @mtslocale @asucorrupt @ascuheap @acucorrupt @aculock @acsmem
 The @code{getmntent} function takes as the parameter a file handle
-previously returned by successful call to @code{setmntent}.  It returns
+previously returned by a successful call to @code{setmntent}.  It returns
 a pointer to a static variable of type @code{struct mntent} which is
 filled with the information from the next entry from the file currently
 read.
 
 The file format used prescribes the use of spaces or tab characters to
-separate the fields.  This makes it harder to use name containing one
+separate the fields.  This makes it harder to use names containing one
 of these characters (e.g., mount points using spaces).  Therefore
 these characters are encoded in the files and the @code{getmntent}
 function takes care of the decoding while reading the entries back in.
@@ -809,7 +809,7 @@ chosen name.
 
 This function takes care of spaces and tab characters in the names to be
 written to the file.  It converts them and the backslash character into
-the format describe in the @code{getmntent} description above.
+the format described in the @code{getmntent} description above.
 
 This function returns @math{0} in case the operation was successful.
 Otherwise the return value is @math{1} and @code{errno} is set
@@ -886,7 +886,7 @@ ignored.  Remounting a filesystem means changing the options that control
 operations on the filesystem while it is mounted.  It does not mean
 unmounting and mounting again.
 
-For a mount, you must identify the type of the filesystem as
+For a mount, you must identify the type of the filesystem with
 @var{fstype}.  This type tells the kernel how to access the filesystem
 and can be thought of as the name of a filesystem driver.  The
 acceptable values are system dependent.  On a system with a Linux kernel
@@ -1023,7 +1023,7 @@ The mount point is busy.  (E.g. it is some process' working directory or
 has a filesystem mounted on it already).
 
 @item
-The request is to remount read-only, but there are files open for write.
+The request is to remount read-only, but there are files open for writing.
 @end itemize
 
 @item EINVAL
@@ -1177,7 +1177,7 @@ The set of available parameters depends on the kernel configuration and
 can change while the system is running, particularly when you load and
 unload loadable kernel modules.
 
-The system parameters with which @code{syslog} is concerned are arranged
+The system parameters with which @code{sysctl} is concerned are arranged
 in a hierarchical structure like a hierarchical filesystem.  To identify
 a particular parameter, you specify a path through the structure in a
 way analogous to specifying the pathname of a file.  Each component of

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=9e302f97d4e4f61935e9d4e7d3175bf70578274c

commit 9e302f97d4e4f61935e9d4e7d3175bf70578274c
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:21:46 2016 +0530

    Manual typos: Users and Groups
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/users.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 06cab50..826c1cd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/users.texi: Fix typos in the manual.
+
 	* manual/job.texi: Fix typos in the manual.
 
 	* manual/process.texi: Fix typos in the manual.
diff --git a/manual/users.texi b/manual/users.texi
index e8f0f3b..0d94db1 100644
--- a/manual/users.texi
+++ b/manual/users.texi
@@ -152,7 +152,7 @@ by creating a new user ID and login name (say, @code{games}) to own the
 scores file, and make the file writable only by this user.  Then, when
 the game program wants to update this file, it can change its effective
 user ID to be that for @code{games}.  In effect, the program must
-adopt the persona of @code{games} so it can write the scores file.
+adopt the persona of @code{games} so it can write to the scores file.
 
 @node How Change Persona
 @section How an Application Can Change Persona
@@ -357,7 +357,7 @@ have this function.
 @c setuid @asulock @aculock
 @c  INLINE_SETXID_SYSCALL dup @asulock @aculock
 If the calling process is privileged, this function sets both the real
-and effective user ID of the process to @var{newuid}.  It also deletes
+and effective user IDs of the process to @var{newuid}.  It also deletes
 the file user ID of the process, if any.  @var{newuid} may be any
 legal value.  (Once this has been done, there is no way to recover the
 old effective user ID.)
@@ -1059,7 +1059,7 @@ The Internet address of a remote host.
 The @code{ut_type}, @code{ut_pid}, @code{ut_id}, @code{ut_tv}, and
 @code{ut_host} fields are not available on all systems.  Portable
 applications therefore should be prepared for these situations.  To help
-doing this the @file{utmp.h} header provides macros
+do this the @file{utmp.h} header provides macros
 @code{_HAVE_UT_TYPE}, @code{_HAVE_UT_PID}, @code{_HAVE_UT_ID},
 @code{_HAVE_UT_TV}, and @code{_HAVE_UT_HOST} if the respective field is
 available.  The programmer can handle the situations by using
@@ -1081,7 +1081,7 @@ accounting information.
 @comment SVID
 @vindex RUN_LVL
 @item RUN_LVL
-This macro is used to identify the systems runlevel.
+This macro is used to identify the system's runlevel.
 
 @comment utmp.h
 @comment SVID
@@ -1099,7 +1099,7 @@ This macro is used to identify the time when the system clock changed.
 @comment SVID
 @vindex NEW_TIME
 @item NEW_TIME
-This macro is used to identify the time after the system changed.
+This macro is used to identify the time after the system clock changed.
 
 @comment utmp.h
 @comment SVID
@@ -1559,7 +1559,7 @@ accounting information.
 @comment XPG4.2
 @vindex RUN_LVL
 @item RUN_LVL
-This macro is used to identify the systems runlevel.
+This macro is used to identify the system's runlevel.
 
 @comment utmpx.h
 @comment XPG4.2
@@ -1577,7 +1577,7 @@ This macro is used to identify the time when the system clock changed.
 @comment XPG4.2
 @vindex NEW_TIME
 @item NEW_TIME
-This macro is used to identify the time after the system changed.
+This macro is used to identify the time after the system clock changed.
 
 @comment utmpx.h
 @comment XPG4.2
@@ -2153,7 +2153,7 @@ A null pointer return indicates there is no user named @var{name}.
 @c
 @c _nss_*_getpwnam_r (assumed) @asuinit @asulock @acucorrupt @aculock
 
-This function is similar to @code{getpwnam} in that is returns
+This function is similar to @code{getpwnam} in that it returns
 information about the user whose user name is @var{name}.  However, like
 @code{getpwuid_r}, it fills the user supplied buffers in
 @var{result_buf} and @var{buffer} with the information instead of using
@@ -2466,13 +2466,12 @@ A null pointer indicates there is no group named @var{name}.
 @c  nss_group_lookup2 dup @mtslocale @ascudlopen @ascuplugin @ascuheap @asulock @acucorrupt @aculock @acsfd @acsmem
 @c  *fct.l @ascuplugin
 @c  nss_next2 dup @ascudlopen @ascuplugin @ascuheap @asulock @acucorrupt @aculock @acsfd @acsmem
-This function is similar to @code{getgrnam} in that is returns
+This function is similar to @code{getgrnam} in that it returns
 information about the group whose group name is @var{name}.  Like
 @code{getgrgid_r}, it uses the user supplied buffers in
 @var{result_buf} and @var{buffer}, not a static buffer.
 
-The return values are the same as for @code{getgrgid_r}
-@code{ERANGE}.
+The return values are the same as for @code{getgrgid_r}.
 @end deftypefun
 
 @node Scanning All Groups
@@ -2570,7 +2569,7 @@ wish to save the information.
 This function is similar to @code{getgrent} in that it returns the next
 entry from the stream initialized by @code{setgrent}.  Like
 @code{fgetgrent_r}, it places the result in user-supplied buffers
-pointed to @var{result_buf} and @var{buffer}.
+pointed to by @var{result_buf} and @var{buffer}.
 
 If the function returns zero @var{result} contains a pointer to the data
 (normally equal to @var{result_buf}).  If errors occurred the return
@@ -2630,7 +2629,7 @@ Sometimes it is useful to group users according to other criteria
 group of users with a certain machine.  On the other hand grouping of
 host names is not supported so far.
 
-In Sun Microsystems SunOS appeared a new kind of database, the netgroup
+In Sun Microsystems' SunOS appeared a new kind of database, the netgroup
 database.  It allows grouping hosts, users, and domains freely, giving
 them individual names.  To be more concrete, a netgroup is a list of triples
 consisting of a host name, a user name, and a domain name where any of
@@ -2657,7 +2656,7 @@ character @code{-} shall be used.
 @node Lookup Netgroup
 @subsection Looking up one Netgroup
 
-The lookup functions for netgroups are a bit different to all other
+The lookup functions for netgroups are a bit different than all other
 system database handling functions.  Since a single netgroup can contain
 many entries a two-step process is needed.  First a single netgroup is
 selected and then one can iterate over all entries in this netgroup.
@@ -2701,7 +2700,7 @@ These functions are declared in @file{netdb.h}.
 @c    memcpy dup ok
 @c  libc_lock_unlock dup @aculock
 A call to this function initializes the internal state of the library to
-allow following calls of the @code{getnetgrent} to iterate over all entries
+allow following calls of @code{getnetgrent} to iterate over all entries
 in the netgroup with name @var{netgroup}.
 
 When the call is successful (i.e., when a netgroup with this name exists)
@@ -2831,7 +2830,7 @@ selected netgroup.
 @c  nss_next2 dup @ascudlopen @ascuplugin @ascuheap @asulock @acucorrupt @aculock @acsfd @acsmem
 @c  free_memory dup @ascuheap @acsmem
 This function tests whether the triple specified by the parameters
-@var{hostp}, @var{userp}, and @var{domainp} is part of the netgroup
+@var{host}, @var{user}, and @var{domain} is part of the netgroup
 @var{netgroup}.  Using this function has the advantage that
 
 @enumerate
@@ -2843,7 +2842,7 @@ the function is implemented more efficiently than successive calls
 to the other @code{set}/@code{get}/@code{endnetgrent} functions.
 @end enumerate
 
-Any of the pointers @var{hostp}, @var{userp}, and @var{domainp} can be
+Any of the pointers @var{host}, @var{user}, or @var{domain} can be
 @code{NULL} which means any value is accepted in this position.  This is
 also true for the name @code{-} which should not match any other string
 otherwise.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=d72457974ddff7a4f73969246b87fe184840d40e

commit d72457974ddff7a4f73969246b87fe184840d40e
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:20:28 2016 +0530

    Manual typos: Job Control
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/job.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 72c645f..06cab50 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/job.texi: Fix typos in the manual.
+
 	* manual/process.texi: Fix typos in the manual.
 
 	* manual/argp.texi: Fix typos in the manual.
diff --git a/manual/job.texi b/manual/job.texi
index 095c26d..72b5599 100644
--- a/manual/job.texi
+++ b/manual/job.texi
@@ -100,7 +100,7 @@ for allowing the user to interactively continue stopped jobs and switch
 jobs between foreground and background.
 
 @xref{Access to the Terminal}, for more information about I/O to the
-controlling terminal,
+controlling terminal.
 
 @node Job Control is Optional, Controlling Terminal, Concepts of Job Control , Job Control
 @section Job Control is Optional

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=9cbcfebd024344e9be096869f08ee5474b881cbb

commit 9cbcfebd024344e9be096869f08ee5474b881cbb
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:19:59 2016 +0530

    Manual typos: Processes
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/process.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 5e9d168..72c645f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/process.texi: Fix typos in the manual.
+
 	* manual/argp.texi: Fix typos in the manual.
 	* manual/getopt.texi: Likewise.
 	* manual/startup.texi: Likewise.
diff --git a/manual/process.texi b/manual/process.texi
index 25bdb8e..67b3237 100644
--- a/manual/process.texi
+++ b/manual/process.texi
@@ -497,7 +497,7 @@ information about signals, see @ref{Signal Handling}.
 File descriptors open in the existing process image remain open in the
 new process image, unless they have the @code{FD_CLOEXEC}
 (close-on-exec) flag set.  The files that remain open inherit all
-attributes of the open file description from the existing process image,
+attributes of the open file descriptors from the existing process image,
 including file locks.  File descriptors are discussed in @ref{Low-Level I/O}.
 
 Streams, by contrast, cannot survive through @code{exec} functions,

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=954cbda0faae0f8e5d47b3a536ef37d8fb2c2626

commit 954cbda0faae0f8e5d47b3a536ef37d8fb2c2626
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:19:25 2016 +0530

    Manual typos: The Basic Program/System Interface
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/argp.texi: Fix typos in the manual.
    	* manual/getopt.texi: Likewise.
    	* manual/startup.texi: Likewise.

diff --git a/ChangeLog b/ChangeLog
index d155ba2..5e9d168 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/argp.texi: Fix typos in the manual.
+	* manual/getopt.texi: Likewise.
+	* manual/startup.texi: Likewise.
+
 	* manual/signal.texi: Fix typos in the manual.
 
 	* manual/setjmp.texi: Fix typos in the manual.
diff --git a/manual/argp.texi b/manual/argp.texi
index dae6809..bca3ca5 100644
--- a/manual/argp.texi
+++ b/manual/argp.texi
@@ -347,7 +347,7 @@ be displayed in much the same manner as the options.  This is known as a
 If this flag is set, then the option @code{name} field is displayed
 unmodified (e.g., no @samp{--} prefix is added) at the left-margin where
 a @emph{short} option would normally be displayed, and this
-documentation string is left in it's usual place.  For purposes of
+documentation string is left in its usual place.  For purposes of
 sorting, any leading whitespace and punctuation is ignored, unless the
 first non-whitespace character is @samp{-}.  This entry is displayed
 after all options, after @code{OPTION_DOC} entries with a leading
@@ -692,7 +692,7 @@ parser function.  @xref{Argp Parsing State}.
 @safety{@prelim{}@mtunsafe{@mtasurace{:argpbuf} @mtsenv{} @mtslocale{}}@asunsafe{@ascuheap{} @ascuintl{} @asucorrupt{}}@acunsafe{@acsmem{} @acucorrupt{} @aculock{}}}
 @c Just calls argp_state_help with stderr and ARGP_HELP_STD_USAGE.
 Outputs the standard usage message for the argp parser referred to by
-@var{state} to @code{@var{state}->err_stream} and terminate the program
+@var{state} to @code{@var{state}->err_stream} and terminates the program
 with @code{exit (argp_err_exit_status)}.  @xref{Argp Global Variables}.
 @end deftypefun
 
@@ -723,7 +723,7 @@ by the program name and @samp{:}, and followed by a @w{@samp{Try @dots{}
 @c blank, release the buffer, call strerror_r with an automatic buffer,
 @c print it out after colon and blank, put[w]c a line break, unlock the
 @c stream, then exit unless ARGP_NO_EXIT.
-Similar to the standard gnu error-reporting function @code{error}, this
+Similar to the standard GNU error-reporting function @code{error}, this
 prints the program name and @samp{:}, the printf format string
 @var{fmt}, and the appropriate following args.  If it is non-zero, the
 standard unix error text for @var{errnum} is printed.  If @var{status} is
@@ -1010,7 +1010,7 @@ Don't exit on errors, although they may still result in error messages.
 @comment argp.h
 @comment GNU
 @item ARGP_LONG_ONLY
-Use the gnu getopt `long-only' rules for parsing arguments.  This allows
+Use the GNU getopt `long-only' rules for parsing arguments.  This allows
 long-options to be recognized with only a single @samp{-}
 (i.e., @samp{-help}).  This results in a less useful interface, and its
 use is discouraged as it conflicts with the way most GNU programs work
@@ -1213,7 +1213,7 @@ These example programs demonstrate the basic usage of argp.
 @subsubsection A Minimal Program Using Argp
 
 This is perhaps the smallest program possible that uses argp.  It won't
-do much except give an error messages and exit when there are any
+do much except give an error message and exit when there are any
 arguments, and prints a rather pointless message for @samp{--help}.
 
 @smallexample
diff --git a/manual/getopt.texi b/manual/getopt.texi
index aa4134b..20e11ef 100644
--- a/manual/getopt.texi
+++ b/manual/getopt.texi
@@ -110,7 +110,7 @@ is treated specially.  It permits arguments that are not options to be
 returned as if they were associated with option character @samp{\1}.
 
 @item
-POSIX demands the following behavior: The first non-option stops option
+POSIX demands the following behavior: the first non-option stops option
 processing.  This mode is selected by either setting the environment
 variable @code{POSIXLY_CORRECT} or beginning the @var{options} argument
 string with a plus sign (@samp{+}).
@@ -256,7 +256,7 @@ options to accept (see above).
 
 When @code{getopt_long} encounters a short option, it does the same
 thing that @code{getopt} would do: it returns the character code for the
-option, and stores the options argument (if it has one) in @code{optarg}.
+option, and stores the option's argument (if it has one) in @code{optarg}.
 
 When @code{getopt_long} encounters a long option, it takes actions based
 on the @code{flag} and @code{val} fields of the definition of that
@@ -293,8 +293,8 @@ When @code{getopt_long} has no more options to handle, it returns
 @var{argv} of the next remaining argument.
 @end deftypefun
 
-Since long option names were used before the @code{getopt_long}
-options was invented there are program interfaces which require programs
+Since long option names were used before @code{getopt_long}
+was invented there are program interfaces which require programs
 to recognize options like @w{@samp{-option value}} instead of
 @w{@samp{--option value}}.  To enable these programs to use the GNU
 getopt functionality there is one more function available.
@@ -306,7 +306,7 @@ getopt functionality there is one more function available.
 @c Same issues as getopt.
 
 The @code{getopt_long_only} function is equivalent to the
-@code{getopt_long} function but it allows to specify the user of the
+@code{getopt_long} function but it allows the user of the
 application to pass long options with only @samp{-} instead of
 @samp{--}.  The @samp{--} prefix is still recognized but instead of
 looking through the short options if a @samp{-} is seen it is first
diff --git a/manual/startup.texi b/manual/startup.texi
index 9a091a5..e4c983a 100644
--- a/manual/startup.texi
+++ b/manual/startup.texi
@@ -18,7 +18,7 @@ one program.
 
 Note that we are using a specific definition of ``program'' for the
 purposes of this manual, which corresponds to a common definition in the
-context of Unix system.  In popular usage, ``program'' enjoys a much
+context of Unix systems.  In popular usage, ``program'' enjoys a much
 broader definition; it can refer for example to a system's kernel, an
 editor macro, a complex package of software, or a discrete section of
 code executing within a process.
@@ -228,9 +228,9 @@ available.
 @c  strncmp dup ok
 
 The @var{optionp} parameter must be a pointer to a variable containing
-the address of the string to process.  When the function returns the
+the address of the string to process.  When the function returns, the
 reference is updated to point to the next suboption or to the
-terminating @samp{\0} character if there is no more suboption available.
+terminating @samp{\0} character if there are no more suboptions available.
 
 The @var{tokens} parameter references an array of strings containing the
 known suboptions.  All strings must be @samp{\0} terminated and to mark
@@ -441,7 +441,7 @@ environment.  If the environment contains an entry with the key
 equivalent to a call to @code{putenv} when the @var{value} part of the
 string is empty.
 
-The function return @code{-1} if @var{name} is a null pointer, points to
+The function returns @code{-1} if @var{name} is a null pointer, points to
 an empty string, or points to a string containing a @code{=} character.
 It returns @code{0} if the call succeeded.
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=16c7d1ec26ecf4cbd3a128a23cf2a8ab495a89b8

commit 16c7d1ec26ecf4cbd3a128a23cf2a8ab495a89b8
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:18:05 2016 +0530

    Manual typos: Signal Handling
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/signal.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index a79d684..d155ba2 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/signal.texi: Fix typos in the manual.
+
 	* manual/setjmp.texi: Fix typos in the manual.
 
 	* manual/resource.texi: Fix typos in the manual.
diff --git a/manual/signal.texi b/manual/signal.texi
index 77f3d7c..79e190d 100644
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -1207,7 +1207,7 @@ the signal.  These are described in more detail in @ref{Flags for Sigaction}.
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 The @var{action} argument is used to set up a new action for the signal
 @var{signum}, while the @var{old-action} argument is used to return
-information about the action previously associated with this symbol.
+information about the action previously associated with this signal.
 (In other words, @var{old-action} has the same purpose as the
 @code{signal} function's return value---you can check to see what the
 old action in effect for the signal was, and restore it later if you
@@ -2092,7 +2092,7 @@ it can also handle a signal in the middle of clearing the flag.  (This
 is an example of the sort of reasoning you need to do to figure out
 whether non-atomic usage is safe.)
 
-Sometimes you can insure uninterrupted access to one object by
+Sometimes you can ensure uninterrupted access to one object by
 protecting its use with another object, perhaps one whose type
 guarantees atomicity.  @xref{Merged Signals}, for an example.
 
@@ -3371,7 +3371,7 @@ signals.  The return value is the previous set of blocked signals.
 @c The exception are BSD systems other than 4.4, where it is a syscall.
 @c sigsetmask @asulock/hurd @aculock/hurd
 @c  sigprocmask(SIG_SETMASK) dup @asulock/hurd @aculock/hurd [no @mtasurace:sigprocmask/bsd(SIG_UNBLOCK)]
-This function equivalent to @code{sigprocmask} (@pxref{Process
+This function is equivalent to @code{sigprocmask} (@pxref{Process
 Signal Mask}) with a @var{how} argument of @code{SIG_SETMASK}: it sets
 the calling process's signal mask to @var{mask}.  The return value is
 the previous set of blocked signals.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=a96ce75c8ed589573e4fa1295c16c61f06bac336

commit a96ce75c8ed589573e4fa1295c16c61f06bac336
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:17:29 2016 +0530

    Manual typos: Non-Local Exits
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/setjmp.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 043b151..a79d684 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/setjmp.texi: Fix typos in the manual.
+
 	* manual/resource.texi: Fix typos in the manual.
 
 	* manual/time.texi: Fix typos in the manual.
diff --git a/manual/setjmp.texi b/manual/setjmp.texi
index ec79c26..94d16be 100644
--- a/manual/setjmp.texi
+++ b/manual/setjmp.texi
@@ -243,9 +243,9 @@ blocked signals.
 
 The Unix standard provides one more set of functions to control the
 execution path and these functions are more powerful than those
-discussed in this chapter so far.  These function were part of the
+discussed in this chapter so far.  These functions were part of the
 original @w{System V} API and by this route were added to the Unix
-API.  Beside on branded Unix implementations these interfaces are not
+API.  Besides on branded Unix implementations these interfaces are not
 widely available.  Not all platforms and/or architectures @theglibc{}
 is available on provide this interface.  Use @file{configure} to
 detect the availability.
@@ -350,7 +350,7 @@ heap memory are normally not tagged to allow this.  The result is that
 programs would fail.  Examples for such code include the calling
 sequences the GNU C compiler generates for calls to nested functions.
 Safe ways to allocate stacks correctly include using memory on the
-original threads stack or explicitly allocate memory tagged for
+original thread's stack or explicitly allocating memory tagged for
 execution using (@pxref{Memory-mapped I/O}).
 
 @strong{Compatibility note}: The current Unix standard is very imprecise
@@ -360,7 +360,7 @@ the elements of the @code{stack_t} value are unclear.  @Theglibc{}
 and most other Unix implementations require the @code{ss_sp} value of
 the @code{uc_stack} element to point to the base of the memory region
 allocated for the stack and the size of the memory region is stored in
-@code{ss_size}.  There are implements out there which require
+@code{ss_size}.  There are implementations out there which require
 @code{ss_sp} to be set to the value the stack pointer will have (which
 can, depending on the direction the stack grows, be different).  This
 difference makes the @code{makecontext} function hard to use and it

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=d3e22d596db768cfa0282176467fcf1c2e286560

commit d3e22d596db768cfa0282176467fcf1c2e286560
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:16:53 2016 +0530

    Manual typos: Resource Usage and Limitation
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/resource.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 596ae14..043b151 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/resource.texi: Fix typos in the manual.
+
 	* manual/time.texi: Fix typos in the manual.
 
 	* manual/arith.texi: Fix typos in the manual.
diff --git a/manual/resource.texi b/manual/resource.texi
index e68458b..75e3a1b 100644
--- a/manual/resource.texi
+++ b/manual/resource.texi
@@ -452,7 +452,7 @@ above do.  The functions above are better choices.
 
 @code{ulimit} gets the current limit or sets the current and maximum
 limit for a particular resource for the calling process according to the
-command @var{cmd}.a
+command @var{cmd}.
 
 If you are getting a limit, the command argument is the only argument.
 If you are setting a limit, there is a second argument:
@@ -652,7 +652,7 @@ instructions for your process.
 Similarly, a page fault causes what looks like a straightforward
 sequence of instructions to take a long time.  The fact that other
 processes get to run while the page faults in is of no consequence,
-because as soon as the I/O is complete, the high priority process will
+because as soon as the I/O is complete, the higher priority process will
 kick them out and run again, but the wait for the I/O itself could be a
 problem.  To neutralize this threat, use @code{mlock} or
 @code{mlockall}.
@@ -668,7 +668,7 @@ order to run.  The errant program is in complete control.  It controls
 the vertical, it controls the horizontal.
 
 There are two ways to avoid this: 1) keep a shell running somewhere with
-a higher absolute priority.  2) keep a controlling terminal attached to
+a higher absolute priority or 2) keep a controlling terminal attached to
 the high priority process group.  All the priority in the world won't
 stop an interrupt handler from running and delivering a signal to the
 process if you hit Control-C.
@@ -733,7 +733,7 @@ between Round Robin and First Come First Served.
 
 To understand how scheduling works when processes of different scheduling
 policies occupy the same absolute priority, you have to know the nitty
-gritty details of how processes enter and exit the ready to run list:
+gritty details of how processes enter and exit the ready to run list.
 
 In both cases, the ready to run list is organized as a true queue, where
 a process gets pushed onto the tail when it becomes ready to run and is
@@ -931,7 +931,7 @@ you want to know.
 absolute priority of the process.
 
 On success, the return value is @code{0}.  Otherwise, it is @code{-1}
-and @code{ERRNO} is set accordingly.  The @code{errno} values specific
+and @code{errno} is set accordingly.  The @code{errno} values specific
 to this function are:
 
 @table @code
@@ -1067,7 +1067,7 @@ among the great unwashed processes gets them.
 @subsubsection Introduction To Traditional Scheduling
 
 Long before there was absolute priority (See @ref{Absolute Priority}),
-Unix systems were scheduling the CPU using this system.  When Posix came
+Unix systems were scheduling the CPU using this system.  When POSIX came
 in like the Romans and imposed absolute priorities to accommodate the
 needs of realtime processing, it left the indigenous Absolute Priority
 Zero processes to govern themselves by their own familiar scheduling
@@ -1095,7 +1095,7 @@ The dynamic priority sometimes determines who gets the next turn on the
 CPU.  Sometimes it determines how long turns last.  Sometimes it
 determines whether a process can kick another off the CPU.
 
-In Linux, the value is a combination of these things, but mostly it is
+In Linux, the value is a combination of these things, but mostly it
 just determines the length of the time slice.  The higher a process'
 dynamic priority, the longer a shot it gets on the CPU when it gets one.
 If it doesn't use up its time slice before giving up the CPU to do
@@ -1124,7 +1124,7 @@ ability to refuse its equal share of CPU time that others might prosper.
 Hence, the higher a process' nice value, the nicer the process is.
 (Then a snake came along and offered some process a negative nice value
 and the system became the crass resource allocation system we know
-today).
+today.)
 
 Dynamic priorities tend upward and downward with an objective of
 smoothing out allocation of CPU time and giving quick response time to
@@ -1181,7 +1181,7 @@ have the same nice value, this returns the lowest value that any of them
 has.
 
 On success, the return value is @code{0}.  Otherwise, it is @code{-1}
-and @code{ERRNO} is set accordingly.  The @code{errno} values specific
+and @code{errno} is set accordingly.  The @code{errno} values specific
 to this function are:
 
 @table @code
@@ -1306,7 +1306,7 @@ over this aspect of the system as well:
 @item
 One thread or process is responsible for absolutely critical work
 which under no circumstances must be interrupted or hindered from
-making process by other process or threads using CPU resources.  In
+making progress by other processes or threads using CPU resources.  In
 this case the special process would be confined to a CPU which no
 other process or thread is allowed to use.
 
@@ -1316,7 +1316,7 @@ from different CPUs.  This is the case in NUMA (Non-Uniform Memory
 Architecture) machines.  Preferably memory should be accessed locally
 but this requirement is usually not visible to the scheduler.
 Therefore forcing a process or thread to the CPUs which have local
-access to the mostly used memory helps to significantly boost the
+access to the most-used memory helps to significantly boost the
 performance.
 
 @item
@@ -1331,7 +1331,7 @@ problem.  The Linux kernel provides a set of interfaces to allow
 specifying @emph{affinity sets} for a process.  The scheduler will
 schedule the thread or process on CPUs specified by the affinity
 masks.  The interfaces which @theglibc{} define follow to some
-extend the Linux kernel interface.
+extent the Linux kernel interface.
 
 @comment sched.h
 @comment GNU
@@ -1345,7 +1345,7 @@ different interface has to be used.
 This type is a GNU extension and is defined in @file{sched.h}.
 @end deftp
 
-To manipulate the bitset, to set and reset bits, a number of macros is
+To manipulate the bitset, to set and reset bits, a number of macros are
 defined.  Some of the macros take a CPU number as a parameter.  Here
 it is important to never exceed the size of the bitset.  The following
 macro specifies the number of bits in the @code{cpu_set_t} bitset.
@@ -1432,7 +1432,7 @@ affinity mask can be retrieved from the system.
 @c Wrapped syscall to zero out past the kernel cpu set size; Linux
 @c only.
 
-This functions stores the CPU affinity mask for the process or thread
+This function stores the CPU affinity mask for the process or thread
 with the ID @var{pid} in the @var{cpusetsize} bytes long bitmap
 pointed to by @var{cpuset}.  If successful, the function always
 initializes all bits in the @code{cpu_set_t} object and returns zero.
@@ -1446,7 +1446,7 @@ and @code{errno} is set to represent the error condition.
 No process or thread with the given ID found.
 
 @item EFAULT
-The pointer @var{cpuset} is does not point to a valid object.
+The pointer @var{cpuset} does not point to a valid object.
 @end table
 
 This function is a GNU extension and is declared in @file{sched.h}.
@@ -1465,7 +1465,7 @@ interface must be provided for that.
 
 This function installs the @var{cpusetsize} bytes long affinity mask
 pointed to by @var{cpuset} for the process or thread with the ID @var{pid}.
-If successful the function returns zero and the scheduler will in future
+If successful the function returns zero and the scheduler will in the future
 take the affinity information into account.
 
 If the function fails it will return @code{-1} and @code{errno} is set
@@ -1476,7 +1476,7 @@ to the error code:
 No process or thread with the given ID found.
 
 @item EFAULT
-The pointer @var{cpuset} is does not point to a valid object.
+The pointer @var{cpuset} does not point to a valid object.
 
 @item EINVAL
 The bitset is not valid.  This might mean that the affinity set might
@@ -1518,7 +1518,7 @@ virtual addresses into physical addresses.  This is normally done by the
 hardware of the processor.
 
 @cindex shared memory
-Using a virtual address space has several advantage.  The most important
+Using a virtual address space has several advantages.  The most important
 is process isolation.  The different processes running on the system
 cannot interfere directly with each other.  No process can write into
 the address space of another process (except when shared memory is used
@@ -1548,16 +1548,16 @@ stores memory content externally it cannot do this on a byte-by-byte
 basis.  The administrative overhead does not allow this (leaving alone
 the processor hardware).  Instead several thousand bytes are handled
 together and form a @dfn{page}.  The size of each page is always a power
-of two byte.  The smallest page size in use today is 4096, with 8192,
+of two bytes.  The smallest page size in use today is 4096, with 8192,
 16384, and 65536 being other popular sizes.
 
 @node Query Memory Parameters
 @subsection How to get information about the memory subsystem?
 
 The page size of the virtual memory the process sees is essential to
-know in several situations.  Some programming interface (e.g.,
+know in several situations.  Some programming interfaces (e.g.,
 @code{mmap}, @pxref{Memory-mapped I/O}) require the user to provide
-information adjusted to the page size.  In the case of @code{mmap} is it
+information adjusted to the page size.  In the case of @code{mmap} it is
 necessary to provide a length argument which is a multiple of the page
 size.  Another place where the knowledge about the page size is useful
 is in memory allocation.  If one allocates pieces of memory in larger
@@ -1568,7 +1568,7 @@ of the page size the kernel's memory handling can work more effectively
 since it only has to allocate memory pages which are fully used.  (To do
 this optimization it is necessary to know a bit about the memory
 allocator which will require a bit of memory itself for each block and
-this overhead must not push the total size over the page size multiple.
+this overhead must not push the total size over the page size multiple.)
 
 The page size traditionally was a compile time constant.  But recent
 development of processors changed this.  Processors now support
@@ -1605,7 +1605,7 @@ information about the physical memory the system has.  The call
 @end smallexample
 
 @noindent
-returns the total number of pages of physical the system has.
+returns the total number of pages of physical memory the system has.
 This does not mean all this memory is available.  This information can
 be found using
 
@@ -1634,7 +1634,7 @@ get this information two functions.  They are declared in the file
 @safety{@prelim{}@mtsafe{}@asunsafe{@ascuheap{} @asulock{}}@acunsafe{@aculock{} @acsfd{} @acsmem{}}}
 @c This fopens a /proc file and scans it for the requested information.
 The @code{get_phys_pages} function returns the total number of pages of
-physical the system has.  To get the amount of memory this number has to
+physical memory the system has.  To get the amount of memory this number has to
 be multiplied by the page size.
 
 This function is a GNU extension.
@@ -1645,7 +1645,7 @@ This function is a GNU extension.
 @deftypefun {long int} get_avphys_pages (void)
 @safety{@prelim{}@mtsafe{}@asunsafe{@ascuheap{} @asulock{}}@acunsafe{@aculock{} @acsfd{} @acsmem{}}}
 The @code{get_avphys_pages} function returns the number of available pages of
-physical the system has.  To get the amount of memory this number has to
+physical memory the system has.  To get the amount of memory this number has to
 be multiplied by the page size.
 
 This function is a GNU extension.
@@ -1712,7 +1712,7 @@ This function is a GNU extension.
 Before starting more threads it should be checked whether the processors
 are not already overused.  Unix systems calculate something called the
 @dfn{load average}.  This is a number indicating how many processes were
-running.  This number is average over different periods of times
+running.  This number is an average over different periods of time
 (normally 1, 5, and 15 minutes).
 
 @comment stdlib.h

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=9269924c829e766ce43f8b2cf7460d622522b2a9

commit 9269924c829e766ce43f8b2cf7460d622522b2a9
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:14:36 2016 +0530

    Manual typos: Date and Time
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/time.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index d49ecdc..596ae14 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/time.texi: Fix typos in the manual.
+
 	* manual/arith.texi: Fix typos in the manual.
 
 	* manual/math.texi: Fix typos in the manual.
diff --git a/manual/time.texi b/manual/time.texi
index f94cbe4..6a899b7 100644
--- a/manual/time.texi
+++ b/manual/time.texi
@@ -26,7 +26,7 @@ we use a rigorous terminology to avoid confusion, and the only thing we
 use the simple word ``time'' for is to talk about the abstract concept.
 
 A @dfn{calendar time} is a point in the time continuum, for example
-November 4, 1990 at 18:02.5 UTC.  Sometimes this is called ``absolute
+November 4, 1990, at 18:02.5 UTC.  Sometimes this is called ``absolute
 time''.
 @cindex calendar time
 
@@ -298,7 +298,7 @@ child processes which have not yet been reported by @code{wait} or
 
 @item clock_t tms_cstime
 This is similar to @code{tms_cutime}, but represents the total processor
-time system has used on behalf of all the terminated child processes
+time the system has used on behalf of all the terminated child processes
 of the calling process.
 @end table
 
@@ -501,7 +501,7 @@ The @code{gettimeofday} function returns the current calendar time as
 the elapsed time since the epoch in the @code{struct timeval} structure
 indicated by @var{tp}.  (@pxref{Elapsed Time} for a description of
 @code{struct timeval}).  Information about the time zone is returned in
-the structure pointed at @var{tzp}.  If the @var{tzp} argument is a null
+the structure pointed to by @var{tzp}.  If the @var{tzp} argument is a null
 pointer, time zone information is ignored.
 
 The return value is @code{0} on success and @code{-1} on failure.  The
@@ -1010,7 +1010,7 @@ system clock from the true calendar time.
 The @code{ntp_gettime} function sets the structure pointed to by
 @var{tptr} to current values.  The elements of the structure afterwards
 contain the values the timer implementation in the kernel assumes.  They
-might or might not be correct.  If they are not a @code{ntp_adjtime}
+might or might not be correct.  If they are not, an @code{ntp_adjtime}
 call is necessary.
 
 The return value is @code{0} on success and other values on failure.  The
@@ -1220,7 +1220,7 @@ for at least 26 bytes, including the terminating null.
 
 If no error occurred the function returns a pointer to the string the
 result was written into, i.e., it returns @var{buffer}.  Otherwise
-return @code{NULL}.
+it returns @code{NULL}.
 @end deftypefun
 
 
@@ -1260,7 +1260,7 @@ gcc extensions, @pxref{Statement Exprs,,,gcc,Porting and Using gcc}):
 
 If no error occurred the function returns a pointer to the string the
 result was written into, i.e., it returns @var{buffer}.  Otherwise
-return @code{NULL}.
+it returns @code{NULL}.
 @end deftypefun
 
 
@@ -1360,7 +1360,7 @@ padded, since there is no natural width for them.
 
 Following the flag an optional specification of the width is possible.
 This is specified in decimal notation.  If the natural size of the
-output is of the field has less than the specified number of characters,
+output of the field has less than the specified number of characters,
 the result is written right adjusted and space padded to the given
 size.
 
@@ -1422,7 +1422,7 @@ The date using the format @code{%m/%d/%y}.
 This format was first standardized by POSIX.2-1992 and by @w{ISO C99}.
 
 @item %e
-The day of the month like with @code{%d}, but padded with blank (range
+The day of the month like with @code{%d}, but padded with spaces (range
 @code{ 1} through @code{31}).
 
 This format was first standardized by POSIX.2-1992 and by @w{ISO C99}.
@@ -1469,13 +1469,13 @@ The day of the year as a decimal number (range @code{001} through @code{366}).
 
 @item %k
 The hour as a decimal number, using a 24-hour clock like @code{%H}, but
-padded with blank (range @code{ 0} through @code{23}).
+padded with spaces (range @code{ 0} through @code{23}).
 
 This format is a GNU extension.
 
 @item %l
 The hour as a decimal number, using a 12-hour clock like @code{%I}, but
-padded with blank (range @code{ 1} through @code{12}).
+padded with spaces (range @code{ 1} through @code{12}).
 
 This format is a GNU extension.
 
@@ -1703,7 +1703,7 @@ function with the difference that it operates on wide character
 strings.  The buffer where the result is stored, pointed to by @var{s},
 must be an array of wide characters.  The parameter @var{size} which
 specifies the size of the output buffer gives the number of wide
-character, not the number of bytes.
+characters, not the number of bytes.
 
 Also the format string @var{template} is a wide character string.  Since
 all characters needed to specify the format string are in the basic
@@ -2105,7 +2105,7 @@ or date elements changed.  This has two implications:
 @item
 Before calling the @code{strptime} function for a new input string, you
 should prepare the @var{tm} structure you pass.  Normally this will mean
-initializing all values are to zero.  Alternatively, you can set all
+initializing all values to zero.  Alternatively, you can set all
 fields to values like @code{INT_MAX}, allowing you to determine which
 elements were set by the function call.  Zero does not work here since
 it is a valid value for many of the fields.
@@ -2121,7 +2121,7 @@ time information.  By parsing one after the other without clearing the
 structure in-between, you can construct a complete broken-down time.
 @end itemize
 
-The following example shows a function which parses a string which is
+The following example shows a function which parses a string which
 contains the date information in either US style or @w{ISO 8601} form:
 
 @smallexample
@@ -2225,7 +2225,7 @@ solution to this.
 
 @item
 If only the weekday is specified the selected day depends on the current
-date.  If the current weekday is greater or equal to the @code{tm_wday}
+date.  If the current weekday is greater than or equal to the @code{tm_wday}
 value the current week's day is chosen, otherwise the day next week is chosen.
 
 @item
@@ -2261,7 +2261,7 @@ run job at %I %p,%B %dnd
 
 As you can see, the template list can contain very specific strings like
 @code{run job at %I %p,%B %dnd}.  Using the above list of templates and
-assuming the current time is Mon Sep 22 12:19:47 EDT 1986 we can obtain the
+assuming the current time is Mon Sep 22 12:19:47 EDT 1986, we can obtain the
 following results for the given input.
 
 @multitable {xxxxxxxxxxxx} {xxxxxxxxxx} {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
@@ -2671,7 +2671,7 @@ To be able to use the alarm function to interrupt a system call which
 might block otherwise indefinitely it is important to @emph{not} set the
 @code{SA_RESTART} flag when registering the signal handler using
 @code{sigaction}.  When not using @code{sigaction} things get even
-uglier: the @code{signal} function has to fixed semantics with respect
+uglier: the @code{signal} function has fixed semantics with respect
 to restarts.  The BSD semantics for this function is to set the flag.
 Therefore, if @code{sigaction} for whatever reason cannot be used, it is
 necessary to use @code{sysv_signal} and not @code{signal}.
@@ -2774,7 +2774,7 @@ can do this by calling @code{alarm} with a @var{seconds} argument of
 zero.
 
 The return value indicates how many seconds remain before the previous
-alarm would have been sent.  If there is no previous alarm, @code{alarm}
+alarm would have been sent.  If there was no previous alarm, @code{alarm}
 returns zero.
 @end deftypefun
 
@@ -2831,10 +2831,10 @@ any descriptors to wait for.
 @c On Mach, it uses ports and calls time.  On generic posix, it calls
 @c nanosleep.  On Linux, it temporarily blocks SIGCHLD, which is MT- and
 @c AS-Unsafe, and in a way that makes it AC-Unsafe (C-unsafe, even!).
-The @code{sleep} function waits for @var{seconds} or until a signal
+The @code{sleep} function waits for @var{seconds} seconds or until a signal
 is delivered, whichever happens first.
 
-If @code{sleep} function returns because the requested interval is over,
+If @code{sleep} returns because the requested interval is over,
 it returns a value of zero.  If it returns because of delivery of a
 signal, its return value is the remaining time in the sleep interval.
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=e4fd1876e91bca446115edc40de0d03d00dd7483

commit e4fd1876e91bca446115edc40de0d03d00dd7483
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:12:26 2016 +0530

    Manual typos: Arithmetic Functions
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/arith.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 1dc3dc8..d49ecdc 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/arith.texi: Fix typos in the manual.
+
 	* manual/math.texi: Fix typos in the manual.
 
 	* manual/syslog.texi: Fix typos in the manual.
diff --git a/manual/arith.texi b/manual/arith.texi
index a13c46f..6ecde21 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -164,7 +164,7 @@ The remainder from the division.
 @deftypefun div_t div (int @var{numerator}, int @var{denominator})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 @c Functions in this section are pure, and thus safe.
-This function @code{div} computes the quotient and remainder from
+The function @code{div} computes the quotient and remainder from
 the division of @var{numerator} by @var{denominator}, returning the
 result in a structure of type @code{div_t}.
 
@@ -567,7 +567,7 @@ Division: @math{0/0} or @math{@infinity{}/@infinity{}}.
 Remainder: @math{x} REM @math{y}, where @math{y} is zero or @math{x} is
 infinite.
 @item
-Square root if the operand is less then zero.  More generally, any
+Square root if the operand is less than zero.  More generally, any
 mathematical function evaluated outside its domain produces this
 exception.
 @item
@@ -1027,7 +1027,7 @@ the calculation was negative, the result is @dfn{negative zero}.
 Negative zero can also result from some operations on infinity, such as
 @math{4/-@infinity{}}.
 
-At any time one of the above four rounding modes is selected.  You can
+At any time, one of the above four rounding modes is selected.  You can
 find out which one with this function:
 
 @comment fenv.h
@@ -1048,7 +1048,7 @@ To change the rounding mode, use this function:
 Changes the currently selected rounding mode to @var{round}.  If
 @var{round} does not correspond to one of the supported rounding modes
 nothing is changed.  @code{fesetround} returns zero if it changed the
-rounding mode, a nonzero value if the mode is not supported.
+rounding mode, or a nonzero value if the mode is not supported.
 @end deftypefun
 
 You should avoid changing the rounding mode if possible.  It can be an
@@ -1204,8 +1204,8 @@ occur, you can use the following two functions.
 @comment GNU
 @deftypefun int feenableexcept (int @var{excepts})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-This functions enables traps for each of the exceptions as indicated by
-the parameter @var{except}.  The individual exceptions are described in
+This function enables traps for each of the exceptions as indicated by
+the parameter @var{excepts}.  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.
 
@@ -1217,8 +1217,8 @@ operation was successful, @code{-1} otherwise.
 @comment GNU
 @deftypefun int fedisableexcept (int @var{excepts})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-This functions disables traps for each of the exceptions as indicated by
-the parameter @var{except}.  The individual exceptions are described in
+This function disables traps for each of the exceptions as indicated by
+the parameter @var{excepts}.  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.
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=60843ffbc2bb732ceea98673b8a6d39748d96e4a

commit 60843ffbc2bb732ceea98673b8a6d39748d96e4a
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:11:07 2016 +0530

    Manual typos: Mathematics
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/math.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index e643b08..1dc3dc8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/math.texi: Fix typos in the manual.
+
 	* manual/syslog.texi: Fix typos in the manual.
 
 	* manual/terminal.texi: Fix typos in the manual.
diff --git a/manual/math.texi b/manual/math.texi
index d689820..ccafb94 100644
--- a/manual/math.texi
+++ b/manual/math.texi
@@ -210,7 +210,7 @@ function to do that.
 @deftypefunx void sincosl (long double @var{x}, long double *@var{sinx}, long double *@var{cosx})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 These functions return the sine of @var{x} in @code{*@var{sinx}} and the
-cosine of @var{x} in @code{*@var{cos}}, where @var{x} is given in
+cosine of @var{x} in @code{*@var{cosx}}, where @var{x} is given in
 radians.  Both values, @code{*@var{sinx}} and @code{*@var{cosx}}, are in
 the range of @code{-1} to @code{1}.
 
@@ -303,7 +303,7 @@ pole.
 @section Inverse Trigonometric Functions
 @cindex inverse trigonometric functions
 
-These are the usual arc sine, arc cosine and arc tangent functions,
+These are the usual arcsine, arccosine and arctangent functions,
 which are the inverses of the sine, cosine and tangent functions
 respectively.
 
@@ -317,12 +317,12 @@ respectively.
 @comment ISO
 @deftypefunx {long double} asinl (long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the arc sine of @var{x}---that is, the value whose
+These functions compute the arcsine of @var{x}---that is, the value whose
 sine is @var{x}.  The value is in units of radians.  Mathematically,
 there are infinitely many such values; the one actually returned is the
 one between @code{-pi/2} and @code{pi/2} (inclusive).
 
-The arc sine function is defined mathematically only
+The arcsine function is defined mathematically only
 over the domain @code{-1} to @code{1}.  If @var{x} is outside the
 domain, @code{asin} signals a domain error.
 @end deftypefun
@@ -337,12 +337,12 @@ domain, @code{asin} signals a domain error.
 @comment ISO
 @deftypefunx {long double} acosl (long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the arc cosine of @var{x}---that is, the value
+These functions compute the arccosine of @var{x}---that is, the value
 whose cosine is @var{x}.  The value is in units of radians.
 Mathematically, there are infinitely many such values; the one actually
 returned is the one between @code{0} and @code{pi} (inclusive).
 
-The arc cosine function is defined mathematically only
+The arccosine function is defined mathematically only
 over the domain @code{-1} to @code{1}.  If @var{x} is outside the
 domain, @code{acos} signals a domain error.
 @end deftypefun
@@ -357,7 +357,7 @@ domain, @code{acos} signals a domain error.
 @comment ISO
 @deftypefunx {long double} atanl (long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the arc tangent of @var{x}---that is, the value
+These functions compute the arctangent of @var{x}---that is, the value
 whose tangent is @var{x}.  The value is in units of radians.
 Mathematically, there are infinitely many such values; the one actually
 returned is the one between @code{-pi/2} and @code{pi/2} (inclusive).
@@ -373,7 +373,7 @@ returned is the one between @code{-pi/2} and @code{pi/2} (inclusive).
 @comment ISO
 @deftypefunx {long double} atan2l (long double @var{y}, long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-This function computes the arc tangent of @var{y}/@var{x}, but the signs
+This function computes the arctangent of @var{y}/@var{x}, but the signs
 of both arguments are used to determine the quadrant of the result, and
 @var{x} is permitted to be zero.  The return value is given in radians
 and is in the range @code{-pi} to @code{pi}, inclusive.
@@ -402,7 +402,7 @@ If both @var{x} and @var{y} are zero, @code{atan2} returns zero.
 @comment ISO
 @deftypefunx {complex long double} casinl (complex long double @var{z})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the complex arc sine of @var{z}---that is, the
+These functions compute the complex arcsine of @var{z}---that is, the
 value whose sine is @var{z}.  The value returned is in radians.
 
 Unlike the real-valued functions, @code{casin} is defined for all
@@ -419,7 +419,7 @@ values of @var{z}.
 @comment ISO
 @deftypefunx {complex long double} cacosl (complex long double @var{z})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the complex arc cosine of @var{z}---that is, the
+These functions compute the complex arccosine of @var{z}---that is, the
 value whose cosine is @var{z}.  The value returned is in radians.
 
 Unlike the real-valued functions, @code{cacos} is defined for all
@@ -437,7 +437,7 @@ values of @var{z}.
 @comment ISO
 @deftypefunx {complex long double} catanl (complex long double @var{z})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions compute the complex arc tangent of @var{z}---that is,
+These functions compute the complex arctangent of @var{z}---that is,
 the value whose tangent is @var{z}.  The value is in units of radians.
 @end deftypefun
 
@@ -730,7 +730,7 @@ to subtraction of two numbers that are nearly equal.
 @comment ISO
 @deftypefunx {long double} log1pl (long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These functions returns a value equivalent to @w{@code{log (1 + @var{x})}}.
+These functions return a value equivalent to @w{@code{log (1 + @var{x})}}.
 They are computed in a way that is accurate even if @var{x} is
 near zero.
 @end deftypefun
@@ -873,7 +873,7 @@ may signal overflow if @var{x} is too large.
 @comment ISO
 @deftypefunx {long double} coshl (long double @var{x})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-These function return the hyperbolic cosine of @var{x},
+These functions return the hyperbolic cosine of @var{x},
 defined mathematically as @w{@code{(exp (@var{x}) + exp (-@var{x})) / 2}}.
 They may signal overflow if @var{x} is too large.
 @end deftypefun
@@ -1146,7 +1146,7 @@ instead of in the @var{signgam} global.  This means it is reentrant.
 @safety{@prelim{}@mtunsafe{@mtasurace{:signgam}}@asunsafe{}@acsafe{}}
 These functions exist for compatibility reasons.  They are equivalent to
 @code{lgamma} etc.  It is better to use @code{lgamma} since for one the
-name reflects better the actual computation, moreover @code{lgamma} is
+name reflects better the actual computation, and moreover @code{lgamma} is
 standardized in @w{ISO C99} while @code{gamma} is not.
 @end deftypefun
 
@@ -1298,7 +1298,7 @@ for functions in the math library, and does not aim for correctness in
 whether ``inexact'' exceptions are raised.  Instead, the goals for
 accuracy of functions without fully specified results are as follows;
 some functions have bugs meaning they do not meet these goals in all
-cases.  In future, @theglibc{} may provide some other correctly
+cases.  In the future, @theglibc{} may provide some other correctly
 rounding functions under the names such as @code{crsin} proposed for
 an extension to ISO C.
 
@@ -1583,7 +1583,7 @@ pseudo-random number generator.
 
 @Theglibc{} contains four additional functions which contain the
 state as an explicit parameter and therefore make it possible to handle
-thread-local PRNGs.  Beside this there is no difference.  In fact, the
+thread-local PRNGs.  Besides this there is no difference.  In fact, the
 four functions already discussed are implemented internally using the
 following interfaces.
 
@@ -1785,7 +1785,7 @@ the user has called the @code{lcong48} function (see below).
 The @code{seed48} function initializes all 48 bits of the state of the
 internal random number generator from the contents of the parameter
 @var{seed16v}.  Here the lower 16 bits of the first element of
-@var{see16v} initialize the least significant 16 bits of the internal
+@var{seed16v} initialize the least significant 16 bits of the internal
 state, the lower 16 bits of @code{@var{seed16v}[1]} initialize the mid-order
 16 bits of the state and the 16 lower bits of @code{@var{seed16v}[2]}
 initialize the most significant 16 bits of the state.
@@ -2027,7 +2027,7 @@ This means that no calls to the library functions may be necessary, and
 can increase the speed of generated code significantly.  The drawback is
 that code size will increase, and the increase is not always negligible.
 
-There are two kind of inline functions: Those that give the same result
+There are two kinds of inline functions: those that give the same result
 as the library functions and others that might not set @code{errno} and
 might have a reduced precision and/or argument range in comparison with
 the library functions.  The latter inline functions are only available

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=56e74aef9ca5a25735fdef78ef9fefe5f6ae990b

commit 56e74aef9ca5a25735fdef78ef9fefe5f6ae990b
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:08:46 2016 +0530

    Manual typos: Syslog
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/syslog.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 5e52306..e643b08 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/syslog.texi: Fix typos in the manual.
+
 	* manual/terminal.texi: Fix typos in the manual.
 
 	* manual/socket.texi: Fix typos in the manual.
diff --git a/manual/syslog.texi b/manual/syslog.texi
index a08e103..91fabc6 100644
--- a/manual/syslog.texi
+++ b/manual/syslog.texi
@@ -89,7 +89,7 @@ more meaning than the system administrator gives to it.
 
 @item priority
 This tells how important the content of the message is.  Examples of
-defined priority values are: debug, informational, warning, critical.
+defined priority values are: debug, informational, warning and critical.
 For the complete list, see @ref{syslog; vsyslog}.  Except for
 the fact that the priorities have a defined order, the meaning of each
 of these priorities is entirely determined by the system administrator.
@@ -257,7 +257,7 @@ If any other bit in @var{options} is on, the result is undefined.
 @var{facility} is the default facility code for this connection.  A
 @code{syslog} on this connection that specifies default facility causes
 this facility to be associated with the message.  See @code{syslog} for
-possible values.  A value of zero means the default default, which is
+possible values.  A value of zero means the default, which is
 @code{LOG_USER}.
 
 If a Syslog connection is already open when you call @code{openlog},

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=dc40b233526bb97b120636ad37f3b0f5d168e732

commit dc40b233526bb97b120636ad37f3b0f5d168e732
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:07:28 2016 +0530

    Manual typos: Low-Level Terminal Interface
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/terminal.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 4f13963..5e52306 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/terminal.texi: Fix typos in the manual.
+
 	* manual/socket.texi: Fix typos in the manual.
 
 	* manual/filesys.texi: Fix typos in the manual.
diff --git a/manual/terminal.texi b/manual/terminal.texi
index 0f0354b..49f5097 100644
--- a/manual/terminal.texi
+++ b/manual/terminal.texi
@@ -235,7 +235,7 @@ and set the attributes.
 @comment termios.h
 @comment POSIX.1
 @deftp {Data Type} {struct termios}
-Structure that records all the I/O attributes of a terminal.  The
+A @code{struct termios} records all the I/O attributes of a terminal.  The
 structure includes at least the following members:
 
 @table @code
@@ -869,7 +869,7 @@ input, without which @code{ECHOE} is simply irrelevant.
 @comment termios.h
 @comment BSD
 @deftypevr Macro tcflag_t ECHOPRT
-This bit is like @code{ECHOE}, enables display of the ERASE character in
+This bit, like @code{ECHOE}, enables display of the ERASE character in
 a way that is geared to a hardcopy terminal.  When you type the ERASE
 character, a @samp{\} character is printed followed by the first
 character erased.  Typing the ERASE character again just prints the next
@@ -933,7 +933,7 @@ This is a BSD extension, and exists only in BSD systems and
 This bit controls whether the INTR, QUIT, and SUSP characters are
 recognized.  The functions associated with these characters are performed
 if and only if this bit is set.  Being in canonical or noncanonical
-input mode has no affect on the interpretation of these characters.
+input mode has no effect on the interpretation of these characters.
 
 You should use caution when disabling recognition of these characters.
 Programs that cannot be interrupted interactively are very
@@ -1457,7 +1457,7 @@ The DSUSP (suspend) character is recognized only if the implementation
 supports job control (@pxref{Job Control}).  It sends a @code{SIGTSTP}
 signal, like the SUSP character, but not right away---only when the
 program tries to read it as input.  Not all systems with job control
-support DSUSP; only BSD-compatible systems (including @gnuhurdsystems{}).
+support DSUSP; only BSD-compatible systems do (including @gnuhurdsystems{}).
 
 @xref{Signal Handling}, for more information about signals.
 
@@ -1484,7 +1484,7 @@ input modes.  If @code{IXON} is set, receiving a START character resumes
 suspended output; the START character itself is discarded.  If
 @code{IXANY} is set, receiving any character at all resumes suspended
 output; the resuming character is not discarded unless it is the START
-character.  @code{IXOFF} is set, the system may also transmit START
+character.  If @code{IXOFF} is set, the system may also transmit START
 characters to the terminal.
 
 The usual value for the START character is @kbd{C-q}.  You may not be
@@ -1588,7 +1588,7 @@ The MIN and TIME are stored in elements of the @code{c_cc} array, which
 is a member of the @w{@code{struct termios}} structure.  Each element of
 this array has a particular role, and each element has a symbolic
 constant that stands for the index of that element.  @code{VMIN} and
-@code{VMAX} are the names for the indices in the array of the MIN and
+@code{VTIME} are the names for the indices in the array of the MIN and
 TIME slots.
 
 @comment termios.h
@@ -1702,7 +1702,7 @@ It does exactly this:
 
 The usual way to get and set terminal modes is with the functions described
 in @ref{Terminal Modes}.  However, on some systems you can use the
-BSD-derived functions in this section to do some of the same thing.  On
+BSD-derived functions in this section to do some of the same things.  On
 many systems, these functions do not exist.  Even with @theglibc{},
 the functions simply fail with @code{errno} = @code{ENOSYS} with many
 kernels, including Linux.
@@ -1749,7 +1749,7 @@ of the terminal which is open with file descriptor @var{filedes}.
 This function sets the attributes of a terminal.
 
 @code{stty} sets the terminal attributes of the terminal which is open with
-file descriptor @var{filedes} to those described by *@var{filedes}.
+file descriptor @var{filedes} to those described by *@var{attributes}.
 @end deftypefun
 
 @node Line Control
@@ -2254,7 +2254,7 @@ is not a null pointer, the file name of the slave pseudo-terminal
 device is stored in @code{*name}.  If @var{termp} is not a null pointer,
 the terminal attributes of the slave are set to the ones specified in
 the structure that @var{termp} points to (@pxref{Terminal Modes}).
-Likewise, if the @var{winp} is not a null pointer, the screen size of
+Likewise, if @var{winp} is not a null pointer, the screen size of
 the slave is set to the values specified in the structure that
 @var{winp} points to.
 

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=b57dd24684173a707c682ce9f249d549df5a66d8

commit b57dd24684173a707c682ce9f249d549df5a66d8
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:05:11 2016 +0530

    Manual typos: Sockets
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/socket.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 1cfb152..4f13963 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/socket.texi: Fix typos in the manual.
+
 	* manual/filesys.texi: Fix typos in the manual.
 
 	* manual/llio.texi: Fix typos in the manual.
diff --git a/manual/socket.texi b/manual/socket.texi
index 1d9d527..24b4563 100644
--- a/manual/socket.texi
+++ b/manual/socket.texi
@@ -254,7 +254,7 @@ address.  Other processes can find it for communication only if you
 give it an address.  We call this @dfn{binding} the address to the
 socket, and the way to do it is with the @code{bind} function.
 
-You need be concerned with the address of a socket if other processes
+You need only be concerned with the address of a socket if other processes
 are to find it and start communicating with it.  You can specify an
 address for other sockets, but this is usually pointless; the first time
 you send data from a socket, or use it to initiate a connection, the
@@ -662,8 +662,8 @@ To create a socket in the local namespace, use the constant
 @comment POSIX
 @deftypevr Macro int PF_LOCAL
 This designates the local namespace, in which socket addresses are local
-names, and its associated family of protocols.  @code{PF_Local} is the
-macro used by Posix.1g.
+names, and its associated family of protocols.  @code{PF_LOCAL} is the
+macro used by POSIX.1g.
 @end deftypevr
 
 @comment sys/socket.h
@@ -713,7 +713,7 @@ the file name string.  This can be done using the macro @code{SUN_LEN}:
 @comment BSD
 @deftypefn {Macro} int SUN_LEN (@emph{struct sockaddr_un *} @var{ptr})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-The macro computes the length of socket address in the local namespace.
+This macro computes the length of the socket address in the local namespace.
 @end deftypefn
 
 @node Local Socket Example
@@ -1148,7 +1148,7 @@ a pointer into a statically-allocated buffer.  Subsequent calls will
 overwrite the same buffer, so you should copy the string if you need
 to save it.
 
-In multi-threaded programs each thread has an own statically-allocated
+In multi-threaded programs each thread has its own statically-allocated
 buffer.  But still subsequent calls of @code{inet_ntoa} in the same
 thread will overwrite the result of the last call.
 
@@ -1464,7 +1464,7 @@ The host database contains an entry for the name, but it doesn't have an
 associated Internet address.
 @end table
 
-The lookup functions above all have one in common: they are not
+The lookup functions above all have one thing in common: they are not
 reentrant and therefore unusable in multi-threaded applications.
 Therefore provides @theglibc{} a new set of functions which can be
 used in this context.
@@ -1545,7 +1545,7 @@ used in this context.
 The @code{gethostbyname_r} function returns information about the host
 named @var{name}.  The caller must pass a pointer to an object of type
 @code{struct hostent} in the @var{result_buf} parameter.  In addition
-the function may need extra buffer space and the caller must pass an
+the function may need extra buffer space and the caller must pass a
 pointer and the size of the buffer in the @var{buf} and @var{buflen}
 parameters.
 
@@ -2527,7 +2527,7 @@ connection in progress (see @code{EINPROGRESS} above).
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -2663,7 +2663,7 @@ connections immediately available.
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -2797,7 +2797,7 @@ signal is ignored or blocked, or if its handler returns, then
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -2848,7 +2848,7 @@ You never connected this socket.
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -3163,7 +3163,7 @@ owing to a problem related to a previous call.
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -3202,7 +3202,7 @@ are also the same as for @code{recv}.
 
 This function is defined as a cancellation point in multi-threaded
 programs, so one has to be prepared for this and make sure that
-allocated resources (like memory, files descriptors, semaphores or
+allocated resources (like memory, file descriptors, semaphores or
 whatever) are freed even if the thread is canceled.
 @c @xref{pthread_cleanup_push}, for a method how to do this.
 @end deftypefun
@@ -3431,7 +3431,7 @@ They are declared in @file{sys/socket.h}.
 The @code{getsockopt} function gets information about the value of
 option @var{optname} at level @var{level} for socket @var{socket}.
 
-The option value is stored in a buffer that @var{optval} points to.
+The option value is stored in the buffer that @var{optval} points to.
 Before the call, you should supply in @code{*@var{optlen-ptr}} the
 size of this buffer; on return, it contains the number of bytes of
 information actually stored in the buffer.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=4ffa3672e174534916e2ec27fd2cfed4dcc70b22

commit 4ffa3672e174534916e2ec27fd2cfed4dcc70b22
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 12:01:51 2016 +0530

    Manual typos: File System Interface
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/filesys.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 7df31bc..1cfb152 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/filesys.texi: Fix typos in the manual.
+
 	* manual/llio.texi: Fix typos in the manual.
 
 	* manual/stdio.text: Fix typos in the manual.
diff --git a/manual/filesys.texi b/manual/filesys.texi
index a22c21f..26758e6 100644
--- a/manual/filesys.texi
+++ b/manual/filesys.texi
@@ -314,7 +314,7 @@ A symbolic link.
 This member is a BSD extension.  The symbol @code{_DIRENT_HAVE_D_TYPE}
 is defined if this member is available.  On systems where it is used, it
 corresponds to the file type bits in the @code{st_mode} member of
-@code{struct stat}.  If the value cannot be determine the member
+@code{struct stat}.  If the value cannot be determined the member
 value is DT_UNKNOWN.  These two macros convert between @code{d_type}
 values and @code{st_mode} values:
 
@@ -335,7 +335,7 @@ This returns the @code{st_mode} value corresponding to @var{dtype}.
 
 This structure may contain additional members in the future.  Their
 availability is always announced in the compilation environment by a
-macro names @code{_DIRENT_HAVE_D_@var{xxx}} where @var{xxx} is replaced
+macro named @code{_DIRENT_HAVE_D_@var{xxx}} where @var{xxx} is replaced
 by the name of the new member.  For instance, the member @code{d_reclen}
 available on some systems is announced through the macro
 @code{_DIRENT_HAVE_D_RECLEN}.
@@ -723,7 +723,7 @@ the result.
 
 The @code{scandir} function scans the contents of the directory selected
 by @var{dir}.  The result in *@var{namelist} is an array of pointers to
-structure of type @code{struct dirent} which describe all selected
+structures of type @code{struct dirent} which describe all selected
 directory entries and which is allocated using @code{malloc}.  Instead
 of always getting all directory entries returned, the user supplied
 function @var{selector} can be used to decide which entries are in the
@@ -742,7 +742,7 @@ directory could not be opened for reading or the malloc call failed) and
 the global variable @code{errno} contains more information on the error.
 @end deftypefun
 
-As described above the fourth argument to the @code{scandir} function
+As described above, the fourth argument to the @code{scandir} function
 must be a pointer to a sorting function.  For the convenience of the
 programmer @theglibc{} contains implementations of functions which
 are very helpful for this purpose.
@@ -1009,7 +1009,7 @@ the @var{filename} parameter and appending the names of all passed
 directories and then the local file name.  So the callback function can
 use this parameter to access the file.  @code{ftw} also calls
 @code{stat} for the file and passes that information on to the callback
-function.  If this @code{stat} call was not successful the failure is
+function.  If this @code{stat} call is not successful the failure is
 indicated by setting the third argument of the callback function to
 @code{FTW_NS}.  Otherwise it is set according to the description given
 in the account of @code{__ftw_func_t} above.
@@ -1261,7 +1261,7 @@ purpose is to obtain information about the link.  @code{link}, the
 function that makes a hard link, does too.  It makes a hard link to the
 symbolic link, which one rarely wants.
 
-Some systems have for some functions operating on files have a limit on
+Some systems have, for some functions operating on files, a limit on
 how many symbolic links are followed when resolving a path name.  The
 limit if it exists is published in the @file{sys/param.h} header file.
 
@@ -1271,7 +1271,7 @@ limit if it exists is published in the @file{sys/param.h} header file.
 
 The macro @code{MAXSYMLINKS} specifies how many symlinks some function
 will follow before returning @code{ELOOP}.  Not all functions behave the
-same and this value is not the same a that returned for
+same and this value is not the same as that returned for
 @code{_SC_SYMLOOP} by @code{sysconf}.  In fact, the @code{sysconf}
 result can indicate that there is no fixed limit although
 @code{MAXSYMLINKS} exists and has a finite value.
@@ -1376,7 +1376,7 @@ In some situations it is desirable to resolve all the
 symbolic links to get the real
 name of a file where no prefix names a symbolic link which is followed
 and no filename in the path is @code{.} or @code{..}.  This is for
-instance desirable if files have to be compare in which case different
+instance desirable if files have to be compared in which case different
 names can refer to the same inode.
 
 @comment stdlib.h
@@ -1392,7 +1392,7 @@ result is passed back as the return value of the function in a block of
 memory allocated with @code{malloc}.  If the result is not used anymore
 the memory should be freed with a call to @code{free}.
 
-If any of the path components is missing the function returns a NULL
+If any of the path components are missing the function returns a NULL
 pointer.  This is also what is returned if the length of the path
 reaches or exceeds @code{PATH_MAX} characters.  In any case
 @code{errno} is set accordingly.
@@ -1448,7 +1448,7 @@ This function is declared in @file{stdlib.h}.
 @end deftypefun
 
 The advantage of using this function is that it is more widely
-available.  The drawback is that it reports failures for long path on
+available.  The drawback is that it reports failures for long paths on
 systems which have no limits on the file name length.
 
 @node Deleting Files
@@ -1828,8 +1828,8 @@ might not be detected as sparse at all.  For practical applications,
 this is not a problem.
 
 @item unsigned int st_blksize
-The optimal block size for reading of writing this file, in bytes.  You
-might use this size for allocating the buffer space for reading of
+The optimal block size for reading or writing this file, in bytes.  You
+might use this size for allocating the buffer space for reading or
 writing the file.  (This is unrelated to @code{st_blocks}.)
 @end table
 @end deftp
@@ -2254,10 +2254,10 @@ This is the file type constant of a FIFO or pipe.
 @end table
 
 The POSIX.1b standard introduced a few more objects which possibly can
-be implemented as object in the filesystem.  These are message queues,
+be implemented as objects in the filesystem.  These are message queues,
 semaphores, and shared memory objects.  To allow differentiating these
-objects from other files the POSIX standard introduces three new test
-macros.  But unlike the other macros it does not take the value of the
+objects from other files the POSIX standard introduced three new test
+macros.  But unlike the other macros they do not take the value of the
 @code{st_mode} field as the parameter.  Instead they expect a pointer to
 the whole @code{struct stat} structure.
 
@@ -2265,7 +2265,7 @@ the whole @code{struct stat} structure.
 @comment POSIX
 @deftypefn Macro int S_TYPEISMQ (struct stat *@var{s})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-If the system implement POSIX message queues as distinct objects and the
+If the system implements POSIX message queues as distinct objects and the
 file is a message queue object, this macro returns a non-zero value.
 In all other cases the result is zero.
 @end deftypefn
@@ -2274,7 +2274,7 @@ In all other cases the result is zero.
 @comment POSIX
 @deftypefn Macro int S_TYPEISSEM (struct stat *@var{s})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-If the system implement POSIX semaphores as distinct objects and the
+If the system implements POSIX semaphores as distinct objects and the
 file is a semaphore object, this macro returns a non-zero value.
 In all other cases the result is zero.
 @end deftypefn
@@ -2283,7 +2283,7 @@ In all other cases the result is zero.
 @comment POSIX
 @deftypefn Macro int S_TYPEISSHM (struct stat *@var{s})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-If the system implement POSIX shared memory objects as distinct objects
+If the system implements POSIX shared memory objects as distinct objects
 and the file is a shared memory object, this macro returns a non-zero
 value.  In all other cases the result is zero.
 @end deftypefn
@@ -2760,7 +2760,7 @@ allow write access to files like @file{/etc/passwd}, which normally can
 be written only by the super-user, the modifying program will have to be
 owned by @code{root} and the setuid-bit must be set.
 
-But beside the files the program is intended to change the user should
+But besides the files the program is intended to change the user should
 not be allowed to access any file to which s/he would not have access
 anyway.  The program therefore must explicitly check whether @emph{the
 user} would have the necessary access to a file, before it reads or
@@ -2780,7 +2780,7 @@ want to try to keep track of the diverse features that different systems
 have.  Using @code{access} is simple and automatically does whatever is
 appropriate for the system you are using.
 
-@code{access} is @emph{only} only appropriate to use in setuid programs.
+@code{access} is @emph{only} appropriate to use in setuid programs.
 A non-setuid program will always use the effective ID rather than the
 real ID.
 
@@ -3230,7 +3230,7 @@ add (off_t at, void *block, size_t size)
 
 The function @code{add} writes a block of memory at an arbitrary
 position in the file.  If the current size of the file is too small it
-is extended.  Note the it is extended by a round number of pages.  This
+is extended.  Note that it is extended by a whole number of pages.  This
 is a requirement of @code{mmap}.  The program has to keep track of the
 real size, and when it has finished a final @code{ftruncate} call should
 set the real size of the file.

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=9739d2d501123ad2be48057a33c9f6b610a9c95e

commit 9739d2d501123ad2be48057a33c9f6b610a9c95e
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 11:58:02 2016 +0530

    Manual typos: Low-Level Input/Output
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/llio.texi: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 26fc3c1..7df31bc 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/llio.texi: Fix typos in the manual.
+
 	* manual/stdio.text: Fix typos in the manual.
 
 2016-10-05  Siddhesh Poyarekar  <siddhesh@sourceware.org>
diff --git a/manual/llio.texi b/manual/llio.texi
index 019dea2..e2697aa 100644
--- a/manual/llio.texi
+++ b/manual/llio.texi
@@ -103,7 +103,7 @@ for this function:
 @table @code
 @item EACCES
 The file exists but is not readable/writable as requested by the @var{flags}
-argument, the file does not exist and the directory is unwritable so
+argument, or the file does not exist and the directory is unwritable so
 it cannot be created.
 
 @item EEXIST
@@ -152,7 +152,7 @@ If on a 32 bit machine the sources are translated with
 descriptor opened in the large file mode which enables the file handling
 functions to use files up to @twoexp{63} bytes in size and offset from
 @minus{}@twoexp{63} to @twoexp{63}.  This happens transparently for the user
-since all of the lowlevel file handling functions are equally replaced.
+since all of the low-level file handling functions are equally replaced.
 
 This function is a cancellation point in multi-threaded programs.  This
 is a problem if the thread allocates some resources (like memory, file
@@ -203,7 +203,7 @@ If on a 32 bit machine the sources are translated with
 descriptor opened in the large file mode which enables the file handling
 functions to use files up to @twoexp{63} in size and offset from
 @minus{}@twoexp{63} to @twoexp{63}.  This happens transparently for the user
-since all of the lowlevel file handling functions are equally replaced.
+since all of the low-level file handling functions are equally replaced.
 @end deftypefn
 
 @comment fcntl.h
@@ -212,7 +212,7 @@ since all of the lowlevel file handling functions are equally replaced.
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{@acsfd{}}}
 This function is similar to @code{creat}.  It returns a file descriptor
 which can be used to access the file named by @var{filename}.  The only
-the difference is that on 32 bit systems the file is opened in the
+difference is that on 32 bit systems the file is opened in the
 large file mode.  I.e., file length and file offsets can exceed 31 bits.
 
 To use this file descriptor one must not use the normal operations but
@@ -364,7 +364,7 @@ or is not open for reading.
 
 @item EINTR
 @code{read} was interrupted by a signal while it was waiting for input.
-@xref{Interrupted Primitives}.  A signal will not necessary cause
+@xref{Interrupted Primitives}.  A signal will not necessarily cause
 @code{read} to return @code{EINTR}; it may instead result in a
 successful @code{read} which returns fewer bytes than requested.
 
@@ -433,7 +433,7 @@ error codes are also the same, with these additions:
 The value given for @var{offset} is negative and therefore illegal.
 
 @item ESPIPE
-The file descriptor @var{filedes} is associate with a pipe or a FIFO and
+The file descriptor @var{filedes} is associated with a pipe or a FIFO and
 this device does not allow positioning of the file pointer.
 @end table
 
@@ -903,7 +903,7 @@ do not permit the access specified by the @var{opentype} argument), a
 null pointer is returned instead.
 
 In some other systems, @code{fdopen} may fail to detect that the modes
-for file descriptor do not permit the access specified by
+for file descriptors do not permit the access specified by
 @code{opentype}.  @Theglibc{} always checks for this.
 @end deftypefun
 
@@ -1182,7 +1182,7 @@ Note that if the buffers are small (under about 1kB), high-level streams
 may be easier to use than these functions.  However, @code{readv} and
 @code{writev} are more efficient when the individual buffers themselves
 (as opposed to the total output), are large.  In that case, a high-level
-stream would not be able to cache the data effectively.
+stream would not be able to cache the data efficiently.
 
 @node Memory-mapped I/O
 @section Memory-mapped I/O
@@ -1281,7 +1281,7 @@ This forces the system to use the exact mapping address specified in
 @item MAP_ANONYMOUS
 @itemx MAP_ANON
 This flag tells the system to create an anonymous mapping, not connected
-to a file.  @var{filedes} and @var{off} are ignored, and the region is
+to a file.  @var{filedes} and @var{offset} are ignored, and the region is
 initialized with zeros.
 
 Anonymous maps are used as the basic primitive to extend the heap on some
@@ -1596,7 +1596,7 @@ On failure @code{errno} is set.
 @c  mempcpy dup ok
 @c  unlink dup ok
 
-This function is inverse of @code{shm_open} and removes the object with
+This function is the inverse of @code{shm_open} and removes the object with
 the given @var{name} previously created by @code{shm_open}.
 
 @code{shm_unlink} returns @math{0} on success or @math{-1} on error.
@@ -1863,7 +1863,7 @@ file descriptor.  E.g., in database files which do not change in size it
 is enough to write all the file content data to the device.
 Meta-information, like the modification time etc., are not that important
 and leaving such information uncommitted does not prevent a successful
-recovering of the file in case of a problem.
+recovery of the file in case of a problem.
 
 @comment unistd.h
 @comment POSIX
@@ -1897,7 +1897,7 @@ No synchronization is possible since the system does not implement this.
 @section Perform I/O Operations in Parallel
 
 The POSIX.1b standard defines a new set of I/O operations which can
-significantly reduce the time an application spends waiting at I/O.  The
+significantly reduce the time an application spends waiting for I/O.  The
 new functions allow a program to initiate one or more I/O operations and
 then immediately resume normal work while the I/O operations are
 executed in parallel.  This functionality is available if the
@@ -2035,16 +2035,16 @@ AIO operation.
 
 @item struct sigevent aio_sigevent
 This element specifies how the calling process is notified once the
-operation terminates.  If the @code{sigev_notify}, element is
+operation terminates.  If the @code{sigev_notify} element is
 @code{SIGEV_NONE} no notification is sent.  If it is @code{SIGEV_SIGNAL},
 the signal determined by @code{sigev_signo} is sent.  Otherwise,
 @code{sigev_notify} must be @code{SIGEV_THREAD} in which case a thread
-which starts executing the function pointed to by
+is created which starts executing the function pointed to by
 @code{sigev_notify_function}.
 
 @item int aio_lio_opcode
 This element is only used by the @code{lio_listio} and
-@code{[lio_listio64} functions.  Since these functions allow an
+@code{lio_listio64} functions.  Since these functions allow an
 arbitrary number of operations to start at once, and since each operation can be
 input or output (or nothing), the information must be stored in the
 control block.  See the description of @code{struct aiocb} for a description
@@ -2293,7 +2293,7 @@ difference is that on @w{32 bit} machines, the file descriptor should
 be opened in the large file mode.  Internally, @code{aio_read64} uses
 functionality equivalent to @code{lseek64} (@pxref{File Position
 Primitive}) to position the file descriptor correctly for the reading,
-as opposed to @code{lseek} functionality used in @code{aio_read}.
+as opposed to the @code{lseek} functionality used in @code{aio_read}.
 
 When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this
 function is available under the name @code{aio_read} and so transparently
@@ -2345,12 +2345,12 @@ request and so this error might also be signaled asynchronously.
 @end table
 
 In the case @code{aio_write} returns zero, the current status of the
-request can be queried using @code{aio_error} and @code{aio_return}
+request can be queried using the @code{aio_error} and @code{aio_return}
 functions.  As long as the value returned by @code{aio_error} is
 @code{EINPROGRESS} the operation has not yet completed.  If
 @code{aio_error} returns zero, the operation successfully terminated,
 otherwise the value is to be interpreted as an error code.  If the
-function terminated, the result of the operation can be get using a call
+function terminated, the result of the operation can be obtained using a call
 to @code{aio_return}.  The returned value is the same as an equivalent
 call to @code{read} would have returned.  Possible error codes returned
 by @code{aio_error} are:
@@ -2379,7 +2379,7 @@ difference is that on @w{32 bit} machines the file descriptor should
 be opened in the large file mode.  Internally @code{aio_write64} uses
 functionality equivalent to @code{lseek64} (@pxref{File Position
 Primitive}) to position the file descriptor correctly for the writing,
-as opposed to @code{lseek} functionality used in @code{aio_write}.
+as opposed to the @code{lseek} functionality used in @code{aio_write}.
 
 When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this
 function is available under the name @code{aio_write} and so transparently
@@ -2432,12 +2432,12 @@ waits until all requests terminated.  Otherwise @var{mode} must be
 having enqueued all the requests.  In this case the caller gets a
 notification of the termination of all requests according to the
 @var{sig} parameter.  If @var{sig} is @code{NULL} no notification is
-send.  Otherwise a signal is sent or a thread is started, just as
+sent.  Otherwise a signal is sent or a thread is started, just as
 described in the description for @code{aio_read} or @code{aio_write}.
 
 If @var{mode} is @code{LIO_WAIT}, the return value of @code{lio_listio}
 is @math{0} when all requests completed successfully.  Otherwise the
-function return @math{-1} and @code{errno} is set accordingly.  To find
+function returns @math{-1} and @code{errno} is set accordingly.  To find
 out which request or requests failed one has to use the @code{aio_error}
 function on all the elements of the array @var{list}.
 
@@ -2490,7 +2490,7 @@ difference is that on @w{32 bit} machines, the file descriptor should
 be opened in the large file mode.  Internally, @code{lio_listio64} uses
 functionality equivalent to @code{lseek64} (@pxref{File Position
 Primitive}) to position the file descriptor correctly for the reading or
-writing, as opposed to @code{lseek} functionality used in
+writing, as opposed to the @code{lseek} functionality used in
 @code{lio_listio}.
 
 When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this
@@ -2553,7 +2553,7 @@ machines.
 This function can be used to retrieve the return status of the operation
 carried out by the request described in the variable pointed to by
 @var{aiocbp}.  As long as the error status of this request as returned
-by @code{aio_error} is @code{EINPROGRESS} the return of this function is
+by @code{aio_error} is @code{EINPROGRESS} the return value of this function is
 undefined.
 
 Once the request is finished this function can be used exactly once to
@@ -2589,7 +2589,7 @@ machines.
 
 When dealing with asynchronous operations it is sometimes necessary to
 get into a consistent state.  This would mean for AIO that one wants to
-know whether a certain request or a group of request were processed.
+know whether a certain request or a group of requests were processed.
 This could be done by waiting for the notification sent by the system
 after the operation terminated, but this sometimes would mean wasting
 resources (mainly computation time).  Instead POSIX.1b defines two
@@ -2605,7 +2605,7 @@ if the symbol @code{_POSIX_SYNCHRONIZED_IO} is defined in @file{unistd.h}.
 @safety{@prelim{}@mtsafe{}@asunsafe{@asulock{} @ascuheap{}}@acunsafe{@aculock{} @acsmem{}}}
 @c After fcntl to check that the FD is open, it calls
 @c aio_enqueue_request.
-Calling this function forces all I/O operations operating queued at the
+Calling this function forces all I/O operations queued at the
 time of the function call operating on the file descriptor
 @code{aiocbp->aio_fildes} into the synchronized I/O completion state
 (@pxref{Synchronizing I/O}).  The @code{aio_fsync} function returns
@@ -2626,7 +2626,7 @@ done @code{aio_error} return @math{0} if the synchronization was not
 successful.  Otherwise the value returned is the value to which the
 @code{fsync} or @code{fdatasync} function would have set the
 @code{errno} variable.  In this case nothing can be assumed about the
-consistency for the data written to this file descriptor.
+consistency of the data written to this file descriptor.
 
 The return value of this function is @math{0} if the request was
 successfully enqueued.  Otherwise the return value is @math{-1} and
@@ -2669,9 +2669,9 @@ functions to notify the initiating process about the termination but in
 some situations this is not the ideal solution.  In a program which
 constantly updates clients somehow connected to the server it is not
 always the best solution to go round robin since some connections might
-be slow.  On the other hand letting the @code{aio_*} function notify the
+be slow.  On the other hand letting the @code{aio_*} functions notify the
 caller might also be not the best solution since whenever the process
-works on preparing data for on client it makes no sense to be
+works on preparing data for a client it makes no sense to be
 interrupted by a notification since the new client will not be handled
 before the current client is served.  For situations like this
 @code{aio_suspend} should be used.
@@ -2781,7 +2781,7 @@ The return value of the function is @code{AIO_CANCELED} if there were
 requests which haven't terminated and which were successfully canceled.
 If there is one or more requests left which couldn't be canceled, the
 return value is @code{AIO_NOTCANCELED}.  In this case @code{aio_error}
-must be used to find out which of the, perhaps multiple, requests (in
+must be used to find out which of the, perhaps multiple, requests (if
 @var{aiocbp} is @code{NULL}) weren't successfully canceled.  If all
 requests already terminated at the time @code{aio_cancel} is called the
 return value is @code{AIO_ALLDONE}.
@@ -2823,10 +2823,10 @@ The POSIX standard does not specify how the AIO functions are
 implemented.  They could be system calls, but it is also possible to
 emulate them at userlevel.
 
-At the point of this writing, the available implementation is a userlevel
+At the time of writing, the available implementation is a user-level
 implementation which uses threads for handling the enqueued requests.
 While this implementation requires making some decisions about
-limitations, hard limitations are something which is best avoided
+limitations, hard limitations are something best avoided
 in @theglibc{}.  Therefore, @theglibc{} provides a means
 for tuning the AIO implementation according to the individual use.
 
@@ -2867,13 +2867,13 @@ This function must be called before any other AIO function.  Calling it
 is completely voluntary, as it is only meant to help the AIO
 implementation perform better.
 
-Before calling the @code{aio_init}, function the members of a variable of
+Before calling @code{aio_init}, the members of a variable of
 type @code{struct aioinit} must be initialized.  Then a reference to
 this variable is passed as the parameter to @code{aio_init} which itself
 may or may not pay attention to the hints.
 
 The function has no return value and no error cases are defined.  It is
-a extension which follows a proposal from the SGI implementation in
+an extension which follows a proposal from the SGI implementation in
 @w{Irix 6}.  It is not covered by POSIX.1b or Unix98.
 @end deftypefun
 
@@ -3361,7 +3361,7 @@ clobber an existing file.
 This prevents @code{open} from blocking for a ``long time'' to open the
 file.  This is only meaningful for some kinds of files, usually devices
 such as serial ports; when it is not meaningful, it is harmless and
-ignored.  Often opening a port to a modem blocks until the modem reports
+ignored.  Often, opening a port to a modem blocks until the modem reports
 carrier detection; if @code{O_NONBLOCK} is specified, @code{open} will
 return immediately without a carrier.
 
@@ -3680,7 +3680,7 @@ can be one of @code{SEEK_SET}, @code{SEEK_CUR}, or @code{SEEK_END}.
 
 @item off_t l_start
 This specifies the offset of the start of the region to which the lock
-applies, and is given in bytes relative to the point specified by
+applies, and is given in bytes relative to the point specified by the
 @code{l_whence} member.
 
 @item off_t l_len
@@ -3759,8 +3759,8 @@ on that part is replaced with the new lock.  You can remove a lock
 by specifying a lock type of @code{F_UNLCK}.
 
 If the lock cannot be set, @code{fcntl} returns immediately with a value
-of @math{-1}.  This function does not block waiting for other processes
-to release locks.  If @code{fcntl} succeeds, it return a value other
+of @math{-1}.  This function does not block while waiting for other processes
+to release locks.  If @code{fcntl} succeeds, it returns a value other
 than @math{-1}.
 
 The following @code{errno} error conditions are defined for this

http://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=c703cd7abbdbe7847562cebb48a1c5cca57dde63

commit c703cd7abbdbe7847562cebb48a1c5cca57dde63
Author: Rical Jasan <ricaljasan@pacific.net>
Date:   Thu Oct 6 11:55:58 2016 +0530

    Manual typos: Input/Output on Streams
    
    2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
    
    	* manual/stdio.text: Fix typos in the manual.

diff --git a/ChangeLog b/ChangeLog
index 2495a2e..26fc3c1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
+
+	* manual/stdio.text: Fix typos in the manual.
+
 2016-10-05  Siddhesh Poyarekar  <siddhesh@sourceware.org>
 
 	* sysdeps/ieee754/dbl-64/s_sin.c (do_sincos_1): Check N
diff --git a/manual/stdio.texi b/manual/stdio.texi
index 0326f29..355c563 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -250,7 +250,7 @@ meaningful in other systems.
 
 If the open fails, @code{fopen} returns a null pointer.
 
-When the sources are compiling with @code{_FILE_OFFSET_BITS == 64} on a
+When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
 32 bit machine this function is in fact @code{fopen64} since the LFS
 interface replaces transparently the old interface.
 @end deftypefun
@@ -325,7 +325,7 @@ hard-coded.  In @theglibc{}, you can simply close the standard
 streams and open new ones with @code{fopen}.  But other systems lack
 this ability, so using @code{freopen} is more portable.
 
-When the sources are compiling with @code{_FILE_OFFSET_BITS == 64} on a
+When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
 32 bit machine this function is in fact @code{freopen64} since the LFS
 interface replaces transparently the old interface.
 @end deftypefun
@@ -374,7 +374,7 @@ is nonzero.  For read-only streams the function returns zero.
 This function is declared in @file{stdio_ext.h}.
 @end deftypefun
 
-For slightly different kind of problems there are two more functions.
+For slightly different kinds of problems there are two more functions.
 They provide even finer-grained information.
 
 @comment stdio_ext.h
@@ -458,7 +458,7 @@ another function.
 @c streams, without any locking.  It's the flushing without locking that
 @c makes it unsafe.
 This function causes all open streams of the process to be closed and
-the connection to corresponding files to be broken.  All buffered data
+the connections to corresponding files to be broken.  All buffered data
 is written and any buffered input is discarded.  The @code{fcloseall}
 function returns a value of @code{0} if all the files were closed
 successfully, and @code{EOF} if an error was detected.
@@ -490,7 +490,7 @@ Streams can be used in multi-threaded applications in the same way they
 are used in single-threaded applications.  But the programmer must be
 aware of the possible complications.  It is important to know about
 these also if the program one writes never use threads since the design
-and implementation of many stream functions is heavily influenced by the
+and implementation of many stream functions are heavily influenced by the
 requirements added by multi-threaded programming.
 
 The POSIX standard requires that by default the stream operations are
@@ -519,7 +519,7 @@ perform the stream locking in the application code.
 The @code{flockfile} function acquires the internal locking object
 associated with the stream @var{stream}.  This ensures that no other
 thread can explicitly through @code{flockfile}/@code{ftrylockfile} or
-implicit through a call of a stream function lock the stream.  The
+implicitly through the call of a stream function lock the stream.  The
 thread will block until the lock is acquired.  An explicit call to
 @code{funlockfile} has to be used to release the lock.
 @end deftypefun
@@ -566,7 +566,7 @@ FILE *fp;
 @end smallexample
 
 Without the explicit locking it would be possible for another thread to
-use the stream @var{fp} after the @code{fputs} call return and before
+use the stream @var{fp} after the @code{fputs} call returns and before
 @code{fprintf} was called with the result that the number does not
 follow the word @samp{number}.
 
@@ -609,7 +609,7 @@ foo (FILE *fp)
 @}
 @end smallexample
 
-Now that we covered why it is necessary to have these locking it is
+Now that we covered why it is necessary to have locking it is
 necessary to talk about situations when locking is unwanted and what can
 be done.  The locking operations (explicit or implicit) don't come for
 free.  Even if a lock is not taken the cost is not zero.  The operations
@@ -688,7 +688,7 @@ locking.  Every stream operation with exception of the @code{_unlocked}
 variants will implicitly lock the stream.
 
 @item FSETLOCKING_BYCALLER
-After the @code{__fsetlocking} function returns the user is responsible
+After the @code{__fsetlocking} function returns, the user is responsible
 for locking the stream.  None of the stream operations will implicitly
 do this anymore until the state is set back to
 @code{FSETLOCKING_INTERNAL}.
@@ -758,12 +758,12 @@ call to @code{freopen} or @code{freopen64} can reset the
 
 @itemize @bullet
 @item
-If any of the normal character functions is used (this includes the
+If any of the normal character functions are used (this includes the
 @code{fread} and @code{fwrite} functions) the stream is marked as not
 wide oriented.
 
 @item
-If any of the wide character functions is used the stream is marked as
+If any of the wide character functions are used the stream is marked as
 wide oriented.
 
 @item
@@ -773,7 +773,7 @@ The @code{fwide} function can be used to set the orientation either way.
 It is important to never mix the use of wide and not wide operations on
 a stream.  There are no diagnostics issued.  The application behavior
 will simply be strange or the application will simply crash.  The
-@code{fwide} function can help avoiding this.
+@code{fwide} function can help avoid this.
 
 @comment wchar.h
 @comment ISO
@@ -831,7 +831,7 @@ print_f (FILE *fp)
 
 Note that in this case the function @code{print_f} decides about the
 orientation of the stream if it was unoriented before (will not happen
-if the advise above is followed).
+if the advice above is followed).
 
 The encoding used for the @code{wchar_t} values is unspecified and the
 user must not make any assumptions about it.  For I/O of @code{wchar_t}
@@ -843,7 +843,7 @@ chosen by the implementation for @code{wchar_t}.  The external encoding
 is determined by the @code{LC_CTYPE} category of the current locale or
 by the @samp{ccs} part of the mode specification given to @code{fopen},
 @code{fopen64}, @code{freopen}, or @code{freopen64}.  How and when the
-conversion happens is unspecified and it happens invisible to the user.
+conversion happens is unspecified and it happens invisibly to the user.
 
 Since a stream is created in the unoriented state it has at that point
 no conversion associated with it.  The conversion which will be used is
@@ -860,7 +860,7 @@ possible, perhaps with a call to @code{fwide}.
 This section describes functions for performing character- and
 line-oriented output.
 
-These narrow streams functions are declared in the header file
+These narrow stream functions are declared in the header file
 @file{stdio.h} and the wide stream functions in @file{wchar.h}.
 @pindex stdio.h
 @pindex wchar.h
@@ -1079,7 +1079,7 @@ recommend you use @code{fwrite} instead (@pxref{Block Input/Output}).
 
 @cindex reading from a stream, by characters
 This section describes functions for performing character-oriented
-input.  These narrow streams functions are declared in the header file
+input.  These narrow stream functions are declared in the header file
 @file{stdio.h} and the wide character functions are declared in
 @file{wchar.h}.
 @pindex stdio.h
@@ -1789,7 +1789,7 @@ extension allows an explicit parameter to be specified.
 
 The @var{param-no} parts of the format must be integers in the range of
 1 to the maximum number of arguments present to the function call.  Some
-implementations limit this number to a certainly upper bound.  The exact
+implementations limit this number to a certain upper bound.  The exact
 limit can be retrieved by the following constant.
 
 @defvr Macro NL_ARGMAX
@@ -1799,7 +1799,7 @@ actual value in effect at runtime can be retrieved by using
 @code{sysconf} using the @code{_SC_NL_ARGMAX} parameter @pxref{Sysconf
 Definition}.
 
-Some system have a quite low limit such as @math{9} for @w{System V}
+Some systems have a quite low limit such as @math{9} for @w{System V}
 systems.  @Theglibc{} has no real limit.
 @end defvr
 
@@ -1908,7 +1908,7 @@ lower-case letters and @samp{%G} uses upper-case.  @xref{Floating-Point
 Conversions}, for details.
 
 @item @samp{%a}, @samp{%A}
-Print a floating-point number in a hexadecimal fractional notation which
+Print a floating-point number in a hexadecimal fractional notation with
 the exponent to base 2 represented in decimal digits.  @samp{%a} uses
 lower-case letters and @samp{%A} uses upper-case.  @xref{Floating-Point
 Conversions}, for details.
@@ -2023,7 +2023,7 @@ modifiers:
 Specifies that the argument is a @code{signed char} or @code{unsigned
 char}, as appropriate.  A @code{char} argument is converted to an
 @code{int} or @code{unsigned int} by the default argument promotions
-anyway, but the @samp{h} modifier says to convert it back to a
+anyway, but the @samp{hh} modifier says to convert it back to a
 @code{char} again.
 
 This modifier was introduced in @w{ISO C99}.
@@ -2043,7 +2043,7 @@ This modifier was introduced in @w{ISO C99}.
 
 @item l
 Specifies that the argument is a @code{long int} or @code{unsigned long
-int}, as appropriate.  Two @samp{l} characters is like the @samp{L}
+int}, as appropriate.  Two @samp{l} characters are like the @samp{L}
 modifier, below.
 
 If used with @samp{%c} or @samp{%s} the corresponding parameter is
@@ -2139,7 +2139,7 @@ a decimal-point character appears only if it is followed by a digit.
 The @samp{%a} and @samp{%A} conversions are meant for representing
 floating-point numbers exactly in textual form so that they can be
 exchanged as texts between different programs and/or machines.  The
-numbers are represented is the form
+numbers are represented in the form
 @w{[@code{-}]@code{0x}@var{h}@code{.}@var{hhh}@code{p}[@code{+}|@code{-}]@var{dd}}.
 At the left of the decimal-point character exactly one digit is print.
 This character is only @code{0} if the number is denormalized.
@@ -2265,7 +2265,7 @@ printf ("%c%c%c%c%c", 'h', 'e', 'l', 'l', 'o');
 @noindent
 prints @samp{hello}.
 
-If there is a @samp{l} modifier present the argument is expected to be
+If there is an @samp{l} modifier present the argument is expected to be
 of type @code{wint_t}.  If used in a multibyte function the wide
 character is converted into a multibyte character before being added to
 the output.  In this case more than one output byte can be produced.
@@ -2273,7 +2273,7 @@ the output.  In this case more than one output byte can be produced.
 The @samp{%s} conversion prints a string.  If no @samp{l} modifier is
 present the corresponding argument must be of type @code{char *} (or
 @code{const char *}).  If used in a wide stream function the string is
-first converted in a wide character string.  A precision can be
+first converted to a wide character string.  A precision can be
 specified to indicate the maximum number of characters to write;
 otherwise characters in the string up to but not including the
 terminating null character are written to the output stream.  The
@@ -2288,7 +2288,8 @@ printf ("%3s%-6s", "no", "where");
 @noindent
 prints @samp{ nowhere }.
 
-If there is a @samp{l} modifier present the argument is expected to be of type @code{wchar_t} (or @code{const wchar_t *}).
+If there is an @samp{l} modifier present, the argument is expected to
+be of type @code{wchar_t} (or @code{const wchar_t *}).
 
 If you accidentally pass a null pointer as the argument for a @samp{%s}
 conversion, @theglibc{} prints it as @samp{(null)}.  We think this
@@ -2441,7 +2442,7 @@ described below.
 
 @comment wchar.h
 @comment GNU
-@deftypefun int swprintf (wchar_t *@var{s}, size_t @var{size}, const wchar_t *@var{template}, @dots{})
+@deftypefun int swprintf (wchar_t *@var{ws}, size_t @var{size}, const wchar_t *@var{template}, @dots{})
 @safety{@prelim{}@mtsafe{@mtslocale{}}@asunsafe{@ascuheap{}}@acunsafe{@acsmem{}}}
 This is like @code{wprintf}, except that the output is stored in the
 wide character array @var{ws} instead of written to a stream.  A null
@@ -2477,7 +2478,7 @@ If @var{size} is zero, nothing, not even the null byte, shall be written and
 
 The return value is the number of characters which would be generated
 for the given input, excluding the trailing null.  If this value is
-greater or equal to @var{size}, not all characters from the result have
+greater than or equal to @var{size}, not all characters from the result have
 been stored in @var{s}.  You should try again with a bigger output
 string.  Here is an example of doing this:
 
@@ -2720,7 +2721,7 @@ specified directly as for @code{vprintf}.
 
 @comment wchar.h
 @comment GNU
-@deftypefun int vswprintf (wchar_t *@var{s}, size_t @var{size}, const wchar_t *@var{template}, va_list @var{ap})
+@deftypefun int vswprintf (wchar_t *@var{ws}, size_t @var{size}, const wchar_t *@var{template}, va_list @var{ap})
 @safety{@prelim{}@mtsafe{@mtslocale{}}@asunsafe{@ascuheap{}}@acunsafe{@acsmem{}}}
 This is the equivalent of @code{swprintf} with the variable argument list
 specified directly as for @code{vwprintf}.
@@ -3639,10 +3640,10 @@ Matches a string of one or more characters; the number of characters
 read is controlled by the maximum field width given for the conversion.
 @xref{String Input Conversions}.
 
-If the @samp{%c} is used in a wide stream function the read value is
+If @samp{%c} is used in a wide stream function the read value is
 converted from a wide character to the corresponding multibyte character
 before storing it.  Note that this conversion can produce more than one
-byte of output and therefore the provided buffer be large enough for up
+byte of output and therefore the provided buffer must be large enough for up
 to @code{MB_CUR_MAX} bytes for each character.  If @samp{%lc} is used in
 a multibyte function the input is treated as a multibyte sequence (and
 not bytes) and the result is converted as with calls to @code{mbrtowc}.
@@ -3803,7 +3804,7 @@ conversions:
 @item
 Provide a buffer to store it in.  This is the default.  You should
 provide an argument of type @code{char *} or @code{wchar_t *} (the
-latter of the @samp{l} modifier is present).
+latter if the @samp{l} modifier is present).
 
 @strong{Warning:} To make a robust program, you must make sure that the
 input (plus its terminating null) cannot possibly exceed the size of the
@@ -3834,7 +3835,7 @@ If the format is @samp{%lc} or @samp{%C} the function stores wide
 characters which are converted using the conversion determined at the
 time the stream was opened from the external byte stream.  The number of
 bytes read from the medium is limited by @code{MB_CUR_LEN * @var{n}} but
-at most @var{n} wide character get stored in the output string.
+at most @var{n} wide characters get stored in the output string.
 
 The @samp{%s} conversion matches a string of non-whitespace characters.
 It skips and discards initial whitespace, but stops when it encounters
@@ -3881,7 +3882,7 @@ last character of the set) is used to specify a range of characters.
 
 @item
 If a caret character @samp{^} immediately follows the initial @samp{[},
-then the set of allowed input characters is the everything @emph{except}
+then the set of allowed input characters is everything @emph{except}
 the characters listed.
 @end itemize
 
@@ -4450,7 +4451,7 @@ For this reason it is a good idea to prefer @code{ftello} whenever it is
 available since its functionality is (if different at all) closer the
 underlying definition.
 
-The functionality and return value is the same as for @code{fseek}.
+The functionality and return value are the same as for @code{fseek}.
 
 The function is an extension defined in the Unix Single Specification
 version 2.
@@ -4489,7 +4490,7 @@ function (@pxref{I/O Primitives}) and to specify offsets for file locks
 @comment ISO
 @deftypevr Macro int SEEK_SET
 This is an integer constant which, when used as the @var{whence}
-argument to the @code{fseek} or @code{fseeko} function, specifies that
+argument to the @code{fseek} or @code{fseeko} functions, specifies that
 the offset provided is relative to the beginning of the file.
 @end deftypevr
 
@@ -4497,7 +4498,7 @@ the offset provided is relative to the beginning of the file.
 @comment ISO
 @deftypevr Macro int SEEK_CUR
 This is an integer constant which, when used as the @var{whence}
-argument to the @code{fseek} or @code{fseeko} function, specifies that
+argument to the @code{fseek} or @code{fseeko} functions, specifies that
 the offset provided is relative to the current file position.
 @end deftypevr
 
@@ -4505,7 +4506,7 @@ the offset provided is relative to the current file position.
 @comment ISO
 @deftypevr Macro int SEEK_END
 This is an integer constant which, when used as the @var{whence}
-argument to the @code{fseek} or @code{fseeko} function, specifies that
+argument to the @code{fseek} or @code{fseeko} functions, specifies that
 the offset provided is relative to the end of the file.
 @end deftypevr
 
@@ -4848,7 +4849,7 @@ The @code{__fpurge} function causes the buffer of the stream
 @var{stream} to be emptied.  If the stream is currently in read mode all
 input in the buffer is lost.  If the stream is in output mode the
 buffered output is not written to the device (or whatever other
-underlying storage) and the buffer the cleared.
+underlying storage) and the buffer is cleared.
 
 This function is declared in @file{stdio_ext.h}.
 @end deftypefun
@@ -5015,7 +5016,7 @@ This function is declared in the @file{stdio_ext.h} header.
 @safety{@prelim{}@mtsafe{@mtsrace{:stream}}@asunsafe{@asucorrupt{}}@acsafe{}}
 The @code{__fpending}
 function returns the number of bytes currently in the output buffer.
-For wide-oriented stream the measuring unit is wide characters.  This
+For wide-oriented streams the measuring unit is wide characters.  This
 function should not be used on buffers in read mode or opened read-only.
 
 This function is declared in the @file{stdio_ext.h} header.
@@ -5583,7 +5584,7 @@ the @code{fmtsmg} function is.  It is available on System V systems.
 @node Example
 @subsection How to use @code{fmtmsg} and @code{addseverity}
 
-Here is a simple example program to illustrate the use of the both
+Here is a simple example program to illustrate the use of both
 functions described in this section.
 
 @smallexample
@@ -5613,7 +5614,7 @@ TO FIX: refer to manual UX:cat:001
 @end smallexample
 
 We see the different fields of the message and how the extra glue (the
-colons and the @code{TO FIX} string) are printed.  But only one of the
+colons and the @code{TO FIX} string) is printed.  But only one of the
 three calls to @code{fmtmsg} produced output.  The first call does not
 print anything because the @var{label} parameter is not in the correct
 form.  The string must contain two fields, separated by a colon

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog            |   62 +++++++++++++++++++++++++++++++++++++
 INSTALL              |    8 ++--
 manual/argp.texi     |   10 +++---
 manual/arith.texi    |   16 +++++-----
 manual/conf.texi     |   10 +++---
 manual/contrib.texi  |    6 ++--
 manual/crypt.texi    |    8 ++--
 manual/debug.texi    |    4 +-
 manual/filesys.texi  |   42 ++++++++++++------------
 manual/getopt.texi   |   10 +++---
 manual/install.texi  |    6 ++--
 manual/job.texi      |    2 +-
 manual/lang.texi     |    4 +-
 manual/llio.texi     |   74 ++++++++++++++++++++++----------------------
 manual/maint.texi    |    2 +-
 manual/math.texi     |   36 +++++++++++-----------
 manual/nss.texi      |   36 +++++++++++-----------
 manual/probes.texi   |    4 +-
 manual/process.texi  |    2 +-
 manual/resource.texi |   52 +++++++++++++++---------------
 manual/setjmp.texi   |    8 ++--
 manual/signal.texi   |    6 ++--
 manual/socket.texi   |   28 ++++++++--------
 manual/startup.texi  |    8 ++--
 manual/stdio.texi    |   83 +++++++++++++++++++++++++------------------------
 manual/sysinfo.texi  |   50 +++++++++++++++---------------
 manual/syslog.texi   |    4 +-
 manual/terminal.texi |   18 +++++-----
 manual/threads.texi  |    2 +-
 manual/time.texi     |   38 +++++++++++-----------
 manual/users.texi    |   33 +++++++++----------
 31 files changed, 367 insertions(+), 305 deletions(-)


hooks/post-receive
-- 
GNU C Library master sources


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]