diff --git a/ACKNOWLEDGEMENTS b/ACKNOWLEDGEMENTS
index 4442aec33..21e6e23b0 100644
--- a/ACKNOWLEDGEMENTS
+++ b/ACKNOWLEDGEMENTS
@@ -42,7 +42,7 @@ for the Squashfs kernel code.
 
 Vito Di Leo sent a patch extending Mksquashfs to support regex filters.
 While his patched worked, it unfortunately made it easy to make Mksquashfs
-perform unpredictably with poorly choosen regex expressions.  It, however,
+perform unpredictably with poorly chosen regex expressions.  It, however,
 encouraged myself to add support for wildcard pattern matching and regex
 filters in a different way.
 
diff --git a/ACTIONS-README b/ACTIONS-README
index d25adcb0c..2dbb9e1ff 100644
--- a/ACTIONS-README
+++ b/ACTIONS-README
@@ -32,7 +32,7 @@ and vice-versa:
 
 An action consists of two parts, separated by an "@".  The action to
 be executed is placed before the @, and one or more tests are
-placed afer the @.  If the action or tests has an argument, it is
+placed after the @.  If the action or tests has an argument, it is
 given in brackets.  Brackets are optional if no argument is needed,
 e.g.
 
@@ -580,7 +580,7 @@ solid state media, seeking is not such a major issue anymore.
 Tell Mksquashfs not to use tail-end packing for the files matching the
 exppression.
 
-For obvious reasons this should be used in conjuction with the global
+For obvious reasons this should be used in conjunction with the global
 Mksquashfs option -always-use-fragments.  By default tail-ends are not
 packed into fragments.
 
@@ -662,7 +662,7 @@ Adds the read and write permissions to both user and group.
 
 3. chmod(u=rw,go=r)
 
-Sets the permissions to rw-r--r--, which is eqivalent to
+Sets the permissions to rw-r--r--, which is equivalent to
 
 4. chmod(644)
 
@@ -767,9 +767,9 @@ Otherwise it can be added to all files.
 The extended attribute value by default will be treated as binary (i.e. an
 uninterpreted byte sequence), but it can be prefixed with 0s, where it will be
 treated as base64 encoded, or prefixed with 0x, where it will be treated as
-hexidecimal.
+hexadecimal.
 
-Obviously using base64 or hexidecimal allows values to be used that cannot be
+Obviously using base64 or hexadecimal allows values to be used that cannot be
 entered on the command line such as non-printable characters etc.  But it
 renders the string non-human readable.  To keep readability and to allow
 non-printable characters to be entered, the 0t prefix is supported.  This
diff --git a/INSTALL b/INSTALL
index 4941bf17e..b106d9d73 100644
--- a/INSTALL
+++ b/INSTALL
@@ -30,7 +30,7 @@ to /usr/local/bin by typing "sudo make install".
 2.1 Compressors supported
 
 By default the Makefile is configured to build Mksquashfs and Unsquashfs
-with GZIP suppport.  Read the Makefile in squashfs-tools for instructions on
+with GZIP support.  Read the Makefile in squashfs-tools for instructions on
 building LZO, LZ4, XZ and ZSTD compression support.
 
 2.2 Extended attribute support (XATTRs)
diff --git a/README-4.5 b/README-4.5
index 86a076f0b..027272c11 100644
--- a/README-4.5
+++ b/README-4.5
@@ -140,7 +140,7 @@ of files within fragments.  Specifically, it creates a specialised fragment
 called "cfiles" which packs files matching the wildcard name "*.[ch]".
 
 It also creates another specialised fragment called "ofiles" which packs
-files matching the wilcard name "*.o".
+files matching the wildcard name "*.o".
 
 Producing specialised fragments which only pack files which match a range
 of tests, can produce better compression and/or I/O performance as
@@ -353,7 +353,7 @@ Mksquashfs now allows you to pipe the set of files to be added to the
 filesystem to standard in (stdin), if the -cpiostyle option is given.
 
 As with cpio, directories are not recursively scanned, and their contents
-added.  Evey file to be added to the filesystem must be explicitly
+added.  Every file to be added to the filesystem must be explicitly
 specified.
 
 Typically the list of files to be added will be produced via find, or a
@@ -365,7 +365,7 @@ For example
 
 Will create an image containing everything in squashfs-tools and its
 sub-directories.  Note, "-" is given as the source pathname in Mksquashfs,
-and indicates no commmand line sources.
+and indicates no command line sources.
 
 and the following will add just the files ending in .c, .h and .o.
 
@@ -412,7 +412,7 @@ higher the percentage, the greater the throughput of the reader thread.
 
 The Pseudo file definitions previously supported did not allow the time
 of the file to be set.  New extended pseudo file definitions have been added
-which take a <time> timestamp.  These are distinquished from the previous
+which take a <time> timestamp.  These are distinguished from the previous
 definitions by using an upper-case type character.  For example the "D"
 definition is identical to the previous "d" definition (it creates
 a directory), but it takes a <time> timestamp.
@@ -459,7 +459,7 @@ Hard Link) Pseudo definition has been added named 'l'.
 README l /home/phillip/latest-version/README
 
 Will create a reference to "/home/phillip/latest-version/README",
-and obviously the timestamp/mode and owership will be used.
+and obviously the timestamp/mode and ownership will be used.
 
 The definition also be used to create additional references to
 files within the source directories.  For instance if "phillip/latest/README"
@@ -589,7 +589,7 @@ in a similar way to "cp -L".  But this is dangerous, and can cause
 Unsquashfs to produce output which does not match the input Squashfs
 filesystem, which is something Unsquashfs should never do.
 
-The reason for this is whereas "cp -L" is derefencing the *input*,
+The reason for this is whereas "cp -L" is dereferencing the *input*,
 Unsquashfs is dereferencing the *output*.  If a filesystem has a real
 filename, say
 
@@ -612,7 +612,7 @@ file, and two copies of directory "c".
 
 Superficially the output may look the same, but, it may not work the same,
 and obviously edits to the one hello_world file will not get reflected in
-the other copies.  Any option that can be accidently or maliciously used
+the other copies.  Any option that can be accidentally or maliciously used
 to produce such an output is too dangerous to be added.
 
 Unsquashfs solves the problem in an equivalent way, but which does not alter
@@ -645,8 +645,8 @@ with the sub-set of files matched by the exclude file(s) excluded.
 
 Often you want to output the filesystem where you're only interested in
 some files, which is where extract files are useful.  But equally, you
-often want to to output the entire filesystem, but, with some unwanted
-files removed.  An example of this, perhaps, is where you've inadvertantly,
+often want to output the entire filesystem, but, with some unwanted
+files removed.  An example of this, perhaps, is where you've inadvertently,
 archived binaries (.o files etc.) and you're only interested in extracting
 the source code.
 
@@ -784,5 +784,5 @@ This will change the ownership to uid 1234, and change the name of
 =================
 
 Mksquashfs 4.5 generates 4.0 filesystems.  These filesystems are fully
