[PATCH 00/37] Manual typos: Overview

[PATCH 00/37] Manual typos: Overview

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 2006 bytes --]

Typos addressed in this patchset include obvious mistakes such as
repeated repeated words, wrong case or tense, speling mistakes, and
wrong variable names.  The occasional comma is also addressed, where
its absence introduces ambiguity, or its presence disturbs the
sentence.

Verified patches apply cleanly against latest master and that `make
info|html|pdf' completes without error on x86_64.

---
 INSTALL              |    8 +--
 manual/argp.texi     |   10 ++--
 manual/arith.texi    |   16 ++---
 manual/charset.texi  |   68 ++++++++++-----------
 manual/conf.texi     |   10 ++--
 manual/contrib.texi  |    6 +-
 manual/crypt.texi    |    8 +--
 manual/ctype.texi    |    4 +-
 manual/debug.texi    |    4 +-
 manual/errno.texi    |   22 +++----
 manual/filesys.texi  |   42 ++++++-------
 manual/getopt.texi   |   10 ++--
 manual/install.texi  |    6 +-
 manual/intro.texi    |    2 +-
 manual/job.texi      |    2 +-
 manual/lang.texi     |    4 +-
 manual/llio.texi     |   78 ++++++++++++-------------
 manual/locale.texi   |   16 ++---
 manual/maint.texi    |    2 +-
 manual/math.texi     |   36 ++++++------
 manual/memory.texi   |   24 ++++----
 manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
 manual/nss.texi      |   44 +++++++-------
 manual/pattern.texi  |   24 ++++----
 manual/probes.texi   |    4 +-
 manual/process.texi  |    2 +-
 manual/resource.texi |   52 ++++++++---------
 manual/search.texi   |   36 ++++++------
 manual/setjmp.texi   |    8 +--
 manual/signal.texi   |    6 +-
 manual/socket.texi   |   28 ++++-----
 manual/startup.texi  |    8 +--
 manual/stdio.texi    |   85 ++++++++++++++-------------
 manual/string.texi   |   24 ++++----
 manual/sysinfo.texi  |   52 ++++++++---------
 manual/syslog.texi   |    4 +-
 manual/terminal.texi |   18 +++---
 manual/threads.texi  |    2 +-
 manual/time.texi     |   40 ++++++-------
 manual/users.texi    |   35 ++++++-----
 40 files changed, 504 insertions(+), 505 deletions(-)

-- 
1.7.9.5

[PATCH 20/37] Manual typos: Resource Usage and Limitation

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 237 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/resource.texi: Fix typos in the manual.
---
 manual/resource.texi |   52 +++++++++++++++++++++++++-------------------------
 1 file changed, 26 insertions(+), 26 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0020-Manual-typos-Resource-Usage-and-Limitation.patch --]
[-- Type: text/x-patch; name="0020-Manual-typos-Resource-Usage-and-Limitation.patch", Size: 12024 bytes --]

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

Re: [PATCH 20/37] Manual typos: Resource Usage and Limitation

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/resource.texi: Fix typos in the manual.
> ---
>  manual/resource.texi |   52 +++++++++++++++++++++++++-------------------------
>  1 file changed, 26 insertions(+), 26 deletions(-)
>

[PATCH 33/37] Manual typos: Internal probes

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 185 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/probes.texi: Fix typos in the manual.
---
 manual/probes.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0033-Manual-typos-Internal-probes.patch --]
[-- Type: text/x-patch; name="0033-Manual-typos-Internal-probes.patch", Size: 1091 bytes --]

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

Re: [PATCH 33/37] Manual typos: Internal probes

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/probes.texi: Fix typos in the manual.
> ---
>  manual/probes.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

[PATCH 08/37] Manual typos: Message Translation

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 236 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/message.texi: Fix typos in the manual.
---
 manual/message.texi |  159 +++++++++++++++++++++++++--------------------------
 1 file changed, 79 insertions(+), 80 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0008-Manual-typos-Message-Translation.patch --]
[-- Type: text/x-patch; name="0008-Manual-typos-Message-Translation.patch", Size: 31139 bytes --]

diff --git a/manual/message.texi b/manual/message.texi
index b03a14a..e48ed61 100644
--- a/manual/message.texi
+++ b/manual/message.texi
@@ -24,7 +24,7 @@ functions is defined in the X/Open standard but this is derived from
 industry decisions and therefore not necessarily based on reasonable
 decisions.
 
-As mentioned above the message catalog handling provides easy
+As mentioned above, the message catalog handling provides easy
 extendibility by using external data files which contain the message
 translations.  I.e., these files contain for each of the messages used
 in the program a translation for the appropriate language.  So the tasks
@@ -61,7 +61,7 @@ identifier is used.
 
 This means for the author of the program that s/he will have to make
 sure the meaning of the identifier in the program code and in the
-message catalogs are always the same.
+message catalogs is always the same.
 
 Before a message can be translated the catalog file must be located.
 The user of the program must be able to guide the responsible function
@@ -111,7 +111,7 @@ are defined/declared in the @file{nl_types.h} header file.
 @c   munmap ok
 @c   close_not_cancel_no_status ok
 @c  free @ascuheap @acsmem
-The @code{catopen} function tries to locate the message data file names
+The @code{catopen} function tries to locate the message data file named
 @var{cat_name} and loads it when found.  The return value is of an
 opaque type and can be used in calls to the other functions to refer to
 this loaded catalog.
@@ -179,7 +179,7 @@ the name of the currently selected locale.  See the explanation of the
 format above.
 
 @item %%
-Since @code{%} is used in a meta character there must be a way to
+Since @code{%} is used as a meta character there must be a way to
 express the @code{%} character in the result itself.  Using @code{%%}
 does this just like it works for @code{printf}.
 @end table
@@ -215,11 +215,11 @@ Otherwise the values of environment variables from the standard
 environment are examined (@pxref{Standard Environment}).  Which
 variables are examined is decided by the @var{flag} parameter of
 @code{catopen}.  If the value is @code{NL_CAT_LOCALE} (which is defined
-in @file{nl_types.h}) then the @code{catopen} function use the name of
+in @file{nl_types.h}) then the @code{catopen} function uses the name of
 the locale currently selected for the @code{LC_MESSAGES} category.
 
 If @var{flag} is zero the @code{LANG} environment variable is examined.
-This is a left-over from the early days where the concept of the locales
+This is a left-over from the early days when the concept of locales
 had not even reached the level of POSIX locales.
 
 The environment variable and the locale name should have a value of the
@@ -243,7 +243,7 @@ translation actually happened must look like this:
 @end smallexample
 
 @noindent
-When an error occurred the global variable @var{errno} is set to
+When an error occurs the global variable @var{errno} is set to
 
 @table @var
 @item EBADF
@@ -269,7 +269,7 @@ variables.
 
 @deftypefun {char *} catgets (nl_catd @var{catalog_desc}, int @var{set}, int @var{message}, const char *@var{string})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-The function @code{catgets} has to be used to access the massage catalog
+The function @code{catgets} has to be used to access the message catalog
 previously opened using the @code{catopen} function.  The
 @var{catalog_desc} parameter must be a value previously returned by
 @code{catopen}.
@@ -277,11 +277,11 @@ previously opened using the @code{catopen} function.  The
 The next two parameters, @var{set} and @var{message}, reflect the
 internal organization of the message catalog files.  This will be
 explained in detail below.  For now it is interesting to know that a
-catalog can consists of several set and the messages in each thread are
+catalog can consist of several sets and the messages in each thread are
 individually numbered using numbers.  Neither the set number nor the
 message number must be consecutive.  They can be arbitrarily chosen.
 But each message (unless equal to another one) must have its own unique
-pair of set and message number.
+pair of set and message numbers.
 
 Since it is not guaranteed that the message catalog for the language
 selected by the user exists the last parameter @var{string} helps to
@@ -303,7 +303,7 @@ functions if no supporting functionality is available.  Since each
 set/message number tuple must be unique the programmer must keep lists
 of the messages at the same time the code is written.  And the work
 between several people working on the same project must be coordinated.
-We will see some how these problems can be relaxed a bit (@pxref{Common
+We will see how some of these problems can be relaxed a bit (@pxref{Common
 Usage}).
 
 @deftypefun int catclose (nl_catd @var{catalog_desc})
@@ -315,7 +315,7 @@ Usage}).
 The @code{catclose} function can be used to free the resources
 associated with a message catalog which previously was opened by a call
 to @code{catopen}.  If the resources can be successfully freed the
-function returns @code{0}.  Otherwise it return @code{@minus{}1} and the
+function returns @code{0}.  Otherwise it returns @code{@minus{}1} and the
 global variable @var{errno} is set.  Errors can occur if the catalog
 descriptor @var{catalog_desc} is not valid in which case @var{errno} is
 set to @code{EBADF}.
@@ -325,7 +325,7 @@ set to @code{EBADF}.
 @node The message catalog files
 @subsection  Format of the message catalog files
 
-The only reasonable way the translate all the messages of a function and
+The only reasonable way to translate all the messages of a function and
 store the result in a message catalog file which can be read by the
 @code{catopen} function is to write all the message text to the
 translator and let her/him translate them all.  I.e., we must have a
@@ -386,9 +386,9 @@ messages will appear in the output.
 @item
 If a line contains after leading whitespaces the sequence
 @code{$quote}, the quoting character used for this input file is
-changed to the first non-whitespace character following the
+changed to the first non-whitespace character following
 @code{$quote}.  If no non-whitespace character is present before the
-line ends quoting is disable.
+line ends quoting is disabled.
 
 By default no quoting character is used.  In this mode strings are
 terminated with the first unescaped line break.  If there is a
@@ -411,7 +411,7 @@ If the start of the line is a number the message number is obvious.  It
 is an error if the same message number already appeared for this set.
 
 If the leading token was an identifier the message number gets
-automatically assigned.  The value is the current maximum messages
+automatically assigned.  The value is the current maximum message
 number for this set plus one.  It is an error if the identifier was
 already used for a message in this set.  It is OK to reuse the
 identifier for a message in another thread.  How to use the symbolic
@@ -451,17 +451,17 @@ Lines 1 and 9 are comments since they start with @code{$} followed by
 a whitespace.
 @item
 The quoting character is set to @code{"}.  Otherwise the quotes in the
-message definition would have to be left away and in this case the
-message with the identifier @code{two} would loose its leading whitespace.
+message definition would have to be omitted and in this case the
+message with the identifier @code{two} would lose its leading whitespace.
 @item
-Mixing numbered messages with message having symbolic names is no
+Mixing numbered messages with messages having symbolic names is no
 problem and the numbering happens automatically.
 @end itemize
 
 
 While this file format is pretty easy it is not the best possible for
 use in a running program.  The @code{catopen} function would have to
-parser the file and handle syntactic errors gracefully.  This is not so
+parse the file and handle syntactic errors gracefully.  This is not so
 easy and the whole process is pretty slow.  Therefore the @code{catgets}
 functions expect the data in another more compact and ready-to-use file
 format.  There is a special program @code{gencat} which is explained in
@@ -492,18 +492,18 @@ implemented which help to work in a more reasonable way with the
 The @code{gencat} program can be invoked in two ways:
 
 @example
-`gencat [@var{Option}]@dots{} [@var{Output-File} [@var{Input-File}]@dots{}]`
+`gencat [@var{Option} @dots{}] [@var{Output-File} [@var{Input-File} @dots{}]]`
 @end example
 
 This is the interface defined in the X/Open standard.  If no
-@var{Input-File} parameter is given input will be read from standard
-input.  Multiple input files will be read as if they are concatenated.
+@var{Input-File} parameter is given, input will be read from standard
+input.  Multiple input files will be read as if they were concatenated.
 If @var{Output-File} is also missing, the output will be written to
 standard output.  To provide the interface one is used to from other
 programs a second interface is provided.
 
 @smallexample
-`gencat [@var{Option}]@dots{} -o @var{Output-File} [@var{Input-File}]@dots{}`
+`gencat [@var{Option} @dots{}] -o @var{Output-File} [@var{Input-File} @dots{}]`
 @end smallexample
 
 The option @samp{-o} is used to specify the output file and all file
@@ -516,17 +516,17 @@ standard output.  Using @file{-} as a file name is allowed in X/Open
 while using the device names is a GNU extension.
 
 The @code{gencat} program works by concatenating all input files and
-then @strong{merge} the resulting collection of message sets with a
+then @strong{merging} the resulting collection of message sets with a
 possibly existing output file.  This is done by removing all messages
 with set/message number tuples matching any of the generated messages
 from the output file and then adding all the new messages.  To
 regenerate a catalog file while ignoring the old contents therefore
-requires to remove the output file if it exists.  If the output is
+requires removing the output file if it exists.  If the output is
 written to standard output no merging takes place.
 
 @noindent
 The following table shows the options understood by the @code{gencat}
-program.  The X/Open standard does not specify any option for the
+program.  The X/Open standard does not specify any options for the
 program so all of these are GNU extensions.
 
 @table @samp
@@ -537,8 +537,8 @@ Print the version information and exit.
 @itemx --help
 Print a usage message listing all available options, then exit successfully.
 @item --new
-Do never merge the new messages from the input files with the old content
-of the output files.  The old content of the output file is discarded.
+Do not merge the new messages from the input files with the old content
+of the output file.  The old content of the output file is discarded.
 @item -H
 @itemx --header=name
 This option is used to emit the symbolic names given to sets and
@@ -608,7 +608,7 @@ The problems mentioned in the last section derive from the fact that:
 the numbers are allocated once and due to the possibly frequent use of
 them it is difficult to change a number later.
 @item
-the numbers do not allow to guess anything about the string and
+the numbers do not allow guessing anything about the string and
 therefore collisions can easily happen.
 @end enumerate
 
@@ -622,7 +622,7 @@ This is necessary since the symbolic names must be mapped to numbers
 before the program sources can be compiled.  In the last section it was
 described how to generate a header containing the mapping of the names.
 E.g., for the example message file given in the last section we could
-call the @code{gencat} program as follow (assume @file{ex.msg} contains
+call the @code{gencat} program as follows (assume @file{ex.msg} contains
 the sources).
 
 @smallexample
@@ -646,8 +646,7 @@ allow to predict the content of the header file (it is deterministic)
 but this is not necessary.  The @code{gencat} program can take care for
 everything.  All the programmer has to do is to put the generated header
 file in the dependency list of the source files of her/his project and
-to add a rules to regenerate the header of any of the input files
-change.
+add a rule to regenerate the header if any of the input files change.
 
 One word about the symbol mangling.  Every symbol consists of two parts:
 the name of the message set plus the name of the message or the special
@@ -816,7 +815,7 @@ If the string which has to be translated is the only argument this of
 course means the string itself is the key.  I.e., the translation will
 be selected based on the original string.  The message catalogs must
 therefore contain the original strings plus one translation for any such
-string.  The task of the @code{gettext} function is it to compare the
+string.  The task of the @code{gettext} function is to compare the
 argument string with the available strings in the catalog and return the
 appropriate translation.  Of course this process is optimized so that
 this process is not more expensive than an access using an atomic key
@@ -864,11 +863,11 @@ processing the @code{%m} format element and if the @code{gettext}
 function would change this value (it is called before @code{printf} is
 called) we would get a wrong message.
 
-So there is no easy way to detect a missing message catalog beside
+So there is no easy way to detect a missing message catalog besides
 comparing the argument string with the result.  But it is normally the
 task of the user to react on missing catalogs.  The program cannot guess
 when a message catalog is really necessary since for a user who speaks
-the language the program was developed in does not need any translation.
+the language the program was developed in, the message does not need any translation.
 @end deftypefun
 
 The remaining two functions to access the message catalog add some
@@ -885,7 +884,7 @@ information.
 @deftypefun {char *} dgettext (const char *@var{domainname}, const char *@var{msgid})
 @safety{@prelim{}@mtsafe{@mtsenv{}}@asunsafe{@asucorrupt{} @ascuheap{} @asulock{} @ascudlopen{}}@acunsafe{@acucorrupt{} @aculock{} @acsfd{} @acsmem{}}}
 @c Wrapper for dcgettext.
-The @code{dgettext} functions acts just like the @code{gettext}
+The @code{dgettext} function acts just like the @code{gettext}
 function.  It only takes an additional first argument @var{domainname}
 which guides the selection of the message catalogs which are searched
 for the translation.  If the @var{domainname} parameter is the null
@@ -1021,12 +1020,12 @@ has to use the available selectors for the categories available in
 @code{LC_COLLATE}, @code{LC_MESSAGES}, @code{LC_MONETARY},
 @code{LC_NUMERIC}, and @code{LC_TIME}.  Please note that @code{LC_ALL}
 must not be used and even though the names might suggest this, there is
-no relation to the environments variables of this name.
+no relation to the environment variable of this name.
 
 The @code{dcgettext} function is only implemented for compatibility with
 other systems which have @code{gettext} functions.  There is not really
 any situation where it is necessary (or useful) to use a different value
-but @code{LC_MESSAGES} in for the @var{category} parameter.  We are
+than @code{LC_MESSAGES} for the @var{category} parameter.  We are
 dealing with messages here and any other choice can only be irritating.
 
 As for @code{gettext} the return value type is @code{char *} which is an
@@ -1034,7 +1033,7 @@ anachronism.  The returned string must never be modified.
 @end deftypefun
 
 When using the three functions above in a program it is a frequent case
-that the @var{msgid} argument is a constant string.  So it is worth to
+that the @var{msgid} argument is a constant string.  So it is worthwhile to
 optimize this case.  Thinking shortly about this one will realize that
 as long as no new message catalog is loaded the translation of a message
 will not change.  This optimization is actually implemented by the
@@ -1058,10 +1057,10 @@ performed by the @code{catgets} functions:
 @enumerate
 @item
 Locate the set of message catalogs.  There are a number of files for
-different languages and which all belong to the package.  Usually they
+different languages which all belong to the package.  Usually they
 are all stored in the filesystem below a certain directory.
 
-There can be arbitrary many packages installed and they can follow
+There can be arbitrarily many packages installed and they can follow
 different guidelines for the placement of their files.
 
 @item
@@ -1079,7 +1078,7 @@ able to do.  But there are some problems unresolved:
 @item
 The language to be used can be specified in several different ways.
 There is no generally accepted standard for this and the user always
-expects the program understand what s/he means.  E.g., to select the
+expects the program to understand what s/he means.  E.g., to select the
 German translation one could write @code{de}, @code{german}, or
 @code{deutsch} and the program should always react the same.
 
@@ -1108,8 +1107,8 @@ be based on this.
 
 As the functions described in the last sections already mention separate
 sets of messages can be selected by a @dfn{domain name}.  This is a
-simple string which should be unique for each program part with uses a
-separate domain.  It is possible to use in one program arbitrary many
+simple string which should be unique for each program part that uses a
+separate domain.  It is possible to use in one program arbitrarily many
 domains at the same time.  E.g., @theglibc{} itself uses a domain
 named @code{libc} while the program using the C Library could use a
 domain named @code{foo}.  The important point is that at any time
@@ -1171,7 +1170,7 @@ different languages.  To be correct, this is the directory where the
 hierarchy of directories is expected.  Details are explained below.
 
 For the programmer it is important to note that the translations which
-come with the program have be placed in a directory hierarchy starting
+come with the program have to be placed in a directory hierarchy starting
 at, say, @file{/foo/bar}.  Then the program should make a
 @code{bindtextdomain} call to bind the domain for the current program to
 this directory.  So it is made sure the catalogs are found.  A correctly
@@ -1206,7 +1205,7 @@ variable @var{errno} is set accordingly.
 
 The functions of the @code{gettext} family described so far (and all the
 @code{catgets} functions as well) have one problem in the real world
-which have been neglected completely in all existing approaches.  What
+which has been neglected completely in all existing approaches.  What
 is meant here is the handling of plural forms.
 
 Looking through Unix source code before the time anybody thought about
@@ -1233,7 +1232,7 @@ tries to solve the problem correctly looked like this:
 But this does not solve the problem.  It helps languages where the
 plural form of a noun is not simply constructed by adding an `s' but
 that is all.  Once again people fell into the trap of believing the
