From patchwork Sat May 27 16:43:18 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Paul Pluzhnikov X-Patchwork-Id: 1786764 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=sourceware.org (client-ip=2620:52:3:1:0:246e:9693:128c; helo=sourceware.org; envelope-from=libc-alpha-bounces+incoming=patchwork.ozlabs.org@sourceware.org; receiver=) Authentication-Results: legolas.ozlabs.org; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=x9z0sDda; dkim-atps=neutral Received: from sourceware.org (server2.sourceware.org [IPv6:2620:52:3:1:0:246e:9693:128c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4QT70N44Zdz20Q1 for ; Sun, 28 May 2023 02:43:47 +1000 (AEST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 576BF3858289 for ; Sat, 27 May 2023 16:43:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 576BF3858289 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1685205824; bh=LAZbugKPTeIsf0C3v9e13nHkITrmcKpO9DI4Xf+aCI0=; h=Date:Subject:To:Cc:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=x9z0sDdaVCmqnsdYskKaAVdVHJyoyeuKabVloaD/li8O0PEPXlmNmjKbNZR8L/VGp SeafY8AlBlPHlsJGs8x53Aau3kUMJS4kd3HiVqwV4eTjl+LJ15l5RIUzWzdbY/uZFJ wM+QRJEHitOcWJ79Fy27TZZGN/Ix9IzibKV7FcTc= X-Original-To: libc-alpha@sourceware.org Delivered-To: libc-alpha@sourceware.org Received: from mail-pg1-x549.google.com (mail-pg1-x549.google.com [IPv6:2607:f8b0:4864:20::549]) by sourceware.org (Postfix) with ESMTPS id C747F3858C50 for ; Sat, 27 May 2023 16:43:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C747F3858C50 Received: by mail-pg1-x549.google.com with SMTP id 41be03b00d2f7-51b743d592dso1184301a12.0 for ; Sat, 27 May 2023 09:43:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685205806; x=1687797806; h=cc:to:from:subject:message-id:mime-version:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=LAZbugKPTeIsf0C3v9e13nHkITrmcKpO9DI4Xf+aCI0=; b=QdfkMt8J7L3UFOazZD6uUX2zy9mW3OwtR6O6bVxVvcBTl6Ao4AOpOVgWoMH34pDThC IeBRS3FsZ80AMdkb4g8TD2lgJG791qCwXPh56+RwVedAIqa6byPvwemCtnb8x3Wx2IRH IWQ68VlEVOydZIVwyEqWec+4KIdr3BHhx7BfKvtGN/+u06DZzFZxJF4pZZRkZsI20iXC SA+GIuSjcLBvFoSJowf428Z3uDmozuw7oT5W1xKE5hGAXPCu5dtp7N9/0Afh6l5ATmJX U0OPTnS2cXALgxUOj1CBsW8FVikb2NMoTGcE7E5+P/rTiiutaup8ojJdZNF/HNJiyVGO i+0Q== X-Gm-Message-State: AC+VfDzP5vRcjv2XvsR+U/81S43rmroxUHnHj1dFMNLy6tLkepCEAB29 tYe69XWSniBFsr6VrHmO6RTmtjfAZE/BWpA6EywPnVRbqyRhpRFiAF4QXNm69eHZkCv0z/nwHeG Zi5FUmpD1Co0UK1+hAGS/AUN4ACISVByRjx4xwiSUDUv7Fdkw41XDaPPDpBG3FItBYePW8VZYL0 yTmjo= X-Google-Smtp-Source: ACHHUZ4grbTuFpaHDemqfbI1P5FC2EcwrFzDrUVTOxpUkF8X7Y7ONC61WYQNUDRiQcCTBf6OgcOaUSqFd3lwPnKnkA== X-Received: from elbrus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:12e9]) (user=ppluzhnikov job=sendgmr) by 2002:a63:1556:0:b0:51a:7d6a:65c9 with SMTP id 22-20020a631556000000b0051a7d6a65c9mr433564pgv.6.1685205805825; Sat, 27 May 2023 09:43:25 -0700 (PDT) Date: Sat, 27 May 2023 16:43:18 +0000 Mime-Version: 1.0 X-Mailer: git-send-email 2.41.0.rc0.172.g3f132b7071-goog Message-ID: <20230527164318.4117590-1-ppluzhnikov@google.com> Subject: [PATCH] Fix misspellings in manual/ -- BZ 25337 To: libc-alpha@sourceware.org Cc: Paul Pluzhnikov X-Spam-Status: No, score=-19.9 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE, USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Patchwork-Original-From: Paul Pluzhnikov via Libc-alpha From: Paul Pluzhnikov Reply-To: Paul Pluzhnikov Errors-To: libc-alpha-bounces+incoming=patchwork.ozlabs.org@sourceware.org Sender: "Libc-alpha" --- manual/README.pretty-printers | 2 +- manual/arith.texi | 2 +- manual/install.texi | 2 +- manual/intro.texi | 4 ++-- manual/ipc.texi | 2 +- manual/llio.texi | 2 +- manual/memory.texi | 2 +- manual/pattern.texi | 2 +- manual/process.texi | 2 +- manual/socket.texi | 2 +- manual/threads.texi | 2 +- manual/time.texi | 2 +- manual/tunables.texi | 4 ++-- 13 files changed, 15 insertions(+), 15 deletions(-) diff --git a/manual/README.pretty-printers b/manual/README.pretty-printers index a2ba89843c..a696406ce5 100644 --- a/manual/README.pretty-printers +++ b/manual/README.pretty-printers @@ -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. diff --git a/manual/arith.texi b/manual/arith.texi index 002621f11e..fa7110e992 100644 --- a/manual/arith.texi +++ b/manual/arith.texi @@ -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 diff --git a/manual/install.texi b/manual/install.texi index a1f01a1ec0..a44a552d1f 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -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 diff --git a/manual/intro.texi b/manual/intro.texi index 9bdfd09c83..ff43c5a7fb 100644 --- a/manual/intro.texi +++ b/manual/intro.texi @@ -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) diff --git a/manual/ipc.texi b/manual/ipc.texi index be74664af9..6a6e5ad410 100644 --- a/manual/ipc.texi +++ b/manual/ipc.texi @@ -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 diff --git a/manual/llio.texi b/manual/llio.texi index 1b801ee817..0b61d491f5 100644 --- a/manual/llio.texi +++ b/manual/llio.texi @@ -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 diff --git a/manual/memory.texi b/manual/memory.texi index 8952ff2bfa..5781a64f35 100644 --- a/manual/memory.texi +++ b/manual/memory.texi @@ -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 diff --git a/manual/pattern.texi b/manual/pattern.texi index 4fa4c25525..250fa1e265 100644 --- a/manual/pattern.texi +++ b/manual/pattern.texi @@ -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 diff --git a/manual/process.texi b/manual/process.texi index 9307379194..c8413a5a58 100644 --- a/manual/process.texi +++ b/manual/process.texi @@ -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. diff --git a/manual/socket.texi b/manual/socket.texi index 68c930b552..f0e35d9e13 100644 --- a/manual/socket.texi +++ b/manual/socket.texi @@ -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. diff --git a/manual/threads.texi b/manual/threads.texi index a721c7f464..e5544ff3da 100644 --- a/manual/threads.texi +++ b/manual/threads.texi @@ -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 diff --git a/manual/time.texi b/manual/time.texi index 0c7a942b4c..3aabdc4953 100644 --- a/manual/time.texi +++ b/manual/time.texi @@ -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}. diff --git a/manual/tunables.texi b/manual/tunables.texi index 130f94b2bc..4ca0e42a11 100644 --- a/manual/tunables.texi +++ b/manual/tunables.texi @@ -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