-compatible/interchangable with filesystems generated by Mksquashfs 4.x and are
+compatible/interchangeable with filesystems generated by Mksquashfs 4.x and are
 mountable on 2.6.29 and later kernels.
diff --git a/README-4.5.1 b/README-4.5.1
index 374704a49..56337aa8f 100644
--- a/README-4.5.1
+++ b/README-4.5.1
@@ -142,7 +142,7 @@ of files within fragments.  Specifically, it creates a specialised fragment
 called "cfiles" which packs files matching the wildcard name "*.[ch]".
 
 It also creates another specialised fragment called "ofiles" which packs
-files matching the wilcard name "*.o".
+files matching the wildcard name "*.o".
 
 Producing specialised fragments which only pack files which match a range
 of tests, can produce better compression and/or I/O performance as
@@ -355,7 +355,7 @@ Mksquashfs now allows you to pipe the set of files to be added to the
 filesystem to standard in (stdin), if the -cpiostyle option is given.
 
 As with cpio, directories are not recursively scanned, and their contents
-added.  Evey file to be added to the filesystem must be explicitly
+added.  Every file to be added to the filesystem must be explicitly
 specified.
 
 Typically the list of files to be added will be produced via find, or a
@@ -367,7 +367,7 @@ For example
 
 Will create an image containing everything in squashfs-tools and its
 sub-directories.  Note, "-" is given as the source pathname in Mksquashfs,
-and indicates no commmand line sources.
+and indicates no command line sources.
 
 and the following will add just the files ending in .c, .h and .o.
 
@@ -414,7 +414,7 @@ higher the percentage, the greater the throughput of the reader thread.
 
 The Pseudo file definitions previously supported did not allow the time
 of the file to be set.  New extended pseudo file definitions have been added
-which take a <time> timestamp.  These are distinquished from the previous
+which take a <time> timestamp.  These are distinguished from the previous
 definitions by using an upper-case type character.  For example the "D"
 definition is identical to the previous "d" definition (it creates
 a directory), but it takes a <time> timestamp.
@@ -461,7 +461,7 @@ Hard Link) Pseudo definition has been added named 'l'.
 README l /home/phillip/latest-version/README
 
 Will create a reference to "/home/phillip/latest-version/README",
-and obviously the timestamp/mode and owership will be used.
+and obviously the timestamp/mode and ownership will be used.
 
 The definition also be used to create additional references to
 files within the source directories.  For instance if "phillip/latest/README"
@@ -591,7 +591,7 @@ in a similar way to "cp -L".  But this is dangerous, and can cause
 Unsquashfs to produce output which does not match the input Squashfs
 filesystem, which is something Unsquashfs should never do.
 
-The reason for this is whereas "cp -L" is derefencing the *input*,
+The reason for this is whereas "cp -L" is dereferencing the *input*,
 Unsquashfs is dereferencing the *output*.  If a filesystem has a real
 filename, say
 
@@ -614,7 +614,7 @@ file, and two copies of directory "c".
 
 Superficially the output may look the same, but, it may not work the same,
 and obviously edits to the one hello_world file will not get reflected in
-the other copies.  Any option that can be accidently or maliciously used
+the other copies.  Any option that can be accidentally or maliciously used
 to produce such an output is too dangerous to be added.
 
 Unsquashfs solves the problem in an equivalent way, but which does not alter
@@ -647,8 +647,8 @@ with the sub-set of files matched by the exclude file(s) excluded.
 
 Often you want to output the filesystem where you're only interested in
 some files, which is where extract files are useful.  But equally, you
-often want to to output the entire filesystem, but, with some unwanted
-files removed.  An example of this, perhaps, is where you've inadvertantly,
+often want to output the entire filesystem, but, with some unwanted
+files removed.  An example of this, perhaps, is where you've inadvertently,
 archived binaries (.o files etc.) and you're only interested in extracting
 the source code.
 
@@ -786,5 +786,5 @@ This will change the ownership to uid 1234, and change the name of
 =================
 
 Mksquashfs 4.5 generates 4.0 filesystems.  These filesystems are fully
-compatible/interchangable with filesystems generated by Mksquashfs 4.x and are
+compatible/interchangeable with filesystems generated by Mksquashfs 4.x and are
 mountable on 2.6.29 and later kernels.
diff --git a/README-4.6 b/README-4.6
index c031152ce..e29d986e6 100644
--- a/README-4.6
+++ b/README-4.6
@@ -160,7 +160,7 @@ files.
 
 The -xattrs-include option instead specifies a regular expression (regex)
 which includes any extended attribute that matches, and removes anything
-that does't match.
+that doesn't match.
 
 Examples:
 
@@ -194,9 +194,9 @@ all files.
 The extended attribute value by default will be treated as binary (i.e. an
 uninterpreted byte sequence), but it can be prefixed with 0s, where it will be
 treated as base64 encoded, or prefixed with 0x, where it will be treated as
-hexidecimal.
+hexadecimal.
 
-Obviously using base64 or hexidecimal allows values to be used that cannot be
+Obviously using base64 or hexadecimal allows values to be used that cannot be
 entered on the command line such as non-printable characters etc.  But it
 renders the string non-human readable.  To keep readability and to allow
 non-printable characters to be entered, the 0t prefix is supported.  This
@@ -310,7 +310,7 @@ extract that:
 
 % unsquashfs -pf - image.sqsh foobar | mksquashfs - new.sqsh -pf -
 
-If you had inadvertantly stored binary ".o" files, you can remove them by
+If you had inadvertently stored binary ".o" files, you can remove them by
 using the new "non-anchored" Unsquashfs exclude file functionality:
 
 % unsquashfs -excludes -pf - image.sqsh "... *.o" | mksquashfs - new.sqsh -pf -
diff --git a/README-4.6.1 b/README-4.6.1
index a259db342..9e3d5fa50 100644
--- a/README-4.6.1
+++ b/README-4.6.1
@@ -172,7 +172,7 @@ files.
 
 The -xattrs-include option instead specifies a regular expression (regex)
 which includes any extended attribute that matches, and removes anything
-that does't match.
+that doesn't match.
 
 Examples:
 
@@ -206,9 +206,9 @@ all files.
 The extended attribute value by default will be treated as binary (i.e. an
 uninterpreted byte sequence), but it can be prefixed with 0s, where it will be
 treated as base64 encoded, or prefixed with 0x, where it will be treated as
-hexidecimal.
+hexadecimal.
 
-Obviously using base64 or hexidecimal allows values to be used that cannot be
+Obviously using base64 or hexadecimal allows values to be used that cannot be
 entered on the command line such as non-printable characters etc.  But it
 renders the string non-human readable.  To keep readability and to allow
 non-printable characters to be entered, the 0t prefix is supported.  This
@@ -322,7 +322,7 @@ extract that:
 
 % unsquashfs -pf - image.sqsh foobar | mksquashfs - new.sqsh -pf -
 