-rules their language is using are universal.  But the handling of plural
+rules their language uses are universal.  But the handling of plural
 forms differs widely between the language families.  There are two
 things we can differ between (and even inside language families);
 
@@ -1266,15 +1265,15 @@ can select using rules specified by the translator the right plural
 form.  The two string arguments then will be used to provide a return
 value in case no message catalog is found (similar to the normal
 @code{gettext} behavior).  In this case the rules for Germanic language
-is used and it is assumed that the first string argument is the singular
+are used and it is assumed that the first string argument is the singular
 form, the second the plural form.
 
 This has the consequence that programs without language catalogs can
 display the correct strings only if the program itself is written using
 a Germanic language.  This is a limitation but since @theglibc{}
-(as well as the GNU @code{gettext} package) are written as part of the
-GNU package and the coding standards for the GNU project require program
-being written in English, this solution nevertheless fulfills its
+(as well as the GNU @code{gettext} package) is written as part of the
+GNU package and the coding standards for the GNU project require programs
+to be written in English, this solution nevertheless fulfills its
 purpose.
 
 @comment libintl.h
@@ -1291,7 +1290,7 @@ The parameter @var{n} is used to determine the plural form.  If no
 message catalog is found @var{msgid1} is returned if @code{n == 1},
 otherwise @code{msgid2}.
 
-An example for the us of this function is:
+An example for the use of this function is:
 
 @smallexample
   printf (ngettext ("%d file removed", "%d files removed", n), n);
@@ -1309,7 +1308,7 @@ Please note that the numeric value @var{n} has to be passed to the
 @c Wrapper for dcngettext.
 The @code{dngettext} is similar to the @code{dgettext} function in the
 way the message catalog is selected.  The difference is that it takes
-two extra parameter to provide the correct plural form.  These two
+two extra parameters to provide the correct plural form.  These two
 parameters are handled in the same way @code{ngettext} handles them.
 @end deftypefun
 
@@ -1320,7 +1319,7 @@ parameters are handled in the same way @code{ngettext} handles them.
 @c Wrapper for dcigettext.
 The @code{dcngettext} is similar to the @code{dcgettext} function in the
 way the message catalog is selected.  The difference is that it takes
-two extra parameter to provide the correct plural form.  These two
+two extra parameters to provide the correct plural form.  These two
 parameters are handled in the same way @code{ngettext} handles them.
 @end deftypefun
 
@@ -1342,7 +1341,7 @@ details are explained in the GNU @code{gettext} manual.  Here only a
 bit of information is provided.
 
 The information about the plural form selection has to be stored in the
-header entry (the one with the empty (@code{msgid} string).  It looks
+header entry (the one with the empty @code{msgid} string).  It looks
 like this:
 
 @smallexample
@@ -1351,8 +1350,8 @@ Plural-Forms: nplurals=2; plural=n == 1 ? 0 : 1;
 
 The @code{nplurals} value must be a decimal number which specifies how
 many different plural forms exist for this language.  The string
-following @code{plural} is an expression which is using the C language
-syntax.  Exceptions are that no negative number are allowed, numbers
+following @code{plural} is an expression using the C language
+syntax.  Exceptions are that no negative numbers are allowed, numbers
 must be decimal, and the only variable allowed is @code{n}.  This
 expression will be evaluated whenever one of the functions
 @code{ngettext}, @code{dngettext}, or @code{dcngettext} is called.  The
@@ -1392,7 +1391,7 @@ Turkish
 
 @item Two forms, singular used for one only
 This is the form used in most existing programs since it is what English
-is using.  A header entry would look like this:
+uses.  A header entry would look like this:
 
 @smallexample
 Plural-Forms: nplurals=2; plural=n != 1;
@@ -1551,7 +1550,7 @@ Slovenian
 @node Charset conversion in gettext
 @subsubsection How to specify the output character set @code{gettext} uses
 
-@code{gettext} not only looks up a translation in a message catalog.  It
+@code{gettext} not only looks up a translation in a message catalog, it
 also converts the translation on the fly to the desired output character
 set.  This is useful if the user is working in a different character set
 than the translator who created the message catalog, because it avoids
@@ -1642,10 +1641,10 @@ are in the dilemma described above.
 One solution to this problem is to artificially enlengthen the strings
 to make them unambiguous.  But what would the program do if no
 translation is available?  The enlengthened string is not what should be
-printed.  So we should use a little bit modified version of the functions.
+printed.  So we should use a slightly modified version of the functions.
 
 To enlengthen the strings a uniform method should be used.  E.g., in the
-example above the strings could be chosen as
+example above, the strings could be chosen as
 
 @smallexample
 Menu|File
@@ -1728,7 +1727,7 @@ why the @file{iso646.h} file exists in @w{ISO C} programming environments).
 @end itemize
 
 There is only one more comment to make left.  The wrapper function above
-require that the translations strings are not enlengthened themselves.
+requires that the translation strings are not enlengthened themselves.
 This is only logical.  There is no need to disambiguate the strings
 (since they are never used as keys for a search) and one also saves
 quite some memory and disk space by doing this.
@@ -1745,7 +1744,7 @@ them.
 The POSIX locale model uses the environment variables @code{LC_COLLATE},
 @code{LC_CTYPE}, @code{LC_MESSAGES}, @code{LC_MONETARY}, @code{LC_NUMERIC},
 and @code{LC_TIME} to select the locale which is to be used.  This way
-the user can influence lots of functions.  As we mentioned above the
+the user can influence lots of functions.  As we mentioned above, the
 @code{gettext} functions also take advantage of this.
 
 To understand how this happens it is necessary to take a look at the
@@ -1796,7 +1795,7 @@ following variables in this order are examined:
 
 This looks very familiar.  With the exception of the @code{LANGUAGE}
 environment variable this is exactly the lookup order the
-@code{setlocale} function uses.  But why introducing the @code{LANGUAGE}
+@code{setlocale} function uses.  But why introduce the @code{LANGUAGE}
 variable?
 
 The reason is that the syntax of the values these variables can have is
@@ -1812,7 +1811,7 @@ exactly one specification of a locale the @code{LANGUAGE} variable's
 value can consist of a colon separated list of locale names.  The
 attentive reader will realize that this is the way we manage to
 implement one of our additional demands above: we want to be able to
-specify an ordered list of language.
+specify an ordered list of languages.
 
 Back to the constructed filename we have only one component missing.
 The @var{domain_name} part is the name which was either registered using
@@ -1823,7 +1822,7 @@ closely related to the program/package name.  E.g., for @theglibc{}
 the domain name is @code{libc}.
 
 @noindent
-A limit piece of example code should show how the programmer is supposed
+A limited piece of example code should show how the program is supposed
 to work:
 
 @smallexample
@@ -1846,7 +1845,7 @@ The @code{textdomain} call changes the default domain to
 the message catalogs for the domain @code{test-package} can be found
 below the directory @file{/usr/local/share/locale}.
 
-If now the user set in her/his environment the variable @code{LANGUAGE}
+If the user sets in her/his environment the variable @code{LANGUAGE}
 to @code{de} the @code{gettext} function will try to use the
 translations from the file
 
@@ -1858,7 +1857,7 @@ From the above descriptions it should be clear which component of this
 filename is determined by which source.
 
-In the above example we assumed that the @code{LANGUAGE} environment
-variable to @code{de}.  This might be an appropriate selection but what
+In the above example we assumed the @code{LANGUAGE} environment
+variable to be @code{de}.  This might be an appropriate selection but what
 happens if the user wants to use @code{LC_ALL} because of the wider
 usability and here the required value is @code{de_DE.ISO-8859-1}?  We
 already mentioned above that a situation like this is not infrequent.
@@ -1876,7 +1875,7 @@ specification:
 
 @code{language[_territory[.codeset]][@@modifier]}
 
-Less specific locale names will be stripped of in the order of the
+Less specific locale names will be stripped in the order of the
 following list:
 
 @enumerate
@@ -1893,8 +1892,8 @@ following list:
 The @code{language} field will never be dropped for obvious reasons.
 
 The only new thing is the @code{normalized codeset} entry.  This is
-another goodie which is introduced to help reducing the chaos which
-derives from the inability of the people to standardize the names of
+another goodie which is introduced to help reduce the chaos which
+derives from the inability of people to standardize the names of
 character sets.  Instead of @w{ISO-8859-1} one can often see @w{8859-1},
 @w{88591}, @w{iso8859-1}, or @w{iso_8859-1}.  The @code{normalized
 codeset} value is generated from the user-provided character set name by
@@ -1902,7 +1901,7 @@ applying the following rules:
 
 @enumerate
 @item
-Remove all characters beside numbers and letters.
+Remove all characters besides numbers and letters.
 @item
 Fold letters to lowercase.
 @item
@@ -1910,8 +1909,8 @@ If the same only contains digits prepend the string @code{"iso"}.
 @end enumerate
 
 @noindent
-So all of the above name will be normalized to @code{iso88591}.  This
-allows the program user much more freely choosing the locale name.
+So all of the above names will be normalized to @code{iso88591}.  This
+allows the program user much more freedom in choosing the locale name.
 
 Even this extended functionality still does not help to solve the
 problem that completely different names can be used to denote the same
@@ -1924,7 +1923,7 @@ whatever prefix you used for configuring the C library) contains a
 mapping of alternative names to more regular names.  The system manager
 is free to add new entries to fill her/his own needs.  The selected
 locale from the environment is compared with the entries in the first
-column of this file ignoring the case.  If they match the value of the
+column of this file ignoring the case.  If they match, the value of the
 second column is used instead for the further handling.
 
 In the description of the format of the environment variables we already
@@ -1932,7 +1931,7 @@ mentioned the character set as a factor in the selection of the message
 catalog.  In fact, only catalogs which contain text written using the
 character set of the system/program can be used (directly; there will
 come a solution for this some day).  This means for the user that s/he
-will always have to take care for this.  If in the collection of the
+will always have to take care of this.  If in the collection of the
 message catalogs there are files for the same language but coded using
 different character sets the user has to be careful.
 
@@ -1965,6 +1964,6 @@ Other programs help to manage the development cycle when new messages appear
 in the source files or when a new translation of the messages appears.
 Here it should only be noted that using all the tools in GNU gettext it
 is possible to @emph{completely} automate the handling of message
-catalogs.  Beside marking the translatable strings in the source code and
+catalogs.  Besides marking the translatable strings in the source code and
 generating the translations the developers do not have anything to do
 themselves.

Re: [PATCH 08/37] Manual typos: Message Translation

[Chris Leonard]

Not sure about several uses of besides vs beside, but otherwise +1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/message.texi: Fix typos in the manual.
> ---
>  manual/message.texi |  159 +++++++++++++++++++++++++--------------------------
>  1 file changed, 79 insertions(+), 80 deletions(-)
>

Re: [PATCH 08/37] Manual typos: Message Translation

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 81 bytes --]

merged!

besides, the beside/besides thing sounds fine either way to me :p
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 01/37] Manual typos: Introduction

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 179 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/intro.texi: Fix typos in the manual.
---
 manual/intro.texi |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0001-Manual-typos-Introduction.patch --]
