diff --git a/ChangeLog.1 b/ChangeLog.1
index f897fa56..f5dd4a55 100644
--- a/ChangeLog.1
+++ b/ChangeLog.1
@@ -1794,7 +1794,7 @@ along with this program. If not, see .
and delete TOO_MANY_COMMAND. Turn these into an enum and declare
main_command_option of this enum type, to replace command_mode,
which was an int, everywhere.
- * tar.c (decode_options): Initialise main_command_option.
+ * tar.c (decode_options): Initialize main_command_option.
(set_main_command_option): New function to replace
SET_COMMAND_MODE. Diagnostic ambiguous command as soon as seen.
However, be forgiving if command has merely been repeated.
@@ -1896,7 +1896,7 @@ along with this program. If not, see .
(process_rawdata, process_dumpdir): Adjusted.
* compare.c: Remove different as a global variable, it is useless.
- (diff_sparse_files): Make different a local variable, reinitialise
+ (diff_sparse_files): Make different a local variable, reinitialize
it on each call. Otherwise, after any error elsewhere, all sparse
files were always and falsely reported as erroneous.
Reported by James E. Carpenter and Tim Towers.
@@ -1975,7 +1975,7 @@ along with this program. If not, see .
appropriately, using initializers when natural, and moving them
closer to the blocks where they are used.
- A bit of reorganisation in the sources:
+ A bit of reorganization in the sources:
* common.h: New file, for holding all GNU tar specific definitions,
which were previously held in tar.h.
* tar.h: Now limited to the archive format description only.
@@ -5866,7 +5866,7 @@ Previous releases by Jay Fenlason (hack@ai.mit.edu)
* Makefile.am ($(TESTS)): Depend on preset.
* version.sh (PATH): Adjust for multi-line --version output.
* preset.in (LANG, LANGUAGE): Export them, so gzip does not
- localise its own output.
+ localize its own output.
(echo_n, echo_c): Define from the result of echo configuration.
* after: Handle echo with newline suppressed.
diff --git a/NEWS b/NEWS
index fa95ffd2..5018327b 100644
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-GNU tar NEWS - User visible changes. 2026-08-20
+GNU tar NEWS - User visible changes. 2026-08-21
Please send GNU tar bug reports to
version 1.35.90 (git)
@@ -219,7 +219,7 @@ Bug introduced with the addition of that option in 1.28.
* Support for zstd compression
New option '--zstd' instructs tar to use zstd as compression program.
-When listing, extractng and comparing, zstd compressed archives are
+When listing, extracting and comparing, zstd compressed archives are
recognized automatically.
When '-a' option is in effect, zstd compression is selected if the
destination archive name ends in '.zst' or '.tzst'.
@@ -785,7 +785,7 @@ the following variables:
** Fix restoring files from backup (debian bug #508199).
** Correctly restore modes and permissions on existing directories.
** The --remove-files option removes files only if they were
-succesfully stored in the archive.
+successfully stored in the archive.
** Fix storing and listing of the volume labels in POSIX format.
** Improve algorithm for splitting long file names (ustar
format).
@@ -1130,8 +1130,8 @@ for example, while comparing 'tar cv' and 'tar tv' outputs.
as well as that about directories.
** The --checkpoint option takes an optional argument specifying the number
-of records between the two successive checkpoints. Optional dot
-starting the argument intructs tar to print dots instead of textual
+of records between the two successive checkpoints. An optional dot
+starting the argument instructs tar to print dots instead of textual
checkpoints.
** The --totals option can be used with any tar operation (previous versions
@@ -1245,7 +1245,7 @@ tar to refuse to extract files from standard input.
version 1.15 - Sergey Poznyakoff, 2004-12-20
-* Compressed archives are recognised automatically, it is no longer
+* Compressed archives are recognized automatically; it is no longer
necessary to specify -Z, -z, or -j options to read them. Thus, you can
now run 'tar tf archive.tar.gz'.
@@ -1488,7 +1488,7 @@ version 1.13.16 - Paul Eggert, 1999-12-13.
before extracting it. If the existing file is a symbolic link, the
link is removed and not the pointed-to file. There is one
exception: existing nonempty directories are not removed, nor are
- their ownerships or permissions extracted. This fixes some
+ their ownership or permissions extracted. This fixes some
longstanding security problems.
The new --overwrite option enables the old default behavior.
diff --git a/doc/recipes.texi b/doc/recipes.texi
index cfaae230..31dfea4e 100644
--- a/doc/recipes.texi
+++ b/doc/recipes.texi
@@ -53,7 +53,7 @@ $ @kbd{tar --directory sourcedir --create --file=- . \
@node intermediate directories
@appendixsec Restoring Intermediate Directories
-A common concern is how to extract permissions and ownerships of
+A common concern is how to extract permissions and ownership of
intermediate directories when extracting only selected members from
the archive. To illustrate this, consider the following archive:
@@ -90,7 +90,7 @@ permissions. The intermediate directories, however, are created with
the default permissions, current timestamp and owned by the current
user. This is because by the time @command{tar} has reached the requested file,
it had already skipped the entries for its parent directories, so it
-has no iformation about their ownership and modes.
+has no information about their ownership and modes.
To restore meta information about the intermediate directories,
you'll need to specify them explicitly in the command line and use the
diff --git a/doc/tar.texi b/doc/tar.texi
index f44d7b58..28f20c75 100644
--- a/doc/tar.texi
+++ b/doc/tar.texi
@@ -2528,7 +2528,7 @@ superuser privileges and can be a pain to manage.
During a @option{--create} operation, enables automatic compressed
format recognition based on the archive suffix. The effect of this
-option is cancelled by @option{--no-auto-compress}. @xref{gzip}.
+option is canceled by @option{--no-auto-compress}. @xref{gzip}.
@opsummary{backup}
@item --backup=@var{backup-type}
@@ -10388,7 +10388,7 @@ the numeric ids from the archive, ignoring the names.
This is useful in certain circumstances, when restoring a backup from
an emergency floppy with different passwd/group files for example.
-It is otherwise impossible to extract files with the right ownerships
+It is otherwise impossible to extract files with the right ownership
if the password file in use during the extraction does not match the
one belonging to the file system(s) being extracted. This occurs,
for example, if you are restoring your files after a major crash and
@@ -10680,7 +10680,7 @@ To force creation a @GNUTAR{} archive, use option
Starting from version 1.14 @GNUTAR{} features full support for
@acronym{POSIX.1-2001} archives.
-A @acronym{POSIX} conformant archive will be created if @command{tar}
+An archive conforming to @acronym{POSIX} will be created if @command{tar}
was given @option{--format=posix} (@option{--format=pax}) option. No
special option is required to read and extract from a @acronym{POSIX}
archive.
@@ -11427,7 +11427,7 @@ file name lengths. The binary and old @acronym{ASCII} formats have a maximum fi
length of 256, and the new @acronym{ASCII} and @acronym{CRC ASCII} formats have a max
file length of 1024. @acronym{GNU} @command{cpio} can read and write archives
with arbitrary file name lengths, but other @command{cpio} implementations
-may crash unexplainedly trying to read them.
+may crash trying to read them.
@command{tar} handles symbolic links in the form in which it comes in @acronym{BSD};
@command{cpio} doesn't handle symbolic links in the form in which it comes
@@ -11540,7 +11540,7 @@ the creation and manipulation of archives located on magnetic tape was
the original purpose of @command{tar}, it contains many features making
such manipulation easier.
-Archives are usually written on dismountable media---tape cartridges,
+Archives are usually written on mountable media---tape cartridges,
mag tapes, or floppy disks.
The amount of data a tape or disk holds depends not only on its size,
diff --git a/src/incremen.c b/src/incremen.c
index 8053283e..87e3b131 100644
--- a/src/incremen.c
+++ b/src/incremen.c
@@ -26,7 +26,7 @@
#include
#include "common.h"
-/* Incremental dump specialities. */
+/* Incremental dump specialties. */
/* Which child files to save under a directory. */
enum children
diff --git a/src/tar.h b/src/tar.h
index 54cd31f8..390f6b24 100644
--- a/src/tar.h
+++ b/src/tar.h
@@ -137,7 +137,7 @@ struct sparse_header
/* The old GNU format header conflicts with POSIX format in such a way that
POSIX archives may fool old GNU tar's, and POSIX tar's might well be
fooled by old GNU tar archives. An old GNU format header uses the space
- used by the prefix field in a POSIX header, and cumulates information
+ used by the prefix field in a POSIX header, and accumulates information
normally found in a GNU extra header. With an old GNU tar header, we
never see any POSIX header nor GNU extra header. Supplementary sparse
headers are allowed, however. */
diff --git a/src/xheader.c b/src/xheader.c
index 09d43995..25830cef 100644
--- a/src/xheader.c
+++ b/src/xheader.c
@@ -1697,7 +1697,7 @@ struct xhdr_tab const xhdr_tab[] = {
{ "GNU.sparse.size", sparse_size_coder, sparse_size_decoder,
XHDR_PROTECTED, false },
/* tar 1.14 - 1.15.1 keywords. Multiple instances of these appeared in 'x'
- headers, and each of them was meaningful. It confilcted with POSIX specs,
+ headers, and each of them was meaningful. It conflicted with POSIX specs,
which requires that "when extended header records conflict, the last one
given in the header shall take precedence." */
{ "GNU.sparse.offset", sparse_offset_coder, sparse_offset_decoder,
diff --git a/tests/dirrem01.at b/tests/dirrem01.at
index bc11c006..3d15abb9 100644
--- a/tests/dirrem01.at
+++ b/tests/dirrem01.at
@@ -26,7 +26,7 @@
# In case of files tar does not return TAREXIT_FAILURE, but instead
# it prints a warning and exits with TAREXIT_DIFFERS.
#
-# This test checks whether this behaviour is mimicked for directories, too.
+# This test checks whether this behavior is mimicked for directories, too.
#
# Notes:
# 1. This file is based on 'filerem01.at', which is the test-case for
diff --git a/tests/extrac22.at b/tests/extrac22.at
index efa78d0e..c5cffd09 100644
--- a/tests/extrac22.at
+++ b/tests/extrac22.at
@@ -18,7 +18,7 @@
AT_SETUP([delay-directory-restore on reversed ordering])
-# The --delay-directory-resore option worked incorrectly on archives with
+# The --delay-directory-restore option worked incorrectly on archives with
# reversed member ordering (which was documented, anyway). This is illustrated
# in
# http://lists.gnu.org/archive/html/bug-tar/2019-03/msg00022.html
@@ -57,4 +57,4 @@ tar -x -p --delay-directory-restore -C restore -f a.tar
],
[0],
[])
-AT_CLEANUP
\ No newline at end of file
+AT_CLEANUP
diff --git a/tests/incremental.at b/tests/incremental.at
index 7ccb75fe..c361ffda 100644
--- a/tests/incremental.at
+++ b/tests/incremental.at
@@ -38,7 +38,7 @@ ls -l structure/file >/dev/null
# in that backup are the same, the file will be backed up again when an
# incremental backup is done, because the incremental backup backs up
# files created "on or after" the initial backup time. Without the sleep
-# command, behaviour of tar becomes variable, depending whether the system
+# command, behavior of tar becomes variable, depending whether the system
# clock ticked over to the next second between creating the file and
# backing it up.
sleep 1
diff --git a/tests/options03.at b/tests/options03.at
index f44c22c9..8eb7b986 100644
--- a/tests/options03.at
+++ b/tests/options03.at
@@ -23,7 +23,7 @@ AT_KEYWORDS([options options03])
# Check whether string values are passed correctly through the
# TAR_OPTIONS environment variable. In tar 1.29 the stored values
-# were inadvertenlty freedm which caused TAR_OPTION to malfunction.
+# were inadvertently freed, which caused TAR_OPTION to malfunction.
# Reported by: Jan Larres
# References: <20160906072153.c75tga556ti5sgk2@majutsushi.net>,
# http://lists.gnu.org/archive/html/bug-tar/2016-09/msg00005.html
diff --git a/tests/recurs02.at b/tests/recurs02.at
index 8c17ee8d..b2b6b531 100644
--- a/tests/recurs02.at
+++ b/tests/recurs02.at
@@ -19,7 +19,7 @@
# along with this program. If not, see .
# Description: Test interaction of --recursion and --no-recursion options.
-# Each of them remains in effect until cancelled by the next occurrence
+# Each of them remains in effect until canceled by the next occurrence
# of its counterpart. This didn't work in v.1.27.1 and was fixed by
# commit 2bd9c153.
# Reported by: Kai