@@ -140,7 +140,7 @@ its name to the 'tests-printers-libs' variable in your submodule's Makefile.
Known issues
------------
-* Pretty printers are inherently coupled to the code they're targetting, thus
+* Pretty printers are inherently coupled to the code they're targeting, thus
any changes to the target code must also update the corresponding printers.
On the plus side, the printer code itself may serve as a kind of documentation
for the target code.
@@ -111,7 +111,7 @@ minimum possible values for each integer data type. The macro names
follow these examples: @code{INT32_MAX}, @code{UINT8_MAX},
@code{INT_FAST32_MIN}, @code{INT_LEAST64_MIN}, @code{UINTMAX_MAX},
@code{INTMAX_MAX}, @code{INTMAX_MIN}. Note that there are no macros for
-unsigned integer minima. These are always zero. Similiarly, there
+unsigned integer minima. These are always zero. Similarly, there
are macros such as @code{INTMAX_WIDTH} for the width of these types.
Those macros for integer type widths come from TS 18661-1:2014.
@cindex maximum possible integer
@@ -509,7 +509,7 @@ build @theglibc{}:
@item
GNU @code{make} 4.0 or newer
-As of relase time, GNU @code{make} 4.4 is the newest verified to work
+As of release time, GNU @code{make} 4.4 is the newest verified to work
to build @theglibc{}.
@item
@@ -1294,14 +1294,14 @@ this manual.
@c Pattern Matching (10)
@c Input/Output Overview (11)
@c Input/Output on Streams (12)
-@c Low-level Input/Ooutput (13)
+@c Low-level Input/Output (13)
@c File System Interface (14)
@c Pipes and FIFOs (15)
@c Sockets (16)
@c Low-Level Terminal Interface (17)
@c Syslog (18)
@c Mathematics (19)
-@c Aritmetic Functions (20)
+@c Arithmetic Functions (20)
@c Date and Time (21)
@c Non-Local Exist (23)
@c Signal Handling (24)
@@ -62,7 +62,7 @@ by @theglibc{}.
@safety{@prelim{}@mtsafe{}@asunsafe{@asuinit{}}@acunsafe{@acuinit{}}}
@c pthread_once asuinit
@c
-@c We are AC-Unsafe becuase we use pthread_once to initialize
+@c We are AC-Unsafe because we use pthread_once to initialize
@c a global variable that holds the location of the mounted
@c shmfs on Linux.
@end deftypefun
@@ -320,7 +320,7 @@ is used.
@item ENOMEM
Either there is not enough memory for the operation, or the process is
-out of address space. It can only happnes when @code{CLOSE_RANGE_UNSHARED}
+out of address space. It can only happen when @code{CLOSE_RANGE_UNSHARED}
flag is used.
@item EMFILE
@@ -1746,7 +1746,7 @@ are no problems with the code, all allocated memory was freed
afterwards.
If we call @code{mtrace} on the example trace given above we would get a
-different outout:
+different output:
@example
drepper$ mtrace errlog
@@ -258,7 +258,7 @@ containing a given name.
The @code{glob} function reads the @code{struct dirent} members listed
above and makes a copy of the file name in the @code{d_name} member
immediately after the @code{gl_readdir} callback function returns.
-Future invocations of any of the callback functions may dealloacte or
+Future invocations of any of the callback functions may deallocate or
reuse the buffer. It is the responsibility of the caller of the
@code{glob} function to allocate and deallocate the buffer, around the
call to @code{glob} or using the callback functions. For example, an
@@ -254,7 +254,7 @@ It is declared in the header file @file{unistd.h}.
@c handlers, and unlocks the internal lock. The child bumps the fork
@c generation, sets the thread-local pid, resets cpu clocks, initializes
@c the robust mutex list, the stream locks, the IO_list lock, the dynamic
-@c loader lock, runs the child handlers, reseting ref counters to 1, and
+@c loader lock, runs the child handlers, resetting ref counters to 1, and
@c initializes the fork lock. These are all safe, unless atfork
@c handlers themselves are unsafe.
The @code{fork} function creates a new process.
@@ -821,7 +821,7 @@ here. The address is stored in network byte order.
This combines the IPv6 traffic class and flow label values, as found
in the IPv6 header. This field is stored in network byte order. Only
the 28 lower bits (of the number in network byte order) are used; the
-remainig bits must be zero. The lower 20 bits are the flow label, and
+remaining bits must be zero. The lower 20 bits are the flow label, and
bits 20 to 27 are the the traffic class. Typically, this field is
zero.
@@ -945,7 +945,7 @@ undefined behavior.) In any case, an application must not write to
@code{__libc_single_threaded} even if it has joined the last
application-created thread because future versions of @theglibc{} may
create background threads after the first thread has been created, and
-the application has no way of knowning that these threads are present.
+the application has no way of knowing that these threads are present.
@node Restartable Sequences
@subsubsection Restartable Sequences
@@ -503,7 +503,7 @@ Systems may support more than just these two clocks.
@deftypefun int clock_gettime (clockid_t @var{clock}, struct timespec *@var{ts})
@standards{POSIX.1, time.h}
-Get the current time accoding to the clock identified by @var{clock},
+Get the current time according to the clock identified by @var{clock},
storing it as seconds and nanoseconds in @code{*@var{ts}}.
@xref{Time Types}, for a description of @code{struct timespec}.
@@ -446,7 +446,7 @@ stack cache exceeds this size, unused thread stacks are returned to
the kernel, to bring the cache size below this limit.
The value is measured in bytes. The default is @samp{41943040}
-(fourty mibibytes).
+(forty mibibytes).
@end deftp
@deftp Tunable glibc.pthread.rseq
@@ -625,7 +625,7 @@ and the process manage memory.
@deftp Tunable glibc.mem.tagging
If the hardware supports memory tagging, this tunable can be used to
control the way @theglibc{} uses this feature. At present this is only
-supported on AArch64 systems with the MTE extention; it is ignored for
+supported on AArch64 systems with the MTE extension; it is ignored for
all other systems.
This tunable takes a value between 0 and 255 and acts as a bitmask