[-- Type: text/x-patch; name="0001-Manual-typos-Introduction.patch", Size: 628 bytes --]

diff --git a/manual/intro.texi b/manual/intro.texi
index d4045f2..cc9c99f 100644
--- a/manual/intro.texi
+++ b/manual/intro.texi
@@ -884,7 +884,7 @@ context.
 
 Some safety annotations may be conditional, in that they only apply if a
 boolean expression involving arguments, global variables or even the
-underlying kernel evaluates evaluates to true.  Such conditions as
+underlying kernel evaluates to true.  Such conditions as
 @code{/hurd} or @code{/!linux!bsd} indicate the preceding marker only
 applies when the underlying kernel is the HURD, or when it is neither
 Linux nor a BSD kernel, respectively.  @code{/!ps} and

Re: [PATCH 01/37] Manual typos: Introduction

[Chris Leonard]

+1+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/intro.texi: Fix typos in the manual.
> ---
>  manual/intro.texi |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Re: [PATCH 01/37] Manual typos: Introduction

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 22 bytes --]

merged, thanks!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 29/37] Manual typos: System Configuration Parameters

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 187 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/conf.texi: Fix typos in the manual.
---
 manual/conf.texi |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0029-Manual-typos-System-Configuration-Parameters.patch --]
[-- Type: text/x-patch; name="0029-Manual-typos-System-Configuration-Parameters.patch", Size: 2047 bytes --]

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
 

Re: [PATCH 29/37] Manual typos: System Configuration Parameters

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/conf.texi: Fix typos in the manual.
> ---
>  manual/conf.texi |   10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>

[PATCH 22/37] Manual typos: Signal Handling

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 187 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/signal.texi: Fix typos in the manual.
---
 manual/signal.texi |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0022-Manual-typos-Signal-Handling.patch --]
[-- Type: text/x-patch; name="0022-Manual-typos-Signal-Handling.patch", Size: 1847 bytes --]

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.

Re: [PATCH 22/37] Manual typos: Signal Handling

[Chris Leonard]

+1

cjl


On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/signal.texi: Fix typos in the manual.
> ---
>  manual/signal.texi |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>

[PATCH 03/37] Manual typos: Virtual Memory Allocation and Paging

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 207 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/memory.texi: Fix typos in the manual.
---
 manual/memory.texi |   24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0003-Manual-typos-Virtual-Memory-Allocation-and-Paging.patch --]
[-- Type: text/x-patch; name="0003-Manual-typos-Virtual-Memory-Allocation-and-Paging.patch", Size: 4891 bytes --]

diff --git a/manual/memory.texi b/manual/memory.texi
index a3ecc0d..59b04b9 100644
--- a/manual/memory.texi
+++ b/manual/memory.texi
@@ -158,7 +158,7 @@ grows, but doesn't shrink when the stack shrinks.
 
 This section covers how ordinary programs manage storage for their data,
 including the famous @code{malloc} function and some fancier facilities
-special @theglibc{} and GNU Compiler.
+special to @theglibc{} and GNU Compiler.
 
 @menu
 * Memory Allocation and C::     How to get different kinds of allocation in C.
@@ -997,7 +997,7 @@ The @code{memalign} function returns a null pointer on error and sets
 There was insufficient memory available to satisfy the request.
 
 @item EINVAL
-@var{alignment} is not a power of two.
+@var{boundary} is not a power of two.
 
 @end table
 
@@ -1066,7 +1066,7 @@ systems that do not support @w{ISO C11}.
 @c  _int_memalign dup @acsfd @acsmem
 @c  mutex_unlock dup @aculock
 Using @code{valloc} is like using @code{memalign} and passing the page size
-as the value of the second argument.  It is implemented like this:
+as the value of the first argument.  It is implemented like this:
 
 @smallexample
 void *
@@ -1628,7 +1628,7 @@ Return information about the current dynamic memory usage.
 
 A complicated task when programming with languages which do not use
 garbage collected dynamic memory allocation is to find memory leaks.
-Long running programs must assure that dynamically allocated objects are
+Long running programs must ensure that dynamically allocated objects are
 freed at the end of their lifetime.  If this does not happen the system
 runs out of memory, sooner or later.
 
@@ -1729,7 +1729,7 @@ main (int argc, char *argv[])
 @}
 @end example
 
-This is all what is needed if you want to trace the calls during the
+This is all that is needed if you want to trace the calls during the
 whole runtime of the program.  Alternatively you can stop the tracing at
 any time with a call to @code{muntrace}.  It is even possible to restart
 the tracing again with a new call to @code{mtrace}.  But this can cause
@@ -1738,8 +1738,8 @@ not called.  Please note that not only the application uses the traced
 functions, also libraries (including the C library itself) use these
 functions.
 
-This last point is also why it is no good idea to call @code{muntrace}
-before the program terminated.  The libraries are informed about the
+This last point is also why it is not a good idea to call @code{muntrace}
+before the program terminates.  The libraries are informed about the
 termination of the program only after the program returns from
 @code{main} or calls @code{exit} and so cannot free the memory they use
 before this time.
@@ -2167,7 +2167,7 @@ in the same obstack.
 If @var{object} is a null pointer, everything allocated in the obstack
 is freed.  Otherwise, @var{object} must be the address of an object
 allocated in the obstack.  Then @var{object} is freed, along with
-everything allocated in @var{obstack} since @var{object}.
+everything allocated in @var{obstack-ptr} since @var{object}.
 @end deftypefun
 
 Note that if @var{object} is a null pointer, the result is an
@@ -2412,7 +2412,7 @@ in the current chunk.  It is declared as follows:
 @safety{@prelim{}@mtsafe{@mtsrace{:obstack-ptr}}@assafe{}@acsafe{}}
 This returns the number of bytes that can be added safely to the current
 growing object (or to an object about to be started) in obstack
-@var{obstack} using the fast growth functions.
+@var{obstack-ptr} using the fast growth functions.
 @end deftypefun
 
 While you know there is room, you can use these fast growth functions
@@ -2822,7 +2822,7 @@ open-coded by the GNU C compiler.)
 
 @item
 Since @code{alloca} does not have separate pools for different sizes of
-block, space used for any size block can be reused for any other size.
+blocks, space used for any size block can be reused for any other size.
 @code{alloca} does not cause memory fragmentation.
 
 @item
@@ -2941,7 +2941,7 @@ The address of the end of a segment is defined to be the address of the
 last byte in the segment plus 1.
 
 The function has no effect if @var{addr} is lower than the low end of
-the data segment.  (This is considered success, by the way).
+the data segment.  (This is considered success, by the way.)
 
 The function fails if it would cause the data segment to overlap another
 segment or exceed the process' data storage limit (@pxref{Limits on
@@ -3263,7 +3263,7 @@ with @code{munlockall} and @code{munlock}.
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 
 @code{munlockall} unlocks every page in the calling process' virtual
-address space and turn off @code{MCL_FUTURE} future locking mode.
+address space and turns off @code{MCL_FUTURE} future locking mode.
 
 The return value is zero if the function succeeds.  Otherwise, it is
 @code{-1} and @code{errno} is set accordingly.  The only way this

Re: [PATCH 03/37] Manual typos: Virtual Memory Allocation and Paging

[Chris Leonard]

Did not personally confirm the word-substitutions.  Would like to see
a subject matter expert sign off on those.  Typo fixes look good.

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/memory.texi: Fix typos in the manual.
> ---
>  manual/memory.texi |   24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
>

Re: [PATCH 03/37] Manual typos: Virtual Memory Allocation and Paging

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]

looks good -- i double checked the wording & various fields

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 21/37] Manual typos: Non-Local Exits

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 189 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/setjmp.texi: Fix typos in the manual.
---
 manual/setjmp.texi |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0021-Manual-typos-Non-Local-Exits.patch --]
[-- Type: text/x-patch; name="0021-Manual-typos-Non-Local-Exits.patch", Size: 2012 bytes --]

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

Re: [PATCH 21/37] Manual typos: Non-Local Exits

[Chris Leonard]

+1

cjl


On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/setjmp.texi: Fix typos in the manual.
> ---
>  manual/setjmp.texi |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>

[PATCH 02/37] Manual typos: Error Reporting

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 203 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/errno.texi: Fix typos in the manual.
---
 manual/errno.texi |   22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0002-Manual-typos-Error-Reporting.patch --]
[-- Type: text/x-patch; name="0002-Manual-typos-Error-Reporting.patch", Size: 4530 bytes --]

diff --git a/manual/errno.texi b/manual/errno.texi
index 1068be3..d5429a0 100644
--- a/manual/errno.texi
+++ b/manual/errno.texi
@@ -1322,13 +1322,13 @@ string in the user supplied buffer starting at @var{buf} with the
 length of @var{n} bytes.
 
 At most @var{n} characters are written (including the NUL byte) so it is
-up to the user to select the buffer large enough.
+up to the user to select a buffer large enough.
 
 This function should always be used in multi-threaded programs since
 there is no way to guarantee the string returned by @code{strerror}
 really belongs to the last call of the current thread.
 
-This function @code{strerror_r} is a GNU extension and it is declared in
+The function @code{strerror_r} is a GNU extension and it is declared in
 @file{string.h}.
 @end deftypefun
 
@@ -1471,7 +1471,7 @@ the problem mentioned above that the error reporting function must be
 called immediately after the function causing the error since otherwise
 @code{errno} might have a different value.
 
-The @code{error} prints first the program name.  If the application
+@code{error} prints first the program name.  If the application
 defined a global variable @code{error_print_progname} and points it to a
 function this function will be called to print the program name.
 Otherwise the string from the global variable @code{program_name} is
@@ -1488,7 +1488,7 @@ afterwards.
 The function will return unless the @var{status} parameter has a
 non-zero value.  In this case the function will call @code{exit} with
 the @var{status} value for its parameter and therefore never return.  If
-@code{error} returns the global variable @code{error_message_count} is
+@code{error} returns, the global variable @code{error_message_count} is
 incremented by one to keep track of the number of errors reported.
 @end deftypefun
 
@@ -1506,13 +1506,13 @@ incremented by one to keep track of the number of errors reported.
 @c like error.
 
 The @code{error_at_line} function is very similar to the @code{error}
-function.  The only difference are the additional parameters @var{fname}
+function.  The only differences are the additional parameters @var{fname}
 and @var{lineno}.  The handling of the other parameters is identical to
 that of @code{error} except that between the program name and the string
 generated by the format string additional text is inserted.
 
 Directly following the program name a colon, followed by the file name
-pointer to by @var{fname}, another colon, and a value of @var{lineno} is
+pointed to by @var{fname}, another colon, and the value of @var{lineno} is
 printed.
 
 This additional output of course is meant to be used to locate an error
@@ -1523,13 +1523,13 @@ value @code{error_at_line} will avoid printing consecutive messages for
 the same file and line.  Repetition which are not directly following
 each other are not caught.
 
-Just like @code{error} this function only returned if @var{status} is
+Just like @code{error} this function only returns if @var{status} is
 zero.  Otherwise @code{exit} is called with the non-zero value.  If
-@code{error} returns the global variable @code{error_message_count} is
+@code{error} returns, the global variable @code{error_message_count} is
 incremented by one to keep track of the number of errors reported.
 @end deftypefun
 
-As mentioned above the @code{error} and @code{error_at_line} functions
+As mentioned above, the @code{error} and @code{error_at_line} functions
 can be customized by defining a variable named
 @code{error_print_progname}.
 
@@ -1541,7 +1541,7 @@ value the function pointed to is called by @code{error} or
 @code{error_at_line}.  It is expected to print the program name or do
 something similarly useful.
 
-The function is expected to be print to the @code{stderr} stream and
+The function is expected to print to the @code{stderr} stream and
 must be able to handle whatever orientation the stream has.
 
 The variable is global and shared by all threads.
@@ -1562,7 +1562,7 @@ The @code{error_one_per_line} variable influences only
 @code{error_at_line}.  Normally the @code{error_at_line} function
 creates output for every invocation.  If @code{error_one_per_line} is
 set to a non-zero value @code{error_at_line} keeps track of the last
-file name and line number for which an error was reported and avoid
+file name and line number for which an error was reported and avoids
 directly following messages for the same file and line.  This variable
 is global and shared by all threads.
 @end deftypevar

Re: [PATCH 02/37] Manual typos: Error Reporting

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/errno.texi: Fix typos in the manual.
> ---
>  manual/errno.texi |   22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
>

Re: [PATCH 02/37] Manual typos: Error Reporting

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 22 bytes --]

merged, thanks!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 30/37] Manual typos: DES Encryption and Password Handling

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 187 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/crypt.texi: Fix typos in the manual.
---
 manual/crypt.texi |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0030-Manual-typos-DES-Encryption-and-Password-Handling.patch --]
[-- Type: text/x-patch; name="0030-Manual-typos-DES-Encryption-and-Password-Handling.patch", Size: 2047 bytes --]

diff --git a/manual/crypt.texi b/manual/crypt.texi
index fd007cf..d5ea50a 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}.

Re: [PATCH 30/37] Manual typos: DES Encryption and Password Handling

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/crypt.texi: Fix typos in the manual.
> ---
>  manual/crypt.texi |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>

[PATCH 31/37] Manual typos: Debugging support

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/debug.texi: Fix typos in the manual.
---
 manual/debug.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0031-Manual-typos-Debugging-support.patch --]
[-- Type: text/x-patch; name="0031-Manual-typos-Debugging-support.patch", Size: 956 bytes --]

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

Re: [PATCH 31/37] Manual typos: Debugging support

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/debug.texi: Fix typos in the manual.
> ---
>  manual/debug.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

[PATCH 26/37] Manual typos: System Databases and Name Service Switch

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 221 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/nss.texi: Fix typos in the manual.
---
 manual/nss.texi |   44 ++++++++++++++++++++++----------------------
 1 file changed, 22 insertions(+), 22 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0026-Manual-typos-System-Databases-and-Name-Service-Switc.patch --]
[-- Type: text/x-patch; name="0026-Manual-typos-System-Databases-and-Name-Service-Switc.patch", Size: 8143 bytes --]

diff --git a/manual/nss.texi b/manual/nss.texi
index 66dccef..fd479d4 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
@@ -279,8 +279,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
@@ -316,7 +316,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}
@@ -349,7 +349,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.
 
@@ -379,7 +379,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
@@ -430,7 +430,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
@@ -461,7 +461,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.
 
 The above function has something special which is missing for almost all
 the other module functions.  There is an argument @var{h_errnop}.  This
@@ -609,7 +609,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
@@ -628,12 +628,12 @@ guaranteed that the same buffer will be passed for the next call of this
 function.  Therefore one must not misuse this buffer to save some state
 information from one call to another.
 
-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.
 
-As explained above this function could also have an additional last
+As explained above, this function could also have an additional last
 argument.  This depends on the database used; it happens only for
 @code{host} and @code{networks}.
 
@@ -642,7 +642,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)
@@ -653,17 +653,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

Re: [PATCH 26/37] Manual typos: System Databases and Name Service Switch

[Chris Leonard]

+1

cjl



On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/nss.texi: Fix typos in the manual.
> ---
>  manual/nss.texi |   44 ++++++++++++++++++++++----------------------
>  1 file changed, 22 insertions(+), 22 deletions(-)
>

[PATCH 37/37] Manual typos: Contributors to

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 189 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/contrib.texi: Fix typos in the manual.
---
 manual/contrib.texi |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0037-Manual-typos-Contributors-to.patch --]
[-- Type: text/x-patch; name="0037-Manual-typos-Contributors-to.patch", Size: 1099 bytes --]

diff --git a/manual/contrib.texi b/manual/contrib.texi
index 930d614..19b015f 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