-If you had inadvertantly stored binary ".o" files, you can remove them by
+If you had inadvertently stored binary ".o" files, you can remove them by
 using the new "non-anchored" Unsquashfs exclude file functionality:
 
 % unsquashfs -excludes -pf - image.sqsh "... *.o" | mksquashfs - new.sqsh -pf -
diff --git a/RELEASE-READMEs/DONATIONS b/RELEASE-READMEs/DONATIONS
index b4653bb19..007bfd3dc 100644
--- a/RELEASE-READMEs/DONATIONS
+++ b/RELEASE-READMEs/DONATIONS
@@ -2,7 +2,7 @@ Help sponsor Squashfs development!
 
 Maintaining and improving Squashfs is a lot of work, but Squashfs is one of
 the only widely used Linux file systems that has no company backing.  Squashfs
-development is funded soley by the author, partially supported by donations
+development is funded solely by the author, partially supported by donations
 from companies and individuals that want to improve Squashfs for themselves
 and others.
 
diff --git a/RELEASE-READMEs/PERFORMANCE.README b/RELEASE-READMEs/PERFORMANCE.README
index 20c282797..ebc6bfa81 100644
--- a/RELEASE-READMEs/PERFORMANCE.README
+++ b/RELEASE-READMEs/PERFORMANCE.README
@@ -13,7 +13,7 @@ liveCD filesystem from the Damn Small Linux liveCD (release 0.8.4).
 The Ubuntu liveCD filesystem was used to test filesystem performance
 from CDROM and hard disk for Zisofs, Cloop, Squashfs 2.0 and Squashfs2.1.
 CRAMFS filesystem performance could not be tested for this filesystem
-bacause it exceeds the maximum supported size of CRAMFS.  To test
+because it exceeds the maximum supported size of CRAMFS.  To test
 CRAMFS performance against Squashfs, the liveCD filesystem from
 Damn Small Linux was used.
 
diff --git a/TECHNICAL-INFO b/TECHNICAL-INFO
index a5cc4915a..3326aca46 100644
--- a/TECHNICAL-INFO
+++ b/TECHNICAL-INFO
@@ -273,7 +273,7 @@ or if it is stored out of line (in which case the value field stores a
 reference to where the actual value is stored).  This allows large values
 to be stored out of line improving scanning and lookup performance and it
 also allows values to be de-duplicated, the value being stored once, and
-all other occurences holding an out of line reference to that value.
+all other occurrences holding an out of line reference to that value.
 
 The xattr lists are packed into compressed 8K metadata blocks.
 To reduce overhead in inodes, rather than storing the on-disk
diff --git a/USAGE b/USAGE
index f14cf2103..a68c69630 100644
--- a/USAGE
+++ b/USAGE
@@ -133,7 +133,7 @@ for more information.
 
 Note: both SOURCE_DATE_EPOCH and the command line options cannot
 be used at the same time.  They are different ways to do the same thing,
-and both have FORCE sematics which mean they can't be over-ridden
+and both have FORCE semantics which mean they can't be over-ridden
 elsewhere (otherwise it would defeat the purpose).
 
 1.1.5 -not-reproducible
@@ -587,7 +587,7 @@ either by name (i.e. "root") or by number.
 The -e and -ef options allow files/directories to be specified which are
 excluded from the output filesystem.  The -e option takes the exclude
 files/directories from the command line, the -ef option takes the
-exlude files/directories from the specified exclude file, one file/directory
+exclude files/directories from the specified exclude file, one file/directory
 per line.
 
 Two styles of exclude file matching are supported: basic exclude matching, and
@@ -683,7 +683,7 @@ being generated, i.e.
 %mksquashfs / /tmp/root.sqsh -e proc /tmp/root.sqsh
 
 Multiple -ef options can be specified on the command line, and the -ef
-option can be used in conjuction with the -e option.
+option can be used in conjunction with the -e option.
 
 3.6 Appending to squashfs filesystems
 -------------------------------------
@@ -762,14 +762,14 @@ requiring root access.
 Mksquashfs 4.1 added support for "dynamic pseudo files" and a modify operation.
 Dynamic pseudo files allow files to be dynamically created when Mksquashfs
 is run, their contents being the result of running a command or piece of
-shell script.  The modifiy operation allows the mode/uid/gid of an existing
+shell script.  The modify operation allows the mode/uid/gid of an existing
 file in the source filesystem to be modified.
 
 Mksquashfs 4.4 adds support for Symbolic links.
 
 Two Mksquashfs options are supported, -p allows one pseudo file to be specified
 on the command line, and -pf allows a pseudo file to be specified containing a
-list of pseduo definitions, one per line.
+list of pseudo definitions, one per line.
 
 3.8.1. Creating a dynamic file
 ------------------------------
@@ -1271,7 +1271,7 @@ or if it is stored out of line (in which case the value field stores a
 reference to where the actual value is stored).  This allows large values
 to be stored out of line improving scanning and lookup performance and it
 also allows values to be de-duplicated, the value being stored once, and
-all other occurences holding an out of line reference to that value.
+all other occurrences holding an out of line reference to that value.
 
 The xattr lists are packed into compressed 8K metadata blocks.
 To reduce overhead in inodes, rather than storing the on-disk
diff --git a/USAGE-MKSQUASHFS-4.6 b/USAGE-MKSQUASHFS-4.6
index 37dab442e..7bc20f4b4 100644
--- a/USAGE-MKSQUASHFS-4.6
+++ b/USAGE-MKSQUASHFS-4.6
@@ -118,7 +118,7 @@ Filesystem extended attribute (xattrs) options:
 			binary (i.e. an uninterpreted byte sequence), but it can
 			be prefixed with 0s, where it will be treated as base64
 			encoded, or prefixed with 0x, where val will be treated
-			as hexidecimal.  Additionally it can be prefixed with
+			as hexadecimal.  Additionally it can be prefixed with
 			0t where this encoding is similar to binary encoding,
 			except backslashes are specially treated, and a
 			backslash followed by 3 octal digits can be used to
@@ -494,7 +494,7 @@ Mksquashfs allows you to pipe the set of files to be added to the filesystem to
 standard in (stdin), if the -cpiostyle option is given.
 
 As with cpio, directories are not recursively scanned and their contents added.
-Evey file to be added to the filesystem must be explicitly specified.
+Every file to be added to the filesystem must be explicitly specified.
 
 Typically the list of files to be added will be produced via find, or a similar
 utility.
@@ -505,7 +505,7 @@ For example
 
 Will create an image containing everything in squashfs-tools and its
 sub-directories.  Note, "-" is given as the source pathname in Mksquashfs, and
-indicates no commmand line sources.
+indicates no command line sources.
 
 The following will add just the files ending in .c, .h and .o.
 
@@ -538,7 +538,7 @@ either by name (i.e. "root") or by number.
 The -e and -ef options allow files/directories to be specified which are
 excluded from the output filesystem.  The -e option takes the exclude
 files/directories from the command line, the -ef option takes the