Re: [PATCH 37/37] Manual typos: Contributors to

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/contrib.texi: Fix typos in the manual.
> ---
>  manual/contrib.texi |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>

[PATCH 25/37] Manual typos: Job Control

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 175 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/job.texi: Fix typos in the manual.
---
 manual/job.texi |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0025-Manual-typos-Job-Control.patch --]
[-- Type: text/x-patch; name="0025-Manual-typos-Job-Control.patch", Size: 500 bytes --]

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

Re: [PATCH 25/37] Manual typos: Job Control

[Chris Leonard]

Not sure I really understand the change here. Is it a CR and whitespace?

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/job.texi: Fix typos in the manual.
> ---
>  manual/job.texi |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

Re: [PATCH 25/37] Manual typos: Job Control

[Rical Jasan]

On 05/30/2016 09:23 AM, Chris Leonard wrote:
> Not sure I really understand the change here. Is it a CR and whitespace?

It ends the sentence with a period instead of a comma.

Thanks for all the review!

Rical

Re: [PATCH 25/37] Manual typos: Job Control

[Chris Leonard]

OK, some things are just harder to see clearly than others.

+1

cjl

On Tue, May 31, 2016 at 2:18 AM, Rical Jasan <ricaljasan@pacific.net> wrote:
> On 05/30/2016 09:23 AM, Chris Leonard wrote:
>> Not sure I really understand the change here. Is it a CR and whitespace?
>
> It ends the sentence with a period instead of a comma.
>
> Thanks for all the review!
>
> Rical

[PATCH 28/37] Manual typos: System Management

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 236 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/sysinfo.texi: Fix typos in the manual.
---
 manual/sysinfo.texi |   52 +++++++++++++++++++++++++--------------------------
 1 file changed, 26 insertions(+), 26 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0028-Manual-typos-System-Management.patch --]
[-- Type: text/x-patch; name="0028-Manual-typos-System-Management.patch", Size: 10949 bytes --]

diff --git a/manual/sysinfo.texi b/manual/sysinfo.texi
index 1fbfb95..e15eddf 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
@@ -701,8 +701,8 @@ upcoming processing through the other functions of the family.  The
 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

Re: [PATCH 28/37] Manual typos: System Management

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/sysinfo.texi: Fix typos in the manual.
> ---
>  manual/sysinfo.texi |   52 +++++++++++++++++++++++++--------------------------
>  1 file changed, 26 insertions(+), 26 deletions(-)
>

[PATCH 36/37] Manual typos: Library Maintenance

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 179 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/maint.texi: Fix typos in the manual.
---
 manual/maint.texi |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0036-Manual-typos-Library-Maintenance.patch --]
[-- Type: text/x-patch; name="0036-Manual-typos-Library-Maintenance.patch", Size: 586 bytes --]

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}.

Re: [PATCH 36/37] Manual typos: Library Maintenance

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/maint.texi: Fix typos in the manual.
> ---
>  manual/maint.texi |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

[PATCH 32/37] Manual typos: POSIX Threads

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/threads.texi: Fix typos in the manual.
---
 manual/threads.texi |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0032-Manual-typos-POSIX-Threads.patch --]
[-- Type: text/x-patch; name="0032-Manual-typos-POSIX-Threads.patch", Size: 406 bytes --]

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

Re: [PATCH 32/37] Manual typos: POSIX Threads

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/threads.texi: Fix typos in the manual.
> ---
>  manual/threads.texi |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

[PATCH 34/37] Manual typos: C Language Facilities in the Library

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/lang.texi: Fix typos in the manual.
---
 manual/lang.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0034-Manual-typos-C-Language-Facilities-in-the-Library.patch --]
[-- Type: text/x-patch; name="0034-Manual-typos-C-Language-Facilities-in-the-Library.patch", Size: 1122 bytes --]

diff --git a/manual/lang.texi b/manual/lang.texi
index 7f8a368..96346ac 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
@@ -1061,7 +1061,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}.
 

Re: [PATCH 34/37] Manual typos: C Language Facilities in the Library

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/lang.texi: Fix typos in the manual.
> ---
>  manual/lang.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

[PATCH 16/37] Manual typos: Syslog

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 185 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/syslog.texi: Fix typos in the manual.
---
 manual/syslog.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0016-Manual-typos-Syslog.patch --]
[-- Type: text/x-patch; name="0016-Manual-typos-Syslog.patch", Size: 1174 bytes --]

diff --git a/manual/syslog.texi b/manual/syslog.texi
index a08e103..7fa0708 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},

Re: [PATCH 16/37] Manual typos: Syslog

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/syslog.texi: Fix typos in the manual.
> ---
>  manual/syslog.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

[PATCH 04/37] Manual typos: Character Handling

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/ctype.texi: Fix typos in the manual.
---
 manual/ctype.texi |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0004-Manual-typos-Character-Handling.patch --]
[-- Type: text/x-patch; name="0004-Manual-typos-Character-Handling.patch", Size: 840 bytes --]

diff --git a/manual/ctype.texi b/manual/ctype.texi
index 2d73d4e..818c095 100644
--- a/manual/ctype.texi
+++ b/manual/ctype.texi
@@ -345,8 +345,8 @@ This type is defined in @file{wctype.h}.
 @c compiler optimizations, but given the decision that setlocale is
 @c MT-Unsafe, all this would afford us would be the ability to not mark
 @c this function with @mtslocale.
-The @code{wctype} returns a value representing a class of wide
-characters which is identified by the string @var{property}.  Beside
+@code{wctype} returns a value representing a class of wide
+characters which is identified by the string @var{property}.  Besides
 some standard properties each locale can define its own ones.  In case
 no property with the given name is known for the current locale
 selected for the @code{LC_CTYPE} category, the function returns zero.

Re: [PATCH 04/37] Manual typos: Character Handling

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/ctype.texi: Fix typos in the manual.
> ---
>  manual/ctype.texi |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>

Re: [PATCH 04/37] Manual typos: Character Handling

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 35/37] Manual typos: Installing

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 252 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/install.texi: Fix typos in the manual.
	* INSTALL: Regenerated.
---
 INSTALL             |    8 ++++----
 manual/install.texi |    6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0035-Manual-typos-Installing.patch --]
[-- Type: text/x-patch; name="0035-Manual-typos-Installing.patch", Size: 2267 bytes --]

diff --git a/INSTALL b/INSTALL
index 31e256d..5c02216 100644
--- a/INSTALL
+++ b/INSTALL
@@ -161,8 +161,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'
@@ -199,8 +199,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 95021b4..ad91c6b 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -192,8 +192,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}
@@ -231,7 +231,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

Re: [PATCH 35/37] Manual typos: Installing

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:55 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/install.texi: Fix typos in the manual.
>         * INSTALL: Regenerated.
> ---
>  INSTALL             |    8 ++++----
>  manual/install.texi |    6 +++---
>  2 files changed, 7 insertions(+), 7 deletions(-)
>

[PATCH 24/37] Manual typos: Processes

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/process.texi: Fix typos in the manual.
---
 manual/process.texi |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0024-Manual-typos-Processes.patch --]
[-- Type: text/x-patch; name="0024-Manual-typos-Processes.patch", Size: 707 bytes --]

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,

Re: [PATCH 24/37] Manual typos: Processes

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/process.texi: Fix typos in the manual.
> ---
>  manual/process.texi |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

[PATCH 15/37] Manual typos: Low-Level Terminal Interface

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 203 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/terminal.texi: Fix typos in the manual.
---
 manual/terminal.texi |   18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0015-Manual-typos-Low-Level-Terminal-Interface.patch --]
[-- Type: text/x-patch; name="0015-Manual-typos-Low-Level-Terminal-Interface.patch", Size: 4516 bytes --]

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.
 

Re: [PATCH 15/37] Manual typos: Low-Level Terminal Interface

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/terminal.texi: Fix typos in the manual.
> ---
>  manual/terminal.texi |   18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
>

[PATCH 07/37] Manual typos: Locales and Internationalization

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 197 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/locale.texi: Fix typos in the manual.
---
 manual/locale.texi |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0007-Manual-typos-Locales-and-Internationalization.patch --]
[-- Type: text/x-patch; name="0007-Manual-typos-Locales-and-Internationalization.patch", Size: 3712 bytes --]

diff --git a/manual/locale.texi b/manual/locale.texi
index 1828500..d227d03 100644
--- a/manual/locale.texi
+++ b/manual/locale.texi
@@ -365,7 +365,7 @@ The function @code{setlocale} sets the current locale for category
 @var{category} to @var{locale}.
 
 If @var{category} is @code{LC_ALL}, this specifies the locale for all
-purposes.  The other possible values of @var{category} specify an
+purposes.  The other possible values of @var{category} specify a
 single purpose (@pxref{Locale Categories}).
 
 You can also use this function to find out the current locale by passing
@@ -407,7 +407,7 @@ name is used if possible.
 
 The effective locale name (either the second argument to
 @code{setlocale}, or if the argument is an empty string, the name
-obtained from the process environment) must be valid locale name.
+obtained from the process environment) must be a valid locale name.
 @xref{Locale Names}.
 
 If you specify an invalid locale name, @code{setlocale} returns a null
@@ -815,7 +815,7 @@ The members with the @code{int_} prefix apply to the
 @code{int_curr_symbol} while the other two apply to
 @code{currency_symbol}.  There is one specialty with the
 @code{int_curr_symbol}, though.  Since all legal values contain a space
-at the end the string one either printf this space (if the currency
+at the end of the string one either prints this space (if the currency
 symbol must appear in front and must be separated) or one has to avoid
 printing this character at all (especially when at the end of the
 string).
@@ -849,7 +849,7 @@ unreasonable.)
 @itemx char int_n_sign_posn
 These members are small integers that indicate how to
 position the sign for nonnegative and negative monetary quantities,
-respectively.  (The string used by the sign is what was specified with
+respectively.  (The string used for the sign is what was specified with
 @code{positive_sign} or @code{negative_sign}.)  The possible values are
 as follows:
 
@@ -1133,11 +1133,11 @@ should be used.
 @end vtable
 
 The file @file{langinfo.h} defines a lot more symbols but none of them
-is official.  Using them is not portable, and the format of the
+are official.  Using them is not portable, and the format of the
 return values might change.  Therefore we recommended you not use
 them.
 
-Note that the return value for any valid argument can be used for
+Note that the return value for any valid argument can be used
 in all situations (with the possible exception of the am/pm time formatting
 codes).  If the user has not selected any locale for the
 appropriate category, @code{nl_langinfo} returns the information from the
@@ -1240,7 +1240,7 @@ it does not fill the entire field width.
 @end table
 @end itemize
 
-The next part of a specification is an optional field width.  If no
+The next part of the specification is an optional field width.  If no
 width is specified @math{0} is taken.  During output, the function first
 determines how much space is required.  If it requires at least as many
 characters as given by the field width, it is output using as much space
@@ -1413,7 +1413,7 @@ access to the corresponding locale definitions.
 @c Calls nl_langinfo with YESEXPR and NOEXPR, triggering @mtslocale but
 @c it's regcomp and regexec that bring in all of the safety issues.
 @c regfree is also called, but it doesn't introduce any further issues.
-The function @code{rpmatch} checks the string in @var{response} whether
+The function @code{rpmatch} checks the string in @var{response} for whether
 or not it is a correct yes-or-no answer and if yes, which one.  The
 check uses the @code{YESEXPR} and @code{NOEXPR} data in the
 @code{LC_MESSAGES} category of the currently selected locale.  The

Re: [PATCH 07/37] Manual typos: Locales and Internationalization

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/locale.texi: Fix typos in the manual.
> ---
>  manual/locale.texi |   16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
>

Re: [PATCH 07/37] Manual typos: Locales and Internationalization

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 10/37] Manual typos: Pattern Matching

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 209 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/pattern.texi: Fix typos in the manual.
---
 manual/pattern.texi |   24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0010-Manual-typos-Pattern-Matching.patch --]
[-- Type: text/x-patch; name="0010-Manual-typos-Pattern-Matching.patch", Size: 4958 bytes --]

diff --git a/manual/pattern.texi b/manual/pattern.texi
index d1b9275..a0c612a 100644
--- a/manual/pattern.texi
+++ b/manual/pattern.texi
@@ -134,7 +134,7 @@ Ignore case in comparing @var{string} to @var{pattern}.
 @item FNM_EXTMATCH
 @cindex Korn Shell
 @pindex ksh
-Recognize beside the normal patterns also the extended patterns
+Besides the normal patterns, also recognize the extended patterns
 introduced in @file{ksh}.  The patterns are written in the form
 explained in the following table where @var{pattern-list} is a @code{|}
 separated list of patterns.
@@ -477,8 +477,8 @@ In the event of an error, @code{glob} stores information in
 It is important to notice that the @code{glob} function will not fail if
 it encounters directories or files which cannot be handled without the
 LFS interfaces.  The implementation of @code{glob} is supposed to use
-these functions internally.  This at least is the assumptions made by
-the Unix standard.  The GNU extension of allowing the user to provide
+these functions internally.  This at least is the assumption made by
+the Unix standard.  The GNU extension of allowing the user to provide their
 own directory handling and @code{stat} functions complicates things a
 bit.  If these callback functions are used and a large file or directory
 is encountered @code{glob} @emph{can} fail.
@@ -493,13 +493,13 @@ The @code{glob64} function was added as part of the Large File Summit
 extensions but is not part of the original LFS proposal.  The reason for
 this is simple: it is not necessary.  The necessity for a @code{glob64}
 function is added by the extensions of the GNU @code{glob}
-implementation which allows the user to provide own directory handling
+implementation which allows the user to provide their own directory handling
 and @code{stat} functions.  The @code{readdir} and @code{stat} functions
 do depend on the choice of @code{_FILE_OFFSET_BITS} since the definition
 of the types @code{struct dirent} and @code{struct stat} will change
 depending on the choice.
 
-Beside this difference the @code{glob64} works just like @code{glob} in
+Besides this difference, @code{glob64} works just like @code{glob} in
 all aspects.
 
 This function is a GNU extension.
@@ -630,7 +630,7 @@ result if the pattern used for matching contains any wildcard character.
 @comment glob.h
 @comment GNU
 @item GLOB_ALTDIRFUNC
-Instead of the using the using the normal functions for accessing the
+Instead of using the normal functions for accessing the
 filesystem the @code{glob} implementation uses the user-supplied
 functions specified in the structure pointed to by @var{pglob}
 parameter.  For more information about the functions refer to the
@@ -640,7 +640,7 @@ sections about directory handling see @ref{Accessing Directories}, and
 @comment glob.h
 @comment GNU
 @item GLOB_BRACE
-If this flag is given the handling of braces in the pattern is changed.
+If this flag is given, the handling of braces in the pattern is changed.
 It is now required that braces appear correctly grouped.  I.e., for each
 opening brace there must be a closing one.  Braces can be used
 recursively.  So it is possible to define one brace expression in
@@ -682,7 +682,7 @@ return it as the sole ``matching'' word, even if no file exists by that name.
 @comment glob.h
 @comment GNU
 @item GLOB_TILDE
-If this flag is used the character @code{~} (tilde) is handled special
+If this flag is used the character @code{~} (tilde) is handled specially
 if it appears at the beginning of the pattern.  Instead of being taken
 verbatim it is used to represent the home directory of a known user.
 
@@ -719,14 +719,14 @@ This functionality is equivalent to what is available in C-shells if the
 @comment glob.h
 @comment GNU
 @item GLOB_TILDE_CHECK
-If this flag is used @code{glob} behaves like as if @code{GLOB_TILDE} is
+If this flag is used @code{glob} behaves as if @code{GLOB_TILDE} is
 given.  The only difference is that if the user name is not available or
 the home directory cannot be determined for other reasons this leads to
 an error.  @code{glob} will return @code{GLOB_NOMATCH} instead of using
 the pattern itself as the name.
 
 This functionality is equivalent to what is available in C-shells if
-@code{nonomatch} flag is not set.
+the @code{nonomatch} flag is not set.
 
 @comment glob.h
 @comment GNU
@@ -1196,7 +1196,7 @@ Ignore case when matching letters.
 @comment regex.h
 @comment POSIX.2
 @item REG_NOSUB
-Don't bother storing the contents of the @var{matches-ptr} array.
+Don't bother storing the contents of the @var{matchptr} array.
 
 @comment regex.h
 @comment POSIX.2
@@ -1531,7 +1531,7 @@ subexpression.
 @comment regex.h
 @comment POSIX.2
 @deftp {Data Type} regmatch_t
-This is the data type of the @var{matcharray} array that you pass to
+This is the data type of the @var{matchptr} array that you pass to
 @code{regexec}.  It contains two structure fields, as follows:
 
 @table @code

Re: [PATCH 10/37] Manual typos: Pattern Matching

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/pattern.texi: Fix typos in the manual.
> ---
>  manual/pattern.texi |   24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
>

Re: [PATCH 10/37] Manual typos: Pattern Matching

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 18/37] Manual typos: Arithmetic Functions

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 195 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/arith.texi: Fix typos in the manual.
---
 manual/arith.texi |   16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0018-Manual-typos-Arithmetic-Functions.patch --]
[-- Type: text/x-patch; name="0018-Manual-typos-Arithmetic-Functions.patch", Size: 3081 bytes --]

diff --git a/manual/arith.texi b/manual/arith.texi
index 72682f0..5e55f62 100644
--- a/manual/arith.texi
+++ b/manual/arith.texi
@@ -162,7 +162,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}.
 
@@ -533,7 +533,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
@@ -970,7 +970,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
@@ -991,7 +991,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
@@ -1114,8 +1114,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.
 
@@ -1127,8 +1127,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.
 

Re: [PATCH 18/37] Manual typos: Arithmetic Functions

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/arith.texi: Fix typos in the manual.
> ---
>  manual/arith.texi |   16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
>

[PATCH 23/37] Manual typos: The Basic Program/System Interface

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 336 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/argp.texi: Fix typos in the manual.
	* manual/getopt.texi: Likewise.
	* manual/startup.texi: Likewise.
---
 manual/argp.texi    |   10 +++++-----
 manual/getopt.texi  |   10 +++++-----
 manual/startup.texi |    8 ++++----
 3 files changed, 14 insertions(+), 14 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0023-Manual-typos-The-Basic-Program-System-Interface.patch --]
[-- Type: text/x-patch; name="0023-Manual-typos-The-Basic-Program-System-Interface.patch", Size: 6862 bytes --]

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.
 

Re: [PATCH 23/37] Manual typos: The Basic Program/System Interface

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/argp.texi: Fix typos in the manual.
>         * manual/getopt.texi: Likewise.
>         * manual/startup.texi: Likewise.
> ---
>  manual/argp.texi    |   10 +++++-----
>  manual/getopt.texi  |   10 +++++-----
>  manual/startup.texi |    8 ++++----
>  3 files changed, 14 insertions(+), 14 deletions(-)
>

[PATCH 05/37] Manual typos: String and Array Utilities

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 207 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/string.texi: Fix typos in the manual.
---
 manual/string.texi |   24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0005-Manual-typos-String-and-Array-Utilities.patch --]
[-- Type: text/x-patch; name="0005-Manual-typos-String-and-Array-Utilities.patch", Size: 5279 bytes --]

diff --git a/manual/string.texi b/manual/string.texi
index 016fd0b..41e14e5 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -503,7 +503,7 @@ The value returned by @code{memmove} is the value of @var{to}.
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 @code{wmemmove} copies the @var{size} wide characters at @var{wfrom}
 into the @var{size} wide characters at @var{wto}, even if those two
-blocks of space overlap.  In the case of overlap, @code{memmove} is
+blocks of space overlap.  In the case of overlap, @code{wmemmove} is
 careful to copy the original values of the wide characters in the block
 at @var{wfrom}, including those wide characters which also belong to the
 block at @var{wto}.
@@ -801,7 +801,7 @@ bytes for the end of the string so that we can append the next string.
 For all strings in total the comparisons necessary to find the end of
 the intermediate results sums up to 5500!  If we combine the copying
 with the search for the allocation we can write this function more
-efficient:
+efficiently:
 
 @smallexample
 char *
@@ -859,15 +859,15 @@ concat (const char *str, @dots{})
 With a bit more knowledge about the input strings one could fine-tune
 the memory allocation.  The difference we are pointing to here is that
 we don't use @code{strcat} anymore.  We always keep track of the length
-of the current intermediate result so we can safe us the search for the
+of the current intermediate result so we can save ourselves the search for the
 end of the string and use @code{mempcpy}.  Please note that we also
-don't use @code{stpcpy} which might seem more natural since we handle
-with strings.  But this is not necessary since we already know the
+don't use @code{stpcpy} which might seem more natural since we are handling
+strings.  But this is not necessary since we already know the
 length of the string and therefore can use the faster memory copying
 function.  The example would work for wide characters the same way.
 
 Whenever a programmer feels the need to use @code{strcat} she or he
-should think twice and look through the program whether the code cannot
+should think twice and look through the program to see whether the code cannot
 be rewritten to take advantage of already calculated results.  Again: it
 is almost always unnecessary to use @code{strcat}.
 
@@ -1311,7 +1311,7 @@ return value is zero.
 @comment ISO
 @deftypefun int wcsncmp (const wchar_t *@var{ws1}, const wchar_t *@var{ws2}, size_t @var{size})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
-This function is the similar to @code{wcscmp}, except that no more than
+This function is similar to @code{wcscmp}, except that no more than
 @var{size} wide characters are compared.  In other words, if the two
 strings are the same in their first @var{size} wide characters, the
 return value is zero.
@@ -2604,7 +2604,7 @@ functions accept either a pointer and a size argument, or pointers to
 them, if they will be modified.
 
 The argz functions use @code{malloc}/@code{realloc} to allocate/grow
-argz vectors, and so any argz vector creating using these functions may
+argz vectors, and so any argz vector created using these functions may
 be freed by using @code{free}; conversely, any argz function that may
 grow a string expects that string to have been allocated using
 @code{malloc} (those argz functions that only examine their arguments or
@@ -2640,7 +2640,7 @@ byte @var{sep}.
 
 @comment argz.h
 @comment GNU
-@deftypefun {size_t} argz_count (const char *@var{argz}, size_t @var{arg_len})
+@deftypefun {size_t} argz_count (const char *@var{argz}, size_t @var{argz_len})
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 Returns the number of elements in the argz vector @var{argz} and
 @var{argz_len}.
@@ -2775,7 +2775,7 @@ invariant is maintained for argz vectors created by the functions here.
 Replace any occurrences of the string @var{str} in @var{argz} with
 @var{with}, reallocating @var{argz} as necessary.  If
 @var{replace_count} is non-zero, @code{*@var{replace_count}} will be
-incremented by number of replacements performed.
+incremented by the number of replacements performed.
 @end deftypefun
 
 @node Envz Functions, , Argz Functions, Argz and Envz Vectors
@@ -2795,7 +2795,7 @@ considered the name of a ``null'' entry, as distinct from an entry with an
 empty value: @code{envz_get} will return @code{0} if given the name of null
 entry, whereas an entry with an empty value would result in a value of
 @code{""}; @code{envz_entry} will still find such entries, however.  Null
-entries can be removed with @code{envz_strip} function.
+entries can be removed with the @code{envz_strip} function.
 
 As with argz functions, envz functions that may allocate memory (and thus
 fail) have a return type of @code{error_t}, and return either @code{0} or
@@ -2834,7 +2834,7 @@ The @code{envz_add} function adds an entry to @code{*@var{envz}}
 (updating @code{*@var{envz}} and @code{*@var{envz_len}}) with the name
 @var{name}, and value @var{value}.  If an entry with the same name
 already exists in @var{envz}, it is removed first.  If @var{value} is
-@code{0}, then the new entry will the special null type of entry
+@code{0}, then the new entry will be the special null type of entry
 (mentioned above).
 @end deftypefun
 

Re: [PATCH 05/37] Manual typos: String and Array Utilities

[Chris Leonard]

 +1

sorry this is going slowly, others welcome to jump in.

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/string.texi: Fix typos in the manual.
> ---
>  manual/string.texi |   24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
>

Re: [PATCH 05/37] Manual typos: String and Array Utilities

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 27/37] Manual typos: Users and Groups

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 216 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/users.texi: Fix typos in the manual.
---
 manual/users.texi |   35 +++++++++++++++++------------------
 1 file changed, 17 insertions(+), 18 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0027-Manual-typos-Users-and-Groups.patch --]
[-- Type: text/x-patch; name="0027-Manual-typos-Users-and-Groups.patch", Size: 7146 bytes --]

diff --git a/manual/users.texi b/manual/users.texi
index e8f0f3b..7424b4f 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,8 +2629,8 @@ 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
 the entries can be a wildcard entry matching all inputs.  A last
@@ -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.

Re: [PATCH 27/37] Manual typos: Users and Groups

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/users.texi: Fix typos in the manual.
> ---
>  manual/users.texi |   35 +++++++++++++++++------------------
>  1 file changed, 17 insertions(+), 18 deletions(-)
>

[PATCH 09/37] Manual typos: Searching and Sorting

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 219 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/search.texi: Fix typos in the manual.
---
 manual/search.texi |   36 ++++++++++++++++++------------------
 1 file changed, 18 insertions(+), 18 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0009-Manual-typos-Searching-and-Sorting.patch --]
[-- Type: text/x-patch; name="0009-Manual-typos-Searching-and-Sorting.patch", Size: 7287 bytes --]

diff --git a/manual/search.texi b/manual/search.texi
index 662527f..a56b3e0 100644
--- a/manual/search.texi
+++ b/manual/search.texi
@@ -76,7 +76,7 @@ two functions can be found in @file{search.h}.
 The @code{lfind} function searches in the array with @code{*@var{nmemb}}
 elements of @var{size} bytes pointed to by @var{base} for an element
 which matches the one pointed to by @var{key}.  The function pointed to
-by @var{compar} is used decide whether two elements match.
+by @var{compar} is used to decide whether two elements match.
 
 The return value is a pointer to the matching element in the array
 starting at @var{base} if it is found.  If no matching element is
@@ -293,15 +293,15 @@ The weakest aspect of this function is that there can be at most one
 hashing table used through the whole program.  The table is allocated
 in local memory out of control of the programmer.  As an extension @theglibc{}
 provides an additional set of functions with a reentrant
-interface which provide a similar interface but which allow to keep
+interface which provides a similar interface but which allows keeping
 arbitrarily many hashing tables.
 
 It is possible to use more than one hashing table in the program run if
 the former table is first destroyed by a call to @code{hdestroy}.
 
-The function returns a non-zero value if successful.  If it return zero
+The function returns a non-zero value if successful.  If it returns zero,
 something went wrong.  This could either mean there is already a hashing
-table in use or the program runs out of memory.
+table in use or the program ran out of memory.
 @end deftypefun
 
 @comment search.h
@@ -325,7 +325,7 @@ If it is really necessary to free a table and all elements the
 programmer has to keep a list of all table elements and before calling
 @code{hdestroy} s/he has to free all element's data using this list.
 This is a very unpleasant mechanism and it also shows that this kind of
-hashing tables is mainly meant for tables which are created once and
+hashing table is mainly meant for tables which are created once and
 used until the end of the program run.
 @end deftypefun
 
@@ -357,8 +357,8 @@ this element might stay undefined since it is not used.
 @c hsearch @mtasurace:hsearch @acucorrupt/action==ENTER
 @c  hsearch_r dup @mtsrace:htab @acucorrupt/action==ENTER
 To search in a hashing table created using @code{hcreate} the
-@code{hsearch} function must be used.  This function can perform simple
-search for an element (if @var{action} has the @code{FIND}) or it can
+@code{hsearch} function must be used.  This function can perform a simple
+search for an element (if @var{action} has the value @code{FIND}) or it can
 alternatively insert the key element into the hashing table.  Entries
 are never replaced.
 
@@ -366,7 +366,7 @@ The key is denoted by a pointer to an object of type @code{ENTRY}.  For
 locating the corresponding position in the hashing table only the
 @code{key} element of the structure is used.
 
-If an entry with matching key is found the @var{action} parameter is
+If an entry with a matching key is found the @var{action} parameter is
 irrelevant.  The found entry is returned.  If no matching entry is found
 and the @var{action} parameter has the value @code{FIND} the function
 returns a @code{NULL} pointer.  If no entry is found and the
@@ -375,7 +375,7 @@ to the hashing table which is initialized with the parameter @var{item}.
 A pointer to the newly added entry is returned.
 @end deftypefun
 
-As mentioned before the hashing table used by the functions described so
+As mentioned before, the hashing table used by the functions described so
 far is global and there can be at any time at most one hashing table in
 the program.  A solution is to use the following functions which are a
 GNU extension.  All have in common that they operate on a hashing table
@@ -416,7 +416,7 @@ function.
 
 The return value is non-zero if the operation was successful.  If the
 return value is zero, something went wrong, which probably means the
-programs ran out of memory.
+program ran out of memory.
 @end deftypefun
 
 @comment search.h
@@ -434,7 +434,7 @@ programs ran out of memory.
 @c  free dup @ascuheap @acsmem
 The @code{hdestroy_r} function frees all resources allocated by the
 @code{hcreate_r} function for this very same object @var{htab}.  As for
-@code{hdestroy} it is the programs responsibility to free the strings
+@code{hdestroy} it is the program's responsibility to free the strings
 for the elements of the table.
 @end deftypefun
 
@@ -455,8 +455,8 @@ table described by the object pointed to by @var{htab} (which is
 initialized by a call to @code{hcreate_r}).
 
 Another difference to @code{hcreate} is that the pointer to the found
-entry in the table is not the return value of the functions.  It is
-returned by storing it in a pointer variables pointed to by the
+entry in the table is not the return value of the function.  It is
+returned by storing it in a pointer variable pointed to by the
 @var{retval} parameter.  The return value of the function is an integer
 value indicating success if it is non-zero and failure if it is zero.
 In the latter case the global variable @var{errno} signals the reason for
@@ -542,7 +542,7 @@ new element is entered (note that the @var{rootp} parameter points to a
 constant pointer).  Instead the function returns @code{NULL}.
 @end deftypefun
 
-Another advantage of the @code{tsearch} function in contrast to the
+Another advantage of the @code{tsearch} functions in contrast to the
 @code{hsearch} functions is that there is an easy way to remove
 elements.
 
@@ -566,7 +566,7 @@ is deleted @code{tdelete} returns some unspecified value not equal to
 @safety{@prelim{}@mtsafe{}@asunsafe{@ascuheap{}}@acunsafe{@acsmem{}}}
 If the complete search tree has to be removed one can use
 @code{tdestroy}.  It frees all resources allocated by the @code{tsearch}
-function to generate the tree pointed to by @var{vroot}.
+functions to generate the tree pointed to by @var{vroot}.
 
 For the data in each tree node the function @var{freefct} is called.
 The pointer to the data is passed as the argument to the function.  If
@@ -577,7 +577,7 @@ This function is a GNU extension and not covered by the @w{System V} or
 X/Open specifications.
 @end deftypefun
 