-exlude files/directories from the specified exclude file, one file/directory
+exclude files/directories from the specified exclude file, one file/directory
 per line.
 
 Two styles of exclude file matching are supported: basic exclude matching, and
@@ -640,7 +640,7 @@ files.  For example the regex '^user.' will remove all User extended attributes.
 
 The -xattrs-include option instead specifies a regular expression (regex)
 which includes any extended attribute that matches, and removes anything
-that does't match.  For example the regex '^user.' will only keep User
+that doesn't match.  For example the regex '^user.' will only keep User
 extended attributes and anything else will be removed.
 
 Mksquashfs also allows you to add extended attributes to files in the Squashfs
@@ -655,9 +655,9 @@ all files.
 The extended attribute value by default will be treated as binary (i.e. an
 uninterpreted byte sequence), but it can be prefixed with 0s, where it will be
 treated as base64 encoded, or prefixed with 0x, where it will be treated as
-hexidecimal.
+hexadecimal.
 
-Obviously using base64 or hexidecimal allows values to be used that cannot be
+Obviously using base64 or hexadecimal allows values to be used that cannot be
 entered on the command line such as non-printable characters etc.  But it
 renders the string non-human readable.  To keep readability and to allow
 non-printable characters to be entered, the 0t prefix is supported.  This
@@ -698,7 +698,7 @@ file in the source filesystem to be modified.
 
 Two Mksquashfs options are supported, -p allows one pseudo file to be specified
 on the command line, and -pf allows a pseudo file to be specified containing a
-list of pseduo definitions, one per line.
+list of pseudo definitions, one per line.
 
 9.1 CREATING A DYNAMIC FILE
 ---------------------------
@@ -830,7 +830,7 @@ Because this is a quite frequent use of the definition, an alternative faster
 README l /home/phillip/latest-version/README
 
 Will create a reference to "/home/phillip/latest-version/README",
-and obviously the timestamp/mode and owership will be used.
+and obviously the timestamp/mode and ownership will be used.
 
 The definition also be used to create additional references to
 files within the source directories.  For instance if "phillip/latest/README"
@@ -912,7 +912,7 @@ of the created file to be specified, and the files will be timestamped
 with the current time.
 
 Extended versions of the Pseudo file definitions are supported which
-take a <time> timestamp.  These are distinquished from the previous
+take a <time> timestamp.  These are distinguished from the previous
 definitions by using an upper-case type character.  For example the "D"
 definition is identical to the "d" definition, but it takes a <time>
 timestamp.
@@ -1026,7 +1026,7 @@ within fragments.  Specifically, it creates a specialised fragment called
 "cfiles" which packs files matching the wildcard name "*.[ch]".
 
 It also creates another specialised fragment called "ofiles" which packs files
-matching the wilcard name "*.o".
+matching the wildcard name "*.o".
 
 Producing specialised fragments which only pack files which match a range of
 tests, can produce better compression and/or I/O performance as it can optimise
diff --git a/USAGE-SQFSTAR-4.6 b/USAGE-SQFSTAR-4.6
index 9b5f0e897..d1e0d431d 100644
--- a/USAGE-SQFSTAR-4.6
+++ b/USAGE-SQFSTAR-4.6
@@ -118,7 +118,7 @@ Filesystem extended attribute (xattrs) options:
 			binary (i.e. an uninterpreted byte sequence), but it can
 			be prefixed with 0s, where it will be treated as base64
 			encoded, or prefixed with 0x, where val will be treated
-			as hexidecimal.  Additionally it can be prefixed with
+			as hexadecimal.  Additionally it can be prefixed with
 			0t where this encoding is similar to binary encoding,
 			except backslashes are specially treated, and a
 			backslash followed by 3 octal digits can be used to
@@ -494,7 +494,7 @@ files.  For example the regex '^user.' will remove all User extended attributes.
 
 The -xattrs-include option instead specifies a regular expression (regex)
 which includes any extended attribute that matches, and removes anything
-that does't match.  For example the regex '^user.' will only keep User
+that doesn't match.  For example the regex '^user.' will only keep User
 extended attributes and anything else will be removed.
 
 Sqfstar also allows you to add extended attributes to files in the Squashfs
@@ -509,9 +509,9 @@ all files.
 The extended attribute value by default will be treated as binary (i.e. an
 uninterpreted byte sequence), but it can be prefixed with 0s, where it will be
 treated as base64 encoded, or prefixed with 0x, where it will be treated as
-hexidecimal.
+hexadecimal.
 
-Obviously using base64 or hexidecimal allows values to be used that cannot be
+Obviously using base64 or hexadecimal allows values to be used that cannot be
 entered on the command line such as non-printable characters etc.  But it
 renders the string non-human readable.  To keep readability and to allow
 non-printable characters to be entered, the 0t prefix is supported.  This
@@ -547,12 +547,12 @@ allows device nodes to be added to the filesystem without requiring root access.
 Pseudo files also support "dynamic pseudo files" and a modify operation.
 Dynamic pseudo files allow files to be dynamically created when Sqfstar
 is run, their contents being the result of running a command or piece of
-shell script.  The modifiy operation allows the mode/uid/gid of an existing
+shell script.  The modify operation allows the mode/uid/gid of an existing
 file in the source filesystem to be modified.
 
 Two Sqfstar options are supported, -p allows one pseudo file to be specified
 on the command line, and -pf allows a pseudo file to be specified containing a
-list of pseduo definitions, one per line.
+list of pseudo definitions, one per line.
 
 8.1 CREATING A DYNAMIC FILE
 ---------------------------
@@ -684,7 +684,7 @@ Because this is a quite frequent use of the definition, an alternative faster
 README l /home/phillip/latest-version/README
 
 Will create a reference to "/home/phillip/latest-version/README",
-and obviously the timestamp/mode and owership will be used.
+and obviously the timestamp/mode and ownership will be used.
 
 The definition also can be used to create additional references to files
 within the source directories.  For instance if "phillip/latest/README" was a
@@ -767,7 +767,7 @@ of the created file to be specified, and the files will be timestamped
 with the current time.
 
 Extended versions of the Pseudo file definitions are supported which
-take a <time> timestamp.  These are distinquished from the previous
+take a <time> timestamp.  These are distinguished from the previous
 definitions by using an upper-case type character.  For example the "D"
 definition is identical to the "d" definition, but it takes a <time>
 timestamp.
diff --git a/USAGE-UNSQUASHFS-4.6 b/USAGE-UNSQUASHFS-4.6
index 0f7dc0e73..f87f4cef2 100644
--- a/USAGE-UNSQUASHFS-4.6
+++ b/USAGE-UNSQUASHFS-4.6
@@ -219,7 +219,7 @@ sub-set of files matched by the exclude file(s) excluded.
 Often you want to output the filesystem where you're only interested in some
 files, which is where extract files are useful.  But equally, you often want to
 output the entire filesystem, but, with some unwanted files removed.  An example