-In addition to the function to create and destroy the tree data
+In addition to the functions to create and destroy the tree data
 structure, there is another function which allows you to apply a
 function to all elements of the tree.  The function must have this type:
 
@@ -625,8 +625,8 @@ For each node in the tree with a node pointed to by @var{root}, the
 @var{value} set to @code{leaf}.  For internal nodes the function is
 called three times, setting the @var{value} parameter or @var{action} to
 the appropriate value.  The @var{level} argument for the @var{action}
-function is computed while descending the tree with increasing the value
-by one for the descend to a child, starting with the value @math{0} for
+function is computed while descending the tree by increasing the value
+by one for each descent to a child, starting with the value @math{0} for
 the root node.
 
 Since the functions used for the @var{action} parameter to @code{twalk}

Re: [PATCH 09/37] Manual typos: Searching and Sorting

[Chris Leonard]

+1

cjl


On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/search.texi: Fix typos in the manual.
> ---
>  manual/search.texi |   36 ++++++++++++++++++------------------
>  1 file changed, 18 insertions(+), 18 deletions(-)
>

Re: [PATCH 09/37] Manual typos: Searching and Sorting

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 14/37] Manual typos: Sockets

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 211 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/socket.texi: Fix typos in the manual.
---
 manual/socket.texi |   28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0014-Manual-typos-Sockets.patch --]
[-- Type: text/x-patch; name="0014-Manual-typos-Sockets.patch", Size: 6268 bytes --]

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.

Re: [PATCH 14/37] Manual typos: Sockets

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/socket.texi: Fix typos in the manual.
> ---
>  manual/socket.texi |   28 ++++++++++++++--------------
>  1 file changed, 14 insertions(+), 14 deletions(-)
>

[PATCH 13/37] Manual typos: File System Interface

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 227 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/filesys.texi: Fix typos in the manual.
---
 manual/filesys.texi |   42 +++++++++++++++++++++---------------------
 1 file changed, 21 insertions(+), 21 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0013-Manual-typos-File-System-Interface.patch --]
[-- Type: text/x-patch; name="0013-Manual-typos-File-System-Interface.patch", Size: 9408 bytes --]

diff --git a/manual/filesys.texi b/manual/filesys.texi
index b323664..bdadefb 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.

Re: [PATCH 13/37] Manual typos: File System Interface

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/filesys.texi: Fix typos in the manual.
> ---
>  manual/filesys.texi |   42 +++++++++++++++++++++---------------------
>  1 file changed, 21 insertions(+), 21 deletions(-)
>

[PATCH 19/37] Manual typos: Date and Time

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 219 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/time.texi: Fix typos in the manual.
---
 manual/time.texi |   40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0019-Manual-typos-Date-and-Time.patch --]
[-- Type: text/x-patch; name="0019-Manual-typos-Date-and-Time.patch", Size: 8042 bytes --]

diff --git a/manual/time.texi b/manual/time.texi
index f94cbe4..f42f7f9 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.
 

Re: [PATCH 19/37] Manual typos: Date and Time

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/time.texi: Fix typos in the manual.
> ---
>  manual/time.texi |   40 ++++++++++++++++++++--------------------
>  1 file changed, 20 insertions(+), 20 deletions(-)
>

[PATCH 12/37] Manual typos: Low-Level Input/Output

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 233 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/llio.texi: Fix typos in the manual.
---
 manual/llio.texi |   78 +++++++++++++++++++++++++++---------------------------
 1 file changed, 39 insertions(+), 39 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0012-Manual-typos-Low-Level-Input-Output.patch --]
[-- Type: text/x-patch; name="0012-Manual-typos-Low-Level-Input-Output.patch", Size: 16803 bytes --]

diff --git a/manual/llio.texi b/manual/llio.texi
index 019dea2..cb47302 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

Re: [PATCH 12/37] Manual typos: Low-Level Input/Output

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/llio.texi: Fix typos in the manual.
> ---
>  manual/llio.texi |   78 +++++++++++++++++++++++++++---------------------------
>  1 file changed, 39 insertions(+), 39 deletions(-)
>

[PATCH 17/37] Manual typos: Mathematics

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 215 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/math.texi: Fix typos in the manual.
---
 manual/math.texi |   36 ++++++++++++++++++------------------
 1 file changed, 18 insertions(+), 18 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0017-Manual-typos-Mathematics.patch --]
[-- Type: text/x-patch; name="0017-Manual-typos-Mathematics.patch", Size: 8559 bytes --]

diff --git a/manual/math.texi b/manual/math.texi
index 5c9f7b9..0d9b09b 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
 
@@ -729,7 +729,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
@@ -872,7 +872,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
@@ -1145,7 +1145,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
 
@@ -1297,7 +1297,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.
 
@@ -1582,7 +1582,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.
 
@@ -1784,7 +1784,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.
@@ -2026,7 +2026,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

Re: [PATCH 17/37] Manual typos: Mathematics

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/math.texi: Fix typos in the manual.
> ---
>  manual/math.texi |   36 ++++++++++++++++++------------------
>  1 file changed, 18 insertions(+), 18 deletions(-)
>

[PATCH 06/37] Manual typos: Character Set Handling

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 236 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/charset.texi: Fix typos in the manual.
---
 manual/charset.texi |   68 +++++++++++++++++++++++++--------------------------
 1 file changed, 34 insertions(+), 34 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0006-Manual-typos-Character-Set-Handling.patch --]
[-- Type: text/x-patch; name="0006-Manual-typos-Character-Set-Handling.patch", Size: 17596 bytes --]

diff --git a/manual/charset.texi b/manual/charset.texi
index 68aecd3..147d9c5 100644
--- a/manual/charset.texi
+++ b/manual/charset.texi
@@ -31,7 +31,7 @@ library to support multiple character sets.
 @node Extended Char Intro
 @section Introduction to Extended Characters
 
-A variety of solutions is available to overcome the differences between
+A variety of solutions are available to overcome the differences between
 character sets with a 1:1 relation between bytes and characters and
 character sets with ratios of 2:1 or 4:1.  The remainder of this
 section gives a few examples to help understand the design decisions
@@ -202,7 +202,7 @@ defined in @file{wchar.h}.
 @end deftypevr
 
 
-These internal representations present problems when it comes to storing
+These internal representations present problems when it comes to storage
 and transmittal.  Because each single wide character consists of more
 than one byte, they are affected by byte-ordering.  Thus, machines with
 different endianesses would see different values when accessing the same
@@ -389,7 +389,7 @@ the conversion is necessary take a look at the @code{iconv} functions
 @subsection Selecting the conversion and its properties
 
 We already said above that the currently selected locale for the
-@code{LC_CTYPE} category decides about the conversion that is performed
+@code{LC_CTYPE} category decides the conversion that is performed
 by the functions we are about to describe.  Each locale uses its own
 character set (given as an argument to @code{localedef}) and this is the
 one assumed as the external multibyte encoding.  The wide character
@@ -549,7 +549,7 @@ necessary output code (@pxref{Converting Strings}).  Please note that with
 @theglibc{} it is not necessary to perform this extra action for the
 conversion from multibyte text to wide character text since the wide
 character encoding is not stateful.  But there is nothing mentioned in
-any standard that prohibits making @code{wchar_t} using a stateful
+any standard that prohibits making @code{wchar_t} use a stateful
 encoding.
 
 @node Converting a Character
@@ -559,7 +559,7 @@ The most fundamental of the conversion functions are those dealing with
 single characters.  Please note that this does not always mean single
 bytes.  But since there is very often a subset of the multibyte
 character set that consists of single byte sequences, there are
-functions to help with converting bytes.  Frequently, ASCII is a subpart
+functions to help with converting bytes.  Frequently, ASCII is a subset
 of the multibyte character set.  In such a scenario, each ASCII character
 stands for itself, and all other characters have at least a first byte
 that is beyond the range @math{0} to @math{127}.
@@ -596,7 +596,7 @@ and is declared in @file{wchar.h}.
 Despite the limitation that the single byte value is always interpreted
 in the initial state, this function is actually useful most of the time.
 Most characters are either entirely single-byte character sets or they
-are extension to ASCII.  But then it is possible to write code like this
+are extensions to ASCII.  But then it is possible to write code like this
 (not that this specific example is very useful):
 
 @smallexample
@@ -643,7 +643,7 @@ value of this function is this character.  Otherwise the return value is
 is declared in @file{wchar.h}.
 @end deftypefun
 
-There are more general functions to convert single character from
+There are more general functions to convert single characters from
 multibyte representation to wide characters and vice versa.  These
 functions pose no limit on the length of the multibyte representation
 and they also do not require it to be in the initial state.
@@ -731,7 +731,7 @@ bytes is adjusted.
 
 The only non-obvious thing about @code{mbrtowc} might be the way memory
 is allocated for the result.  The above code uses the fact that there
-can never be more wide characters in the converted results than there are
+can never be more wide characters in the converted result than there are
 bytes in the multibyte input string.  This method yields a pessimistic
 guess about the size of the result, and if many wide character strings
 have to be constructed this way or if the strings are long, the extra
@@ -813,7 +813,7 @@ Therefore, the @code{mbrlen} function will never read invalid memory.
 
 Now that this function is available (just to make this clear, this
 function is @emph{not} part of @theglibc{}) we can compute the
-number of wide character required to store the converted multibyte
+number of wide characters required to store the converted multibyte
 character string @var{s} using
 
 @smallexample
@@ -879,7 +879,7 @@ multibyte'') converts a single wide character into a multibyte string
 corresponding to that wide character.
 
 If @var{s} is a null pointer, the function resets the state stored in
-the objects pointed to by @var{ps} (or the internal @code{mbstate_t}
+the object pointed to by @var{ps} (or the internal @code{mbstate_t}
 object) to the initial state.  This can also be achieved by a call like
 this:
 
@@ -1020,7 +1020,7 @@ extensions that can help in some important situations.
 @deftypefun size_t mbsrtowcs (wchar_t *restrict @var{dst}, const char **restrict @var{src}, size_t @var{len}, mbstate_t *restrict @var{ps})
 @safety{@prelim{}@mtunsafe{@mtasurace{:mbsrtowcs/!ps}}@asunsafe{@asucorrupt{} @ascuheap{} @asulock{} @ascudlopen{}}@acunsafe{@acucorrupt{} @aculock{} @acsmem{} @acsfd{}}}
 The @code{mbsrtowcs} function (``multibyte string restartable to wide
-character string'') converts a NUL-terminated multibyte character
+character string'') converts the NUL-terminated multibyte character
 string at @code{*@var{src}} into an equivalent wide character string,
 including the NUL wide character at the end.  The conversion is started
 using the state information from the object pointed to by @var{ps} or
@@ -1061,7 +1061,7 @@ declared in @file{wchar.h}.
 The definition of the @code{mbsrtowcs} function has one important
 limitation.  The requirement that @var{dst} has to be a NUL-terminated
 string provides problems if one wants to convert buffers with text.  A
-buffer is normally no collection of NUL-terminated strings but instead a
+buffer is not normally a collection of NUL-terminated strings but instead a
 continuous collection of lines, separated by newline characters.  Now
 assume that a function to convert one line from a buffer is needed.  Since
 the line is not NUL-terminated, the source pointer cannot directly point
@@ -1078,7 +1078,7 @@ guess.
 @cindex stateful
 There is still a problem with the method of NUL-terminating a line right
 after the newline character, which could lead to very strange results.
-As said in the description of the @code{mbsrtowcs} function above the
+As said in the description of the @code{mbsrtowcs} function above, the
 conversion state is guaranteed to be in the initial shift state after
 processing the NUL byte at the end of the input string.  But this NUL
 byte is not really part of the text (i.e., the conversion state after
@@ -1110,7 +1110,7 @@ multibyte string'') converts the NUL-terminated wide character string at
 stores the result in the array pointed to by @var{dst}.  The NUL wide
 character is also converted.  The conversion starts in the state
 described in the object pointed to by @var{ps} or by a state object
-locally to @code{wcsrtombs} in case @var{ps} is a null pointer.  If
+local to @code{wcsrtombs} in case @var{ps} is a null pointer.  If
 @var{dst} is a null pointer, the conversion is performed as usual but the
 result is not available.  If all characters of the input string were
 successfully converted and if @var{dst} is not a null pointer, the
@@ -1123,13 +1123,13 @@ variable @code{errno} to @code{EILSEQ}, and returns @code{(size_t) -1}.
 Another reason for a premature stop is if @var{dst} is not a null
 pointer and the next converted character would require more than
 @var{len} bytes in total to the array @var{dst}.  In this case (and if
-@var{dest} is not a null pointer) the pointer pointed to by @var{src} is
+@var{dst} is not a null pointer) the pointer pointed to by @var{src} is
 assigned a value pointing to the wide character right after the last one
 successfully converted.
 
 Except in the case of an encoding error the return value of the
 @code{wcsrtombs} function is the number of bytes in all the multibyte
-character sequences stored in @var{dst}.  Before returning the state in
+character sequences stored in @var{dst}.  Before returning, the state in
 the object pointed to by @var{ps} (or the internal object in case
 @var{ps} is a null pointer) is updated to reflect the state after the
 last conversion.  The state is the initial shift state in case the
@@ -1158,11 +1158,11 @@ This new parameter specifies how many bytes at most can be used from the
 multibyte character string.  In other words, the multibyte character
 string @code{*@var{src}} need not be NUL-terminated.  But if a NUL byte
 is found within the @var{nmc} first bytes of the string, the conversion
-stops here.
+stops there.
 
 This function is a GNU extension.  It is meant to work around the
 problems mentioned above.  Now it is possible to convert a buffer with
-multibyte character text piece for piece without having to care about
+multibyte character text piece by piece without having to care about
 inserting NUL bytes and the effect of NUL bytes on the conversion state.
 @end deftypefun
 
@@ -1603,7 +1603,7 @@ common that they operate on character sets that are not directly
 specified by the functions.  The multibyte encoding used is specified by
 the currently selected locale for the @code{LC_CTYPE} category.  The
 wide character set is fixed by the implementation (in the case of @theglibc{}
-it is always UCS-4 encoded @w{ISO 10646}.
+it is always UCS-4 encoded @w{ISO 10646}).
 
 This has of course several problems when it comes to general character
 conversion:
@@ -1681,7 +1681,7 @@ This data type is an abstract type defined in @file{iconv.h}.  The user
 must not assume anything about the definition of this type; it must be
 completely opaque.
 
-Objects of this type can get assigned handles for the conversions using
+Objects of this type can be assigned handles for the conversions using
 the @code{iconv} functions.  The objects themselves need not be freed, but
 the conversions for which the handles stand for have to.
 @end deftp
@@ -1716,7 +1716,7 @@ returns @code{(iconv_t) -1}.  In this case the global variable
 @item EMFILE
 The process already has @code{OPEN_MAX} file descriptors open.
 @item ENFILE
-The system limit of open file is reached.
+The system limit of open files is reached.
 @item ENOMEM
 Not enough memory to carry out the operation.
 @item EINVAL
@@ -1778,7 +1778,7 @@ the @code{iconv_open} function.
 
 If the function call was successful the return value is @math{0}.
 Otherwise it is @math{-1} and @code{errno} is set appropriately.
-Defined error are:
+Defined errors are:
 
 @table @code
 @item EBADF
@@ -1847,7 +1847,7 @@ stop is that the output buffer is full.  And the third reason is that
 the input contains invalid characters.
 
 In all of these cases the buffer pointers after the last successful
-conversion, for input and output buffer, are stored in @var{inbuf} and
+conversion, for the input and output buffers, are stored in @var{inbuf} and
 @var{outbuf}, and the available room in each buffer is stored in
 @var{inbytesleft} and @var{outbytesleft}.
 