-of this, perhaps, is where you've inadvertantly, archived binaries (.o files
+of this, perhaps, is where you've inadvertently, archived binaries (.o files
 etc.) and you're only interested in extracting the source code.
 
 In the above example, trying to remove the binaries (.o etc) when you've only
@@ -354,7 +354,7 @@ in a similar way to "cp -L".  But this is dangerous, and can cause
 Unsquashfs to produce output which does not match the input Squashfs
 filesystem, which is something Unsquashfs should never do.
 
-The reason for this is whereas "cp -L" is derefencing the *input*,
+The reason for this is whereas "cp -L" is dereferencing the *input*,
 Unsquashfs is dereferencing the *output*.  If a filesystem has a real
 filename, say
 
@@ -377,7 +377,7 @@ file, and two copies of directory "c".
 
 Superficially the output may look the same, but, it may not work the same,
 and obviously edits to the one hello_world file will not get reflected in
-the other copies.  Any option that can be accidently or maliciously used
+the other copies.  Any option that can be accidentally or maliciously used
 to produce such an output is too dangerous to be added.
 
 Unsquashfs solves the problem in an equivalent way, but which does not alter
diff --git a/generate-manpages/mksquashfs-manpage.sh b/generate-manpages/mksquashfs-manpage.sh
index 0c4aae1b6..3f0273307 100755
--- a/generate-manpages/mksquashfs-manpage.sh
+++ b/generate-manpages/mksquashfs-manpage.sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 # This script generates a manpage from the mksquashfs -help and -version
-# output, using help2man.  The script does various modfications to the
+# output, using help2man.  The script does various modifications to the
 # output from -help and -version, before passing it to help2man, to allow
 # it be successfully processed into a manpage by help2man.
 
diff --git a/generate-manpages/sqfscat-manpage.sh b/generate-manpages/sqfscat-manpage.sh
index 0bcf36996..6608e2037 100755
--- a/generate-manpages/sqfscat-manpage.sh
+++ b/generate-manpages/sqfscat-manpage.sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 # This script generates a manpage from the sqfscat -help and -version
-# output, using help2man.  The script does various modfications to the
+# output, using help2man.  The script does various modifications to the
 # output from -help and -version, before passing it to help2man, to allow
 # it be successfully processed into a manpage by help2man.
 
diff --git a/generate-manpages/sqfstar-manpage.sh b/generate-manpages/sqfstar-manpage.sh
index 850812ecb..d44dceb0f 100755
--- a/generate-manpages/sqfstar-manpage.sh
+++ b/generate-manpages/sqfstar-manpage.sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 # This script generates a manpage from the sqfstar -help and -version
-# output, using help2man.  The script does various modfications to the
+# output, using help2man.  The script does various modifications to the
 # output from -help and -version, before passing it to help2man, to allow
 # it be successfully processed into a manpage by help2man.
 
diff --git a/generate-manpages/unsquashfs-manpage.sh b/generate-manpages/unsquashfs-manpage.sh
index 4cc222eef..061bd457e 100755
--- a/generate-manpages/unsquashfs-manpage.sh
+++ b/generate-manpages/unsquashfs-manpage.sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 
 # This script generates a manpage from the unsquashfs -help and -version
-# output, using help2man.  The script does various modfications to the
+# output, using help2man.  The script does various modifications to the
 # output from -help and -version, before passing it to help2man, to allow
 # it be successfully processed into a manpage by help2man.
 
diff --git a/kernel/kernel-2.6/fs/squashfs/cache.c b/kernel/kernel-2.6/fs/squashfs/cache.c
index f29eda16d..6fc8cc66f 100644
--- a/kernel/kernel-2.6/fs/squashfs/cache.c
+++ b/kernel/kernel-2.6/fs/squashfs/cache.c
@@ -26,10 +26,10 @@
  * recently accessed data Squashfs uses two small metadata and fragment caches.
  *
  * This file implements a generic cache implementation used for both caches,
- * plus functions layered ontop of the generic cache implementation to
+ * plus functions layered on top of the generic cache implementation to
  * access the metadata and fragment caches.
  *
- * To avoid out of memory and fragmentation isssues with vmalloc the cache
+ * To avoid out of memory and fragmentation issues with vmalloc the cache
  * uses sequences of kmalloced PAGE_CACHE_SIZE buffers.
  *
  * It should be noted that the cache is not used for file datablocks, these
@@ -106,7 +106,7 @@ struct squashfs_cache_entry *squashfs_cache_get(struct super_block *sb,
 			entry = &cache->entry[i];
 
 			/*
-			 * Initialise choosen cache entry, and fill it in from
+			 * Initialise chosen cache entry, and fill it in from
 			 * disk.
 			 */
 			cache->unused--;
diff --git a/manpages/mksquashfs.1 b/manpages/mksquashfs.1
index 9d5cfff2a..fad0b92f7 100644
--- a/manpages/mksquashfs.1
+++ b/manpages/mksquashfs.1
@@ -176,7 +176,7 @@ exclude any xattr names matching REGEX.  REGEX is a POSIX regular expression, e.
 include any xattr names matching REGEX.  REGEX is a POSIX regular expression, e.g. \fB\-xattrs\-include\fR '^user.' includes xattrs from the user namespace.
 .TP
 \fB\-xattrs\-add\fR NAME=VAL
-add the xattr NAME with VAL to files.  If an user xattr it will be added to regular files and directories (see man 7 xattr).  Otherwise it will be added to all files.  VAL by default will be treated as binary (i.e. an uninterpreted byte sequence), but it can be prefixed with 0s, where it will be treated as base64 encoded, or prefixed with 0x, where val will be treated as hexidecimal.  Additionally it can be prefixed with 0t where this encoding is similar to binary encoding, except backslashes are specially treated, and a backslash followed by 3 octal digits can be used to encode any ASCII character, which obviously can be used to encode control codes.  The option can be repeated multiple times to add multiple xattrs.
+add the xattr NAME with VAL to files.  If an user xattr it will be added to regular files and directories (see man 7 xattr).  Otherwise it will be added to all files.  VAL by default will be treated as binary (i.e. an uninterpreted byte sequence), but it can be prefixed with 0s, where it will be treated as base64 encoded, or prefixed with 0x, where val will be treated as hexadecimal.  Additionally it can be prefixed with 0t where this encoding is similar to binary encoding, except backslashes are specially treated, and a backslash followed by 3 octal digits can be used to encode any ASCII character, which obviously can be used to encode control codes.  The option can be repeated multiple times to add multiple xattrs.
 .SS "Mksquashfs runtime options:"
 .TP
 \fB\-version\fR
diff --git a/manpages/sqfstar.1 b/manpages/sqfstar.1
index 35a47f08c..652a81897 100644
--- a/manpages/sqfstar.1
+++ b/manpages/sqfstar.1
@@ -151,7 +151,7 @@ exclude any xattr names matching REGEX.  REGEX is a POSIX regular expression, e.
 include any xattr names matching REGEX.  REGEX is a POSIX regular expression, e.g. \fB\-xattrs\-include\fR '^user.' includes xattrs from the user namespace.
 .TP
 \fB\-xattrs\-add\fR NAME=VAL
-add the xattr NAME with VAL to files.  If an user xattr it will be added to regular files and directories (see man 7 xattr).  Otherwise it will be added to all files.  VAL by default will be treated as binary (i.e. an uninterpreted byte sequence), but it can be prefixed with 0s, where it will be treated as base64 encoded, or prefixed with 0x, where val will be treated as hexidecimal.  Additionally it can be prefixed with 0t where this encoding is similar to binary encoding, except backslashes are specially treated, and a backslash followed by 3 octal digits can be used to encode any ASCII character, which obviously can be used to encode control codes.  The option can be repeated multiple times to add multiple xattrs.
+add the xattr NAME with VAL to files.  If an user xattr it will be added to regular files and directories (see man 7 xattr).  Otherwise it will be added to all files.  VAL by default will be treated as binary (i.e. an uninterpreted byte sequence), but it can be prefixed with 0s, where it will be treated as base64 encoded, or prefixed with 0x, where val will be treated as hexadecimal.  Additionally it can be prefixed with 0t where this encoding is similar to binary encoding, except backslashes are specially treated, and a backslash followed by 3 octal digits can be used to encode any ASCII character, which obviously can be used to encode control codes.  The option can be repeated multiple times to add multiple xattrs.
 .SS "Sqfstar runtime options:"
 .TP
 \fB\-version\fR
diff --git a/squashfs-tools/gzip_wrapper.c b/squashfs-tools/gzip_wrapper.c
index 965bc78cb..969e1b35c 100644
--- a/squashfs-tools/gzip_wrapper.c
+++ b/squashfs-tools/gzip_wrapper.c
@@ -219,7 +219,7 @@ static void *gzip_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden
  *
- * This function returns 0 on sucessful extraction of options, and
+ * This function returns 0 on successful extraction of options, and
  *			-1 on error
  */
 static int gzip_extract_options(int block_size, void *buffer, int size)
diff --git a/squashfs-tools/lz4_wrapper.c b/squashfs-tools/lz4_wrapper.c
index 2f8c2be95..7e7a3447b 100644
--- a/squashfs-tools/lz4_wrapper.c
+++ b/squashfs-tools/lz4_wrapper.c
@@ -95,8 +95,8 @@ static int lz4_options(char *argv[], int argc)
  * options
  *
  * Currently LZ4 always returns a comp_opts structure, with
- * the version indicating LZ4_LEGACY stream fomat.  This is to
- * easily accomodate changes in the kernel code to different
+ * the version indicating LZ4_LEGACY stream format.  This is to
+ * easily accommodate changes in the kernel code to different
  * stream formats 
  */
 static void *lz4_dump_options(int block_size, int *size)
@@ -129,7 +129,7 @@ static void *lz4_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden
  *
- * This function returns 0 on sucessful extraction of options, and
+ * This function returns 0 on successful extraction of options, and
  *			-1 on error
  */
 static int lz4_extract_options(int block_size, void *buffer, int size)
@@ -181,7 +181,7 @@ static int lz4_extract_options(int block_size, void *buffer, int size)
  * If this does happen, then this version of LZ4 will not be able to decode
  * the newer format.  So we need to check for this.
  *
- * This function returns 0 on sucessful checking of options, and
+ * This function returns 0 on successful checking of options, and
  *			-1 on error
  */
 static int lz4_check_options(int block_size, void *buffer, int size)
diff --git a/squashfs-tools/lzo_wrapper.c b/squashfs-tools/lzo_wrapper.c
index 633fad0bd..15eb3211b 100644
--- a/squashfs-tools/lzo_wrapper.c
+++ b/squashfs-tools/lzo_wrapper.c
@@ -205,7 +205,7 @@ static void *lzo_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden
  *
- * This function returns 0 on sucessful extraction of options, and
+ * This function returns 0 on successful extraction of options, and
  *			-1 on error
  */
 static int lzo_extract_options(int block_size, void *buffer, int size)
@@ -355,8 +355,8 @@ static int lzo_compress(void *strm, void *dest, void *src,  int size,
 	 * buffer space.  Normally in other compressor APIs they take
 	 * a destination buffer size, and overflows return an error.
 	 * With LZO it lacks a destination size and so we must output
-	 * to a temporary buffer large enough to accomodate any
-	 * result, and explictly check here for overflow
+	 * to a temporary buffer large enough to accommodate any
+	 * result, and explicitly check here for overflow
 	 */
 	if(compsize > block_size)
 		return 0;
diff --git a/squashfs-tools/merge_sort.h b/squashfs-tools/merge_sort.h
index 345942c26..b9d173970 100644
--- a/squashfs-tools/merge_sort.h
+++ b/squashfs-tools/merge_sort.h
@@ -29,7 +29,7 @@
  *
  * Qsort and other O(n log n) algorithms work well with arrays but not
  * linked lists.  Merge sort another O(n log n) sort algorithm on the other hand
- * is not ideal for arrays (as it needs an additonal n storage locations
+ * is not ideal for arrays (as it needs an additional n storage locations
  * as sorting is not done in place), but it is ideal for linked lists because
  * it doesn't require any extra storage,
  */ 
@@ -59,7 +59,7 @@ void FUNCTION_NAME(struct LIST_TYPE **head, int count) \
  \
 		/* \
 		 * Iterate through the linked list, merging adjacent sublists. \
-		 * On each interation l2 points to the next sublist pair to be \
+		 * On each interaction l2 points to the next sublist pair to be \
 		 * merged (if there's only one sublist left this is simply added \
 		 * to the output list) \
 		 */ \
diff --git a/squashfs-tools/mksquashfs.c b/squashfs-tools/mksquashfs.c
index d481c2517..8c613277f 100644
--- a/squashfs-tools/mksquashfs.c
+++ b/squashfs-tools/mksquashfs.c
@@ -93,7 +93,7 @@ int block_log;
 int no_fragments = FALSE;
 int always_use_fragments = FALSE;
 
-/* Are duplicates detected in fileystem ? */
+/* Are duplicates detected in filesystem ? */
 int duplicate_checking = TRUE;
 
 /* Are filesystems exportable via NFS? */
@@ -322,7 +322,7 @@ int fd;
 /* Variables used for appending */
 int appending = TRUE;
 
-/* restore orignal filesystem state if appending to existing filesystem is
+/* restore original filesystem state if appending to existing filesystem is
  * cancelled */
 char *sdata_cache, *sdirectory_data_cache, *sdirectory_compressed;
 long long sbytes, stotal_bytes;
@@ -806,7 +806,7 @@ static long long write_inodes()
 	}
 
 	start_bytes = get_and_inc_pos(inode_bytes);
-	write_destination(fd, start_bytes, inode_bytes,  inode_table);
+	write_destination(fd, start_bytes, inode_bytes, inode_table);
 
 	return start_bytes;
 }
@@ -4450,7 +4450,7 @@ static void dir_scan5(struct dir_info *dir)
  *
  * Qsort and other O(n log n) algorithms work well with arrays but not
  * linked lists.  Merge sort another O(n log n) sort algorithm on the other hand
- * is not ideal for arrays (as it needs an additonal n storage locations
+ * is not ideal for arrays (as it needs an additional n storage locations
  * as sorting is not done in place), but it is ideal for linked lists because
  * it doesn't require any extra storage,
  */ 
@@ -4823,7 +4823,7 @@ static struct dir_info *add_source(struct dir_info *sdir, char *source,
 		/*
 		 * Matching file.
 		 *
-		 * For tarstyle source handling (leaf directores are
+		 * For tarstyle source handling (leaf directories are
 		 * recursively descended)
 		 *
 		 * - If we're at the leaf of the source, then we either match
@@ -7121,7 +7121,7 @@ static int sqfstar(int argc, char *argv[])
 			 * the destination file as input, which
 			 * will result in an I/O loop */
 			if(stat(destination_file, &buf) == -1) {
-				/* disappered after creating? */
+				/* disappeared after creating? */
 				perror("Could not stat destination file");
 				exit(1);
 			}
@@ -7168,7 +7168,7 @@ static int sqfstar(int argc, char *argv[])
 	}
 
 	/*
-	 * process the exclude files - must be done afer destination file has
+	 * process the exclude files - must be done after destination file has
 	 * been possibly created
 	 */
 	for(i = 1; i < dest_index; i++) {
@@ -7213,7 +7213,7 @@ static int sqfstar(int argc, char *argv[])
 	/*
 	 * store any compressor specific options after the superblock,
 	 * and set the COMP_OPT flag to show that the filesystem has
-	 * compressor specfic options
+	 * compressor specific options
 	 */
 	if(comp_data) {
 		unsigned short c_byte = size | SQUASHFS_COMPRESSED_BIT;
@@ -7386,7 +7386,7 @@ int main(int argc, char *argv[])
 	 * any -X compressor specific options are passed to the
 	 * correct compressor.
 	 *
-	 * Also scan for -Xhelp and -help-comp specified on command line,
+	 * Also scan for -Xhelp specified on command line.
 	 */
 	for(j = i; j < argc; j++) {
 		struct compressor *prev_comp = comp;
@@ -7424,7 +7424,7 @@ int main(int argc, char *argv[])
 	/*
 	 * if no -comp option specified lookup default compressor.  Note the
 	 * Makefile ensures the default compressor has been built, and so we
-	 * don't need to to check for failure here
+	 * don't need to check for failure here
 	 */
 	if(comp == NULL)
 		comp = lookup_compressor(COMP_DEFAULT);
@@ -8146,7 +8146,7 @@ int main(int argc, char *argv[])
 
 	check_source_date_epoch();
 
-	/* If cpiostyle is set, then file names  will be read-in
+	/* If cpiostyle is set, then file names will be read-in
 	 * from standard in.  We do not expect to have any sources
 	 * specified on the command line */
 	if(cpiostyle && source)
@@ -8271,7 +8271,7 @@ int main(int argc, char *argv[])
 			 * the destination file as input, which
 			 * will result in an I/O loop */
 			if(stat(destination_file, &buf) == -1) {
-				/* disappered after creating? */
+				/* disappeared after creating? */
 				perror("Could not stat destination file");
 				exit(1);
 			}
@@ -8319,7 +8319,7 @@ int main(int argc, char *argv[])
 	}
 
 	/*
-	 * process the exclude files - must be done afer destination file has
+	 * process the exclude files - must be done after destination file has
 	 * been possibly created
 	 */
 	for(i = option_offset; i < argc; i++)
@@ -8346,7 +8346,7 @@ int main(int argc, char *argv[])
 				add_exclude(argv[i++]);
 	}
 
-	/* process the sort files - must be done afer the exclude files  */
+	/* process the sort files - must be done after the exclude files  */
 	for(i = option_offset; i < argc; i++)
 		if(strcmp(argv[i], "-sort") == 0) {
 			if(tarfile)
@@ -8418,7 +8418,7 @@ int main(int argc, char *argv[])
 		/*
 		 * store any compressor specific options after the superblock,
 		 * and set the COMP_OPT flag to show that the filesystem has
-		 * compressor specfic options
+		 * compressor specific options
 		 */
 		if(comp_data) {
 			unsigned short c_byte = size | SQUASHFS_COMPRESSED_BIT;
diff --git a/squashfs-tools/mksquashfs_help.c b/squashfs-tools/mksquashfs_help.c
index 35ce4245e..cfc2e08be 100644
--- a/squashfs-tools/mksquashfs_help.c
+++ b/squashfs-tools/mksquashfs_help.c
@@ -257,7 +257,7 @@ static char *mksquashfs_text[]={
 		"(i.e. an uninterpreted byte sequence), but it can be "
 		"prefixed with 0s, where it will be treated as base64 "
 		"encoded, or prefixed with 0x, where val will be treated as "
-		"hexidecimal.  Additionally it can be prefixed with 0t where "
+		"hexadecimal.  Additionally it can be prefixed with 0t where "
 		"this encoding is similar to binary encoding, except "
 		"backslashes are specially treated, and a backslash followed "
 		"by 3 octal digits can be used to encode any ASCII character, "
@@ -545,7 +545,7 @@ static char *sqfstar_text[]={
 		"all files.  <val> by default will be treated as binary (i.e. "
 		"an uninterpreted byte sequence), but it can be prefixed with "
 		"0s, where it will be treated as base64 encoded, or prefixed "
-		"with 0x, where val will be treated as hexidecimal.  "
+		"with 0x, where val will be treated as hexadecimal.  "
 		"Additionally it can be prefixed with 0t where this encoding "
 		"is similar to binary encoding, except backslashes are "
 		"specially treated, and a backslash followed by 3 octal digits "
diff --git a/squashfs-tools/print_pager.c b/squashfs-tools/print_pager.c
index 70b832389..2c767345b 100644
--- a/squashfs-tools/print_pager.c
+++ b/squashfs-tools/print_pager.c
@@ -279,7 +279,7 @@ FILE *exec_pager(pid_t *process)
 failed:
 	res = kill(child, SIGKILL);
 	if(res == -1)
-	ERROR("Error executing pager, kill failed\n");
+		ERROR("Error executing pager, kill failed\n");
 	close(pipefd[1]);
 	return NULL;
 }
diff --git a/squashfs-tools/progressbar.c b/squashfs-tools/progressbar.c
index 19ad807cb..124ecb1a5 100644
--- a/squashfs-tools/progressbar.c
+++ b/squashfs-tools/progressbar.c
@@ -41,7 +41,7 @@
 /* flag whether progressbar display is enabled or not */
 static int display_progress_bar = FALSE;
 
-/* flag whether the progress bar is temporarily disbled */
+/* flag whether the progress bar is temporarily disabled */
 static int temp_disabled = FALSE;
 
 /* flag whether to display full progress bar or just a percentage */
diff --git a/squashfs-tools/reader.c b/squashfs-tools/reader.c
index 2c8d89966..62dad15b2 100644
--- a/squashfs-tools/reader.c
+++ b/squashfs-tools/reader.c
@@ -179,7 +179,7 @@ static void reader_read_process(struct dir_ent *dir_ent)
 		/*
 		 * Update progress bar size.  This is done
 		 * on every block rather than waiting for all blocks to be
-		 * read incase write_file_process() is running in parallel
+		 * read in case write_file_process() is running in parallel
 		 * with this.  Otherwise the current progress bar position
 		 * may get ahead of the progress bar size.
 		 */
@@ -395,7 +395,7 @@ static int get_readahead(struct pseudo_file *file, long long current,
 				int buffer_offset = READAHEAD_OFFSET(buffer->start);
 
 				/*
-				 * Four posibilities:
+				 * Four possibilities:
 				 * 1. Wanted data is whole of buffer
 				 * 2. Wanted data is at start of buffer
 				 * 3. Wanted data is at end of buffer
diff --git a/squashfs-tools/sort.c b/squashfs-tools/sort.c
index d25f3e25f..15ffccf43 100644
--- a/squashfs-tools/sort.c
+++ b/squashfs-tools/sort.c
@@ -260,7 +260,7 @@ int read_sort_file(char *filename, int source, char *source_path[])
 
 		/*
 		 * if filename empty, then line was empty of anything but
-		 * whitespace or a backslash character.  Skip empy lines
+		 * whitespace or a backslash character.  Skip empty lines
 		 */
 		if(sort_filename[0] == '\0')
 			continue;
diff --git a/squashfs-tools/squashfs_swap.h b/squashfs-tools/squashfs_swap.h
index edaf029d9..7e005b370 100644
--- a/squashfs-tools/squashfs_swap.h
+++ b/squashfs-tools/squashfs_swap.h
@@ -24,7 +24,7 @@
  */
 
 /*
- * macros to convert each stucture from big endian to little endian
+ * macros to convert each structure from big endian to little endian
  */
 
 #include "endian_compat.h"
diff --git a/squashfs-tools/tar.c b/squashfs-tools/tar.c
index af4f1ea76..38921b978 100644
--- a/squashfs-tools/tar.c
+++ b/squashfs-tools/tar.c
@@ -340,7 +340,7 @@ static void fixup_tree(struct dir_info *dir)
 
 
 /*
- * Add source to the tardir directory hierachy.
+ * Add source to the tardir directory hierarchy.
  * Tarfile describes the tar file to be added.
  */
 static struct dir_info *add_tarfile(struct dir_info *sdir, char *source,
diff --git a/squashfs-tools/unsquashfs_xattr_system.c b/squashfs-tools/unsquashfs_xattr_system.c
index b5ba6fb73..1880b64a9 100644
--- a/squashfs-tools/unsquashfs_xattr_system.c
+++ b/squashfs-tools/unsquashfs_xattr_system.c
@@ -89,7 +89,7 @@ int write_xattr(char *pathname, unsigned int xattr)
 				if(errno == ENOTSUP) {
 					/*
 					 * If the destination filesystem cannot
-					 * suppport xattrs, print error, and
+					 * support xattrs, print error, and
 					 * disable xattr output as this error is
 					 * unlikely to go away, and printing
 					 * screenfulls of the same error message
@@ -114,10 +114,10 @@ int write_xattr(char *pathname, unsigned int xattr)
 					 * limits on the amount of xattr
 					 * data that can be stored per file
 					 * (typically one block or 4K), so
-					 * we shouldn't disable xattr ouput,
-					 * as the error may be restriced to one
+					 * we shouldn't disable xattr output,
+					 * as the error may be restricted to one
 					 * file only.  If we get a lot of these
-					 * then suppress the error messsage
+					 * then suppress the error message
 					 */
 					EXIT_UNSQUASH_IGNORE("write_xattr: failed to write "
 						"xattr %s for file %s because "
diff --git a/squashfs-tools/xattr.c b/squashfs-tools/xattr.c
index fb5e4afa7..cc57a5264 100644
--- a/squashfs-tools/xattr.c
+++ b/squashfs-tools/xattr.c
@@ -1073,7 +1073,7 @@ struct xattr_add *xattr_parse(char *str, char *pre, char *option)
 		entry->value = hex_decode(value, strlen(value), &size);
 		if(entry->value == NULL) {
 			ERROR("%sinvalid argument %s in %s option, because "
-				"invalid hexidecimal value\n", pre, str, option);
+				"invalid hexadecimal value\n", pre, str, option);
 			goto failed2;
 		}
 
diff --git a/squashfs-tools/xz_wrapper.c b/squashfs-tools/xz_wrapper.c
index 448978f5e..216002bbf 100644
--- a/squashfs-tools/xz_wrapper.c
+++ b/squashfs-tools/xz_wrapper.c
@@ -295,7 +295,7 @@ static void *xz_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden
  *
- * This function returns 0 on sucessful extraction of options, and
+ * This function returns 0 on successful extraction of options, and
  *			-1 on error
  */
 static int xz_extract_options(int block_size, void *buffer, int size)
diff --git a/squashfs-tools/xz_wrapper_extended.c b/squashfs-tools/xz_wrapper_extended.c
index 07e0af122..dbfd6855e 100644
--- a/squashfs-tools/xz_wrapper_extended.c
+++ b/squashfs-tools/xz_wrapper_extended.c
@@ -384,7 +384,7 @@ static void *xz_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden
  *
- * This function returns 0 on sucessful extraction of options, and
+ * This function returns 0 on successful extraction of options, and
  *			-1 on error
  */
 static int xz_extract_options(int block_size, void *buffer, int size)
diff --git a/squashfs-tools/zstd_wrapper.c b/squashfs-tools/zstd_wrapper.c
index ab5f3c24b..7b4be53e8 100644
--- a/squashfs-tools/zstd_wrapper.c
+++ b/squashfs-tools/zstd_wrapper.c
@@ -115,7 +115,7 @@ static void *zstd_dump_options(int block_size, int *size)
  * set the default options, this is to ensure any user supplied
  * -X options on the appending mksquashfs command line are over-ridden.
  *
- * This function returns 0 on sucessful extraction of options, and -1 on error.
+ * This function returns 0 on successful extraction of options, and -1 on error.
  */
 static int zstd_extract_options(int block_size, void *buffer, int size)
 {
@@ -206,7 +206,7 @@ static int zstd_compress(void *strm, void *dest, void *src, int size,
 	if (ZSTD_isError(res)) {
 		/* FIXME:
 		 * zstd does not expose stable error codes. The error enum may
-		 * change between versions. Until upstream zstd stablizes the
+		 * change between versions. Until upstream zstd stabilizes the
 		 * error codes, we have no way of knowing why the error occurs.
 		 * zstd shouldn't fail to compress any input unless there isn't
 		 * enough output space. We assume that is the cause and return