@@ -2087,7 +2087,7 @@ possibilities.  This does not mean 200 different character sets are
 supported; for example, conversions from one character set to a set of 10
 others might count as 10 conversions.  Together with the other direction
 this makes 20 conversion possibilities used up by one character set.  One
-can imagine the thin coverage these platform provide.  Some Unix vendors
+can imagine the thin coverage these platforms provide.  Some Unix vendors
 even provide only a handful of conversions, which renders them useless for
 almost all uses.
 
@@ -2133,7 +2133,7 @@ will succeed, but how to find @math{@cal{B}}?
 
 Unfortunately, the answer is: there is no general solution.  On some
 systems guessing might help.  On those systems most character sets can
-convert to and from UTF-8 encoded @w{ISO 10646} or Unicode text.  Beside
+convert to and from UTF-8 encoded @w{ISO 10646} or Unicode text.  Besides
 this only some very system-specific methods can help.  Since the
 conversion functions come from loadable modules and these modules must
 be stored somewhere in the filesystem, one @emph{could} try to find them
@@ -2143,7 +2143,7 @@ and whether there is an indirect route from @math{@cal{A}} to
 
 This example shows one of the design errors of @code{iconv} mentioned
 above.  It should at least be possible to determine the list of available
-conversion programmatically so that if @code{iconv_open} says there is no
+conversions programmatically so that if @code{iconv_open} says there is no
 such conversion, one could make sure this also is true for indirect
 routes.
 
@@ -2235,7 +2235,7 @@ achieve the same result as when using the real character set name.
 
 This is quite important as a character set has often many different
 names.  There is normally an official name but this need not correspond to
-the most popular name.  Beside this many character sets have special
+the most popular name.  Besides this many character sets have special
 names that are somehow constructed.  For example, all character sets
 specified by the ISO have an alias of the form @code{ISO-IR-@var{nnn}}
 where @var{nnn} is the registration number.  This allows programs that
@@ -2371,7 +2371,7 @@ itself).
 @itemx const char *__modname
 @itemx int __counter
 All these elements of the structure are used internally in the C library
-to coordinate loading and unloading the shared.  One must not expect any
+to coordinate loading and unloading the shared object.  One must not expect any
 of the other elements to be available or initialized.
 
 @item const char *__from_name
@@ -2438,7 +2438,7 @@ These elements specify the output buffer for the conversion step.  The
 @code{__outbuf} element points to the beginning of the buffer, and
 @code{__outbufend} points to the byte following the last byte in the
 buffer.  The conversion function must not assume anything about the size
-of the buffer but it can be safely assumed the there is room for at
+of the buffer but it can be safely assumed there is room for at
 least one complete character in the output buffer.
 
 Once the conversion is finished, if the conversion is the last step, the
@@ -2673,7 +2673,7 @@ Next, a data structure, which contains the necessary information about
 which conversion is selected, is allocated.  The data structure
 @code{struct iso2022jp_data} is locally defined since, outside the
 module, this data is not used at all.  Please note that if all four
-conversions this modules supports are requested there are four data
+conversions this module supports are requested there are four data
 blocks.
 
 One interesting thing is the initialization of the @code{__min_} and
@@ -2686,7 +2686,7 @@ the conversion from @code{INTERNAL} to ISO-2022-JP we have to take into
 account that escape sequences might be necessary to switch the character
 sets.  Therefore the @code{__max_needed_to} element for this direction
 gets assigned @code{MAX_NEEDED_FROM + 2}.  This takes into account the
-two bytes needed for the escape sequences to single the switching.  The
+two bytes needed for the escape sequences to signal the switching.  The
 asymmetry in the maximum values for the two directions can be explained
 easily: when reading ISO-2022-JP text, escape sequences can be handled
 alone (i.e., it is not necessary to process a real character since the
@@ -2694,7 +2694,7 @@ effect of the escape sequence can be recorded in the state information).
 The situation is different for the other direction.  Since it is in
 general not known which character comes next, one cannot emit escape
 sequences to change the state in advance.  This means the escape
-sequences that have to be emitted together with the next character.
+sequences have to be emitted together with the next character.
 Therefore one needs more room than only for the character itself.
 
 The possible return values of the initialization function are:
@@ -2740,7 +2740,7 @@ conversion function.
 @comment gconv.h
 @comment GNU
 @deftypevr {Data type} int {(*__gconv_fct)} (struct __gconv_step *, struct __gconv_step_data *, const char **, const char *, size_t *, int)
-The conversion function can be called for two basic reason: to convert
+The conversion function can be called for two basic reasons: to convert
 text or to reset the state.  From the description of the @code{iconv}
 function it can be seen why the flushing mode is necessary.  What mode
 is selected is determined by the sixth argument, an integer.  This
@@ -2817,7 +2817,7 @@ therefore will look similar to this:
 But this is not yet all.  Once the function call returns the conversion
 function might have some more to do.  If the return value of the function
 is @code{__GCONV_EMPTY_INPUT}, more room is available in the output
-buffer.  Unless the input buffer is empty the conversion, functions start
+buffer.  Unless the input buffer is empty, the conversion functions start
 all over again and process the rest of the input buffer.  If the return
 value is not @code{__GCONV_EMPTY_INPUT}, something went wrong and we have
 to recover from this.

Re: [PATCH 06/37] Manual typos: Character Set Handling

[Chris Leonard]

+1


cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/charset.texi: Fix typos in the manual.
> ---
>  manual/charset.texi |   68 +++++++++++++++++++++++++--------------------------
>  1 file changed, 34 insertions(+), 34 deletions(-)
>

Re: [PATCH 06/37] Manual typos: Character Set Handling

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 14 bytes --]

merged!
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[PATCH 11/37] Manual typos: Input/Output on Streams

[ricaljasan]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]

This is a multi-part message in MIME format.

[-- Attachment #2: Type: text/plain, Size: 234 bytes --]

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/stdio.text: Fix typos in the manual.
---
 manual/stdio.texi |   85 +++++++++++++++++++++++++++--------------------------
 1 file changed, 43 insertions(+), 42 deletions(-)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0011-Manual-typos-Input-Output-on-Streams.patch --]
[-- Type: text/x-patch; name="0011-Manual-typos-Input-Output-on-Streams.patch", Size: 18649 bytes --]

diff --git a/manual/stdio.texi b/manual/stdio.texi
index 0326f29..22f4bee 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

Re: [PATCH 11/37] Manual typos: Input/Output on Streams

[Chris Leonard]

+1

cjl

On Fri, May 6, 2016 at 3:54 AM,  <ricaljasan@pacific.net> wrote:
> 2016-05-06  Rical Jasan  <ricaljasan@pacific.net>
>
>         * manual/stdio.text: Fix typos in the manual.
> ---
>  manual/stdio.texi |   85 +++++++++++++++++++++++++++--------------------------
>  1 file changed, 43 insertions(+), 42 deletions(-)
>

[PING] [PATCH 00/37] Manual typos: Overview

[ricaljasan]

Ping.

Is it preferred that I ping each of these separately? 01-04 have been
reviewed, but 03 requested further review, so there are 34 still pending
review (and all are New and undelegated in patchwork, fwiw).

Rical

On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
> Typos addressed in this patchset include obvious mistakes such as
> repeated repeated words, wrong case or tense, speling mistakes, and
> wrong variable names.  The occasional comma is also addressed, where
> its absence introduces ambiguity, or its presence disturbs the
> sentence.
> 
> Verified patches apply cleanly against latest master and that `make
> info|html|pdf' completes without error on x86_64.
> 
> ---
>  INSTALL              |    8 +--
>  manual/argp.texi     |   10 ++--
>  manual/arith.texi    |   16 ++---
>  manual/charset.texi  |   68 ++++++++++-----------
>  manual/conf.texi     |   10 ++--
>  manual/contrib.texi  |    6 +-
>  manual/crypt.texi    |    8 +--
>  manual/ctype.texi    |    4 +-
>  manual/debug.texi    |    4 +-
>  manual/errno.texi    |   22 +++----
>  manual/filesys.texi  |   42 ++++++-------
>  manual/getopt.texi   |   10 ++--
>  manual/install.texi  |    6 +-
>  manual/intro.texi    |    2 +-
>  manual/job.texi      |    2 +-
>  manual/lang.texi     |    4 +-
>  manual/llio.texi     |   78 ++++++++++++-------------
>  manual/locale.texi   |   16 ++---
>  manual/maint.texi    |    2 +-
>  manual/math.texi     |   36 ++++++------
>  manual/memory.texi   |   24 ++++----
>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>  manual/nss.texi      |   44 +++++++-------
>  manual/pattern.texi  |   24 ++++----
>  manual/probes.texi   |    4 +-
>  manual/process.texi  |    2 +-
>  manual/resource.texi |   52 ++++++++---------
>  manual/search.texi   |   36 ++++++------
>  manual/setjmp.texi   |    8 +--
>  manual/signal.texi   |    6 +-
>  manual/socket.texi   |   28 ++++-----
>  manual/startup.texi  |    8 +--
>  manual/stdio.texi    |   85 ++++++++++++++-------------
>  manual/string.texi   |   24 ++++----
>  manual/sysinfo.texi  |   52 ++++++++---------
>  manual/syslog.texi   |    4 +-
>  manual/terminal.texi |   18 +++---
>  manual/threads.texi  |    2 +-
>  manual/time.texi     |   40 ++++++-------
>  manual/users.texi    |   35 ++++++-----
>  40 files changed, 504 insertions(+), 505 deletions(-)
> 

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Carlos O'Donell]

On 05/16/2016 09:58 PM, ricaljasan wrote:
> Ping.
> 
> Is it preferred that I ping each of these separately? 01-04 have been
> reviewed, but 03 requested further review, so there are 34 still pending
> review (and all are New and undelegated in patchwork, fwiw).

Just pinging the set is fine. I have this on my radar to review too, so the
ping reminds me :-)

-- 
Cheers,
Carlos.

[PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

ping^2

01-09 have been reviewed, 03 still requires additional review.

Also, 01 & 02 have been merged, per mike (thanks! I think... :), but
their status in patchwork is still New and undelegated; unsure what
merging is if patchwork isn't Committed (all are still New).

Rical

On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
> Typos addressed in this patchset include obvious mistakes such as
> repeated repeated words, wrong case or tense, speling mistakes, and
> wrong variable names.  The occasional comma is also addressed, where
> its absence introduces ambiguity, or its presence disturbs the
> sentence.
> 
> Verified patches apply cleanly against latest master and that `make
> info|html|pdf' completes without error on x86_64.
> 
> ---
>  INSTALL              |    8 +--
>  manual/argp.texi     |   10 ++--
>  manual/arith.texi    |   16 ++---
>  manual/charset.texi  |   68 ++++++++++-----------
>  manual/conf.texi     |   10 ++--
>  manual/contrib.texi  |    6 +-
>  manual/crypt.texi    |    8 +--
>  manual/ctype.texi    |    4 +-
>  manual/debug.texi    |    4 +-
>  manual/errno.texi    |   22 +++----
>  manual/filesys.texi  |   42 ++++++-------
>  manual/getopt.texi   |   10 ++--
>  manual/install.texi  |    6 +-
>  manual/intro.texi    |    2 +-
>  manual/job.texi      |    2 +-
>  manual/lang.texi     |    4 +-
>  manual/llio.texi     |   78 ++++++++++++-------------
>  manual/locale.texi   |   16 ++---
>  manual/maint.texi    |    2 +-
>  manual/math.texi     |   36 ++++++------
>  manual/memory.texi   |   24 ++++----
>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>  manual/nss.texi      |   44 +++++++-------
>  manual/pattern.texi  |   24 ++++----
>  manual/probes.texi   |    4 +-
>  manual/process.texi  |    2 +-
>  manual/resource.texi |   52 ++++++++---------
>  manual/search.texi   |   36 ++++++------
>  manual/setjmp.texi   |    8 +--
>  manual/signal.texi   |    6 +-
>  manual/socket.texi   |   28 ++++-----
>  manual/startup.texi  |    8 +--
>  manual/stdio.texi    |   85 ++++++++++++++-------------
>  manual/string.texi   |   24 ++++----
>  manual/sysinfo.texi  |   52 ++++++++---------
>  manual/syslog.texi   |    4 +-
>  manual/terminal.texi |   18 +++---
>  manual/threads.texi  |    2 +-
>  manual/time.texi     |   40 ++++++-------
>  manual/users.texi    |   35 ++++++-----
>  40 files changed, 504 insertions(+), 505 deletions(-)
> 

[PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

ping^3

Current status:

  * 01-26 have been reviewed.
  * 01-02 have been merged.
  * 03 & 08 requested additional review.

The additional review in 03 is in regards to some variable names that
appear to have changed.  The reviewer will need to have the manual open
to the relevant section for context.  There were a few places where, for
example, in the description for function foo with a parameter bar-ptr,
the description refers to a parameter "bar", which not being the name of
a parameter for the function, seemed to be a typo.

The additional review in 08 is in regards to the use of besides vs.
beside.  Beside is a preposition meaning next to and is usually used for
spatial descriptions; besides, while also a preposition, can be an
adverb and usually introduces some new information (i.e., in addition
to).  At least, that's how my grammar usually goes, so it would be nice
to have someone else look over those changes.

Thank you,
Rical

On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
> Typos addressed in this patchset include obvious mistakes such as
> repeated repeated words, wrong case or tense, speling mistakes, and
> wrong variable names.  The occasional comma is also addressed, where
> its absence introduces ambiguity, or its presence disturbs the
> sentence.
> 
> Verified patches apply cleanly against latest master and that `make
> info|html|pdf' completes without error on x86_64.
> 
> ---
>  INSTALL              |    8 +--
>  manual/argp.texi     |   10 ++--
>  manual/arith.texi    |   16 ++---
>  manual/charset.texi  |   68 ++++++++++-----------
>  manual/conf.texi     |   10 ++--
>  manual/contrib.texi  |    6 +-
>  manual/crypt.texi    |    8 +--
>  manual/ctype.texi    |    4 +-
>  manual/debug.texi    |    4 +-
>  manual/errno.texi    |   22 +++----
>  manual/filesys.texi  |   42 ++++++-------
>  manual/getopt.texi   |   10 ++--
>  manual/install.texi  |    6 +-
>  manual/intro.texi    |    2 +-
>  manual/job.texi      |    2 +-
>  manual/lang.texi     |    4 +-
>  manual/llio.texi     |   78 ++++++++++++-------------
>  manual/locale.texi   |   16 ++---
>  manual/maint.texi    |    2 +-
>  manual/math.texi     |   36 ++++++------
>  manual/memory.texi   |   24 ++++----
>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>  manual/nss.texi      |   44 +++++++-------
>  manual/pattern.texi  |   24 ++++----
>  manual/probes.texi   |    4 +-
>  manual/process.texi  |    2 +-
>  manual/resource.texi |   52 ++++++++---------
>  manual/search.texi   |   36 ++++++------
>  manual/setjmp.texi   |    8 +--
>  manual/signal.texi   |    6 +-
>  manual/socket.texi   |   28 ++++-----
>  manual/startup.texi  |    8 +--
>  manual/stdio.texi    |   85 ++++++++++++++-------------
>  manual/string.texi   |   24 ++++----
>  manual/sysinfo.texi  |   52 ++++++++---------
>  manual/syslog.texi   |    4 +-
>  manual/terminal.texi |   18 +++---
>  manual/threads.texi  |    2 +-
>  manual/time.texi     |   40 ++++++-------
>  manual/users.texi    |   35 ++++++-----
>  40 files changed, 504 insertions(+), 505 deletions(-)
> 

[PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

ping^4

On 06/06/2016 01:03 AM, Rical Jasan wrote:
> ping^3
> 
> Current status:
> 
>   * 01-26 have been reviewed.
>   * 01-02 have been merged.
>   * 03 & 08 requested additional review.
> 
> The additional review in 03 is in regards to some variable names that
> appear to have changed.  The reviewer will need to have the manual open
> to the relevant section for context.  There were a few places where, for
> example, in the description for function foo with a parameter bar-ptr,
> the description refers to a parameter "bar", which not being the name of
> a parameter for the function, seemed to be a typo.
> 
> The additional review in 08 is in regards to the use of besides vs.
> beside.  Beside is a preposition meaning next to and is usually used for
> spatial descriptions; besides, while also a preposition, can be an
> adverb and usually introduces some new information (i.e., in addition
> to).  At least, that's how my grammar usually goes, so it would be nice
> to have someone else look over those changes.
> 
> Thank you,
> Rical
> 
> On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
>> Typos addressed in this patchset include obvious mistakes such as
>> repeated repeated words, wrong case or tense, speling mistakes, and
>> wrong variable names.  The occasional comma is also addressed, where
>> its absence introduces ambiguity, or its presence disturbs the
>> sentence.
>>
>> Verified patches apply cleanly against latest master and that `make
>> info|html|pdf' completes without error on x86_64.
>>
>> ---
>>  INSTALL              |    8 +--
>>  manual/argp.texi     |   10 ++--
>>  manual/arith.texi    |   16 ++---
>>  manual/charset.texi  |   68 ++++++++++-----------
>>  manual/conf.texi     |   10 ++--
>>  manual/contrib.texi  |    6 +-
>>  manual/crypt.texi    |    8 +--
>>  manual/ctype.texi    |    4 +-
>>  manual/debug.texi    |    4 +-
>>  manual/errno.texi    |   22 +++----
>>  manual/filesys.texi  |   42 ++++++-------
>>  manual/getopt.texi   |   10 ++--
>>  manual/install.texi  |    6 +-
>>  manual/intro.texi    |    2 +-
>>  manual/job.texi      |    2 +-
>>  manual/lang.texi     |    4 +-
>>  manual/llio.texi     |   78 ++++++++++++-------------
>>  manual/locale.texi   |   16 ++---
>>  manual/maint.texi    |    2 +-
>>  manual/math.texi     |   36 ++++++------
>>  manual/memory.texi   |   24 ++++----
>>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>>  manual/nss.texi      |   44 +++++++-------
>>  manual/pattern.texi  |   24 ++++----
>>  manual/probes.texi   |    4 +-
>>  manual/process.texi  |    2 +-
>>  manual/resource.texi |   52 ++++++++---------
>>  manual/search.texi   |   36 ++++++------
>>  manual/setjmp.texi   |    8 +--
>>  manual/signal.texi   |    6 +-
>>  manual/socket.texi   |   28 ++++-----
>>  manual/startup.texi  |    8 +--
>>  manual/stdio.texi    |   85 ++++++++++++++-------------
>>  manual/string.texi   |   24 ++++----
>>  manual/sysinfo.texi  |   52 ++++++++---------
>>  manual/syslog.texi   |    4 +-
>>  manual/terminal.texi |   18 +++---
>>  manual/threads.texi  |    2 +-
>>  manual/time.texi     |   40 ++++++-------
>>  manual/users.texi    |   35 ++++++-----
>>  40 files changed, 504 insertions(+), 505 deletions(-)
>>
> 

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

i noticed that all of your patches have broken From lines in them
which means it's a pain to `git am` them.  please make sure your
gitconfig settings are correct.
$ cd
$ git config user.name 'Rical Jasan'
-mie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

On 06/15/2016 09:35 PM, Mike Frysinger wrote:
> i noticed that all of your patches have broken From lines in them
> which means it's a pain to `git am` them.  please make sure your
> gitconfig settings are correct.
> $ cd
> $ git config user.name 'Rical Jasan'
> -mie

I noticed that too when I got the digest and they all said from
ricaljasan; already fixed.

Thanks for working on these!

Rical

[PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

ping^5

All have been reviewed by cjl.  01-10 have been merged by mike.

An errant From: seems to have caused issues with `git am'.  I can resend
the rest if preferred.

On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
...
> ---
>  INSTALL              |    8 +--
>  manual/argp.texi     |   10 ++--
>  manual/arith.texi    |   16 ++---
>  manual/charset.texi  |   68 ++++++++++-----------
>  manual/conf.texi     |   10 ++--
>  manual/contrib.texi  |    6 +-
>  manual/crypt.texi    |    8 +--
>  manual/ctype.texi    |    4 +-
>  manual/debug.texi    |    4 +-
>  manual/errno.texi    |   22 +++----
>  manual/filesys.texi  |   42 ++++++-------
>  manual/getopt.texi   |   10 ++--
>  manual/install.texi  |    6 +-
>  manual/intro.texi    |    2 +-
>  manual/job.texi      |    2 +-
>  manual/lang.texi     |    4 +-
>  manual/llio.texi     |   78 ++++++++++++-------------
>  manual/locale.texi   |   16 ++---
>  manual/maint.texi    |    2 +-
>  manual/math.texi     |   36 ++++++------
>  manual/memory.texi   |   24 ++++----
>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>  manual/nss.texi      |   44 +++++++-------
>  manual/pattern.texi  |   24 ++++----
>  manual/probes.texi   |    4 +-
>  manual/process.texi  |    2 +-
>  manual/resource.texi |   52 ++++++++---------
>  manual/search.texi   |   36 ++++++------
>  manual/setjmp.texi   |    8 +--
>  manual/signal.texi   |    6 +-
>  manual/socket.texi   |   28 ++++-----
>  manual/startup.texi  |    8 +--
>  manual/stdio.texi    |   85 ++++++++++++++-------------
>  manual/string.texi   |   24 ++++----
>  manual/sysinfo.texi  |   52 ++++++++---------
>  manual/syslog.texi   |    4 +-
>  manual/terminal.texi |   18 +++---
>  manual/threads.texi  |    2 +-
>  manual/time.texi     |   40 ++++++-------
>  manual/users.texi    |   35 ++++++-----
>  40 files changed, 504 insertions(+), 505 deletions(-)

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Chris Leonard]

Some more commits would be appreciated on these reviewed patches.

TIA

cjl

On Sun, Jul 10, 2016 at 10:22 PM, Rical Jasan <ricaljasan@pacific.net> wrote:
> ping^5
>
> All have been reviewed by cjl.  01-10 have been merged by mike.
>
> An errant From: seems to have caused issues with `git am'.  I can resend
> the rest if preferred.
>
> On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
> ...
>> ---
>>  INSTALL              |    8 +--
>>  manual/argp.texi     |   10 ++--
>>  manual/arith.texi    |   16 ++---
>>  manual/charset.texi  |   68 ++++++++++-----------
>>  manual/conf.texi     |   10 ++--
>>  manual/contrib.texi  |    6 +-
>>  manual/crypt.texi    |    8 +--
>>  manual/ctype.texi    |    4 +-
>>  manual/debug.texi    |    4 +-
>>  manual/errno.texi    |   22 +++----
>>  manual/filesys.texi  |   42 ++++++-------
>>  manual/getopt.texi   |   10 ++--
>>  manual/install.texi  |    6 +-
>>  manual/intro.texi    |    2 +-
>>  manual/job.texi      |    2 +-
>>  manual/lang.texi     |    4 +-
>>  manual/llio.texi     |   78 ++++++++++++-------------
>>  manual/locale.texi   |   16 ++---
>>  manual/maint.texi    |    2 +-
>>  manual/math.texi     |   36 ++++++------
>>  manual/memory.texi   |   24 ++++----
>>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>>  manual/nss.texi      |   44 +++++++-------
>>  manual/pattern.texi  |   24 ++++----
>>  manual/probes.texi   |    4 +-
>>  manual/process.texi  |    2 +-
>>  manual/resource.texi |   52 ++++++++---------
>>  manual/search.texi   |   36 ++++++------
>>  manual/setjmp.texi   |    8 +--
>>  manual/signal.texi   |    6 +-
>>  manual/socket.texi   |   28 ++++-----
>>  manual/startup.texi  |    8 +--
>>  manual/stdio.texi    |   85 ++++++++++++++-------------
>>  manual/string.texi   |   24 ++++----
>>  manual/sysinfo.texi  |   52 ++++++++---------
>>  manual/syslog.texi   |    4 +-
>>  manual/terminal.texi |   18 +++---
>>  manual/threads.texi  |    2 +-
>>  manual/time.texi     |   40 ++++++-------
>>  manual/users.texi    |   35 ++++++-----
>>  40 files changed, 504 insertions(+), 505 deletions(-)
>

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

On 08/18/2016 06:33 AM, Chris Leonard wrote:
> Some more commits would be appreciated on these reviewed patches.
> 
> TIA
> 
> cjl

Hear, hear!  Thank you; I've been meaning to re-ping now that 2.25 is open.

Rical

> On Sun, Jul 10, 2016 at 10:22 PM, Rical Jasan <ricaljasan@pacific.net> wrote:
>> ping^5
>>
>> All have been reviewed by cjl.  01-10 have been merged by mike.
>>
>> An errant From: seems to have caused issues with `git am'.  I can resend
>> the rest if preferred.
>>
>> On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
>> ...
>>> ---
>>>  INSTALL              |    8 +--
>>>  manual/argp.texi     |   10 ++--
>>>  manual/arith.texi    |   16 ++---
>>>  manual/charset.texi  |   68 ++++++++++-----------
>>>  manual/conf.texi     |   10 ++--
>>>  manual/contrib.texi  |    6 +-
>>>  manual/crypt.texi    |    8 +--
>>>  manual/ctype.texi    |    4 +-
>>>  manual/debug.texi    |    4 +-
>>>  manual/errno.texi    |   22 +++----
>>>  manual/filesys.texi  |   42 ++++++-------
>>>  manual/getopt.texi   |   10 ++--
>>>  manual/install.texi  |    6 +-
>>>  manual/intro.texi    |    2 +-
>>>  manual/job.texi      |    2 +-
>>>  manual/lang.texi     |    4 +-
>>>  manual/llio.texi     |   78 ++++++++++++-------------
>>>  manual/locale.texi   |   16 ++---
>>>  manual/maint.texi    |    2 +-
>>>  manual/math.texi     |   36 ++++++------
>>>  manual/memory.texi   |   24 ++++----
>>>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>>>  manual/nss.texi      |   44 +++++++-------
>>>  manual/pattern.texi  |   24 ++++----
>>>  manual/probes.texi   |    4 +-
>>>  manual/process.texi  |    2 +-
>>>  manual/resource.texi |   52 ++++++++---------
>>>  manual/search.texi   |   36 ++++++------
>>>  manual/setjmp.texi   |    8 +--
>>>  manual/signal.texi   |    6 +-
>>>  manual/socket.texi   |   28 ++++-----
>>>  manual/startup.texi  |    8 +--
>>>  manual/stdio.texi    |   85 ++++++++++++++-------------
>>>  manual/string.texi   |   24 ++++----
>>>  manual/sysinfo.texi  |   52 ++++++++---------
>>>  manual/syslog.texi   |    4 +-
>>>  manual/terminal.texi |   18 +++---
>>>  manual/threads.texi  |    2 +-
>>>  manual/time.texi     |   40 ++++++-------
>>>  manual/users.texi    |   35 ++++++-----
>>>  40 files changed, 504 insertions(+), 505 deletions(-)

[PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

ping^6

I know they're trivial, but it would be nice if these weren't left
half-committed.

On 07/10/2016 07:22 PM, Rical Jasan wrote:
> ping^5
> 
> All have been reviewed by cjl.  01-10 have been merged by mike.
> 
> An errant From: seems to have caused issues with `git am'.  I can resend
> the rest if preferred.
> 
> On 05/06/2016 12:54 AM, ricaljasan@pacific.net wrote:
> ...
>> ---
>>  INSTALL              |    8 +--
>>  manual/argp.texi     |   10 ++--
>>  manual/arith.texi    |   16 ++---
>>  manual/charset.texi  |   68 ++++++++++-----------
>>  manual/conf.texi     |   10 ++--
>>  manual/contrib.texi  |    6 +-
>>  manual/crypt.texi    |    8 +--
>>  manual/ctype.texi    |    4 +-
>>  manual/debug.texi    |    4 +-
>>  manual/errno.texi    |   22 +++----
>>  manual/filesys.texi  |   42 ++++++-------
>>  manual/getopt.texi   |   10 ++--
>>  manual/install.texi  |    6 +-
>>  manual/intro.texi    |    2 +-
>>  manual/job.texi      |    2 +-
>>  manual/lang.texi     |    4 +-
>>  manual/llio.texi     |   78 ++++++++++++-------------
>>  manual/locale.texi   |   16 ++---
>>  manual/maint.texi    |    2 +-
>>  manual/math.texi     |   36 ++++++------
>>  manual/memory.texi   |   24 ++++----
>>  manual/message.texi  |  159 +++++++++++++++++++++++++-------------------------
>>  manual/nss.texi      |   44 +++++++-------
>>  manual/pattern.texi  |   24 ++++----
>>  manual/probes.texi   |    4 +-
>>  manual/process.texi  |    2 +-
>>  manual/resource.texi |   52 ++++++++---------
>>  manual/search.texi   |   36 ++++++------
>>  manual/setjmp.texi   |    8 +--
>>  manual/signal.texi   |    6 +-
>>  manual/socket.texi   |   28 ++++-----
>>  manual/startup.texi  |    8 +--
>>  manual/stdio.texi    |   85 ++++++++++++++-------------
>>  manual/string.texi   |   24 ++++----
>>  manual/sysinfo.texi  |   52 ++++++++---------
>>  manual/syslog.texi   |    4 +-
>>  manual/terminal.texi |   18 +++---
>>  manual/threads.texi  |    2 +-
>>  manual/time.texi     |   40 ++++++-------
>>  manual/users.texi    |   35 ++++++-----
>>  40 files changed, 504 insertions(+), 505 deletions(-)

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Siddhesh Poyarekar]

On Thursday 06 October 2016 02:40 AM, Rical Jasan wrote:
> ping^6
> 
> I know they're trivial, but it would be nice if these weren't left
> half-committed.

I'll look at them later today.

Siddhesh

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Siddhesh Poyarekar]

On Thursday 06 October 2016 11:20 AM, Siddhesh Poyarekar wrote:
> On Thursday 06 October 2016 02:40 AM, Rical Jasan wrote:
>> ping^6
>>
>> I know they're trivial, but it would be nice if these weren't left
>> half-committed.
> 
> I'll look at them later today.

I have pushed all of the patches.  26/37 had issues with merging because
a couple of hunks had changed, but I fixed those up before pushing them.

Thank you for your attention to detail and apologies for the delay!

Siddhesh

Re: [PING] [PATCH 00/37] Manual typos: Overview

[Rical Jasan]

On 10/06/2016 12:13 AM, Siddhesh Poyarekar wrote:
> On Thursday 06 October 2016 11:20 AM, Siddhesh Poyarekar wrote:
>> On Thursday 06 October 2016 02:40 AM, Rical Jasan wrote:
>>> ping^6
>>>
>>> I know they're trivial, but it would be nice if these weren't left
>>> half-committed.
>>
>> I'll look at them later today.
> 
> I have pushed all of the patches.  26/37 had issues with merging because
> a couple of hunks had changed, but I fixed those up before pushing them.
> 
> Thank you for your attention to detail and apologies for the delay!

Thank you!

Rical