Fix typos (#313)

00DIST

@@ -1903,7 +1903,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 		possible.  PTX 4.4.4 requires clnt_create().
 
 4.41		February 27, 1999
-		Added FreeBSD 3.1 and and 4.0 support with help
+		Added FreeBSD 3.1 and 4.0 support with help
 		from Sheldon Hearn <[email protected]>, David O'Brien
 		<[email protected]>, and John Polstra <[email protected]>.
 
@@ -4016,7 +4016,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 		a patch to 4.75.
 
 		Added support for Solaris 10 port and CTFS files.  The
-		CTFS support is imcomplete, because I don't know how
+		CTFS support is incomplete, because I don't know how
 		to get inode number, size and link count.  (There's
 		a new 00FAQ entry about that.)
 
@@ -4076,7 +4076,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 		PA-RISC HP-UX 11.23, based on a report from John
 		Orndorff <[email protected]>.  Found that
 		neither the HP bundled C compiler nor gcc would build
-		lsof, but the the HP unbundled ANSI C compiler would.
+		lsof, but the HP unbundled ANSI C compiler would.
 		Concluded that HP bundled C compiler can't handle
 		<gssapi/gssapi.h>.  Devised a work-around to gcc's
 		omission of the rpcent structure definition of
@@ -4600,7 +4600,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 		Made FreeBSD 9 adjustment.
 
 		Fixed a Linux bug that prevented the display of paths for
-		abstact UNIX sockets.  Masatake Yamato <[email protected]>
+		abstract UNIX sockets.  Masatake Yamato <[email protected]>
 		reported the bug and supplied a patch.
 
 		Added compensation for the removal of RPC header files from
@@ -4752,7 +4752,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 		file names.  Stephane Chazelas <[email protected]>
 		reported the problem.
 
-		Added support for Linux RDMA and CRYPTO protocal names and UNIX
+		Added support for Linux RDMA and CRYPTO protocol names and UNIX
 		socket type with code from Masatake YAMATO <[email protected]>.
 
 		Fixed field output to insure that the field descriptor field is
@@ -5522,7 +5522,7 @@ Supplement	Regenerated the 4.04 distribution to correct a non-
 
 4.99.0		November 10, 2023
 
-		[netbsd] Get device numer of tmpfs instead of reporting zero
+		[netbsd] Get device number of tmpfs instead of reporting zero
 
 
 		[openbsd] Rewrite OpenBSD support because OpenBSD disallows

00FAQ

@@ -485,7 +485,7 @@ Table of Contents:
 17.26.1	Why doesn't lsof report size, link count and node number for
 	Solaris 10 contract files?
 17.26.2 Why can't lsof locate a Solaris 10 contract file by path name?
-17.27	Solaris 10 and above ZFS probblems
+17.27	Solaris 10 and above ZFS problems
 17.27.1	Why does Configure warn that ZFS support is not enabled?
 17.28	Problems with Solaris 9 and above
 17.28.1	Why does the compiler complain about lgrp_root on Solaris 9
@@ -495,7 +495,7 @@ Table of Contents:
 18.1	Why doesn't lsof doesn't report on /proc entries on my
 	system?
 18.2	How do I disable the device cache file feature or alter
-	it's behavior?
+	its behavior?
 18.2.1	What's the risk with a perverted device cache file?
 18.2.2	How do I put the full host name in a personal device cache file
 	path?
@@ -973,7 +973,7 @@ ______________________________________________________________________
 	The vendor additions are significant to lsof because they
 	affect the internal kernel structures with which lsof does
 	business.  While some vendor derivatives of SVR4 are similar,
-	each one I have encounted so far has been different enough
+	each one I have encountered so far has been different enough
 	from its siblings to require special source code.
 
 	If you're interested in an SVR4 version of lsof, here are
@@ -1140,7 +1140,7 @@ ______________________________________________________________________
 	Errors like the above are most likely not problems in the
 	system's header files, but in the private copies of them
 	that were created when gcc was made or installed.  Note
-	the presense of
+	the presence of
 	".../gcc-3.2.1/lib/gcc-lib/sparcv9-sun-solaris2/3.2.1/include/..."
 	in the paths for user.h and task.h.  It indicates both
 	header files are gcc-specific.
@@ -1404,7 +1404,7 @@ ______________________________________________________________________
 	exclusion and inclusion used?" question.
 
 	Your UNIX dialect may not support "-s p:s" and its associated
-	performance improvments to Internet-only file processing.  You
+	performance improvements to Internet-only file processing.  You
 	can find more information on those topics in the answer to the
 	"Why doesn't my dialect support state name exclusion and
 	inclusion?" question.
@@ -1460,7 +1460,7 @@ ______________________________________________________________________
 	ownerships are changed to that of the real user and group.
 	In addition, lsof checks the file carefully before using
 	it (See the question "How do I disable the device cache
-	file feature or alter it's behavior?" for a description of
+	file feature or alter its behavior?" for a description of
 	the checks.); discards the file if it fails the scrutiny;
 	complains about the condition of the file; then rebuilds
 	the file.
@@ -2055,7 +2055,7 @@ ______________________________________________________________________
 
 	If the mounted-on device is a block device (the permission
 	field in output of `ls -l <device>` starts with a `b/),
-	you can specify it's name, too -- e.g.,
+	you can specify its name, too -- e.g.,
 
 	    $ lsof /dev/sd0a
 
@@ -2783,7 +2783,7 @@ ______________________________________________________________________
 	    $ lsof -s/.\// ...
 	    lsof: invalid regexp modifier: /
 
-	Lsof is complaining the the first character it found after
+	Lsof is complaining the first character it found after
 	the second slash isn't an lsof command RE modifier -- 'b',
 	'i', or 'x'.
 
@@ -4067,7 +4067,7 @@ ______________________________________________________________________
 
 	At an upcoming release lsof will use a library called libproc
 	to obtain information about open files.  That version of lsof
-	wil be called libproc-based lsof.
+	will be called libproc-based lsof.
 
 	The /dev/kmem-based lsof sources may be found in the kmem
 	subdirectory of the dialects/darwin branch of the lsof source
@@ -5511,7 +5511,7 @@ ______________________________________________________________________
 	subdirectory of a process' /proc/<PID> directory, it reports a
 	single file of the type ``NOFD'' (for no file descriptors).
 
-	Lsof reports the the /proc/<PID>/path in the NAME column,
+	Lsof reports the /proc/<PID>/path in the NAME column,
 	followed by "(opendir: xxx)", where ``xxx'' is the error
 	message returned by opendir().
 
@@ -7523,7 +7523,7 @@ ______________________________________________________________________
 	applying stat(2) to the contract file path name with what it
 	finds in kernel data.
 
-17.27	Solaris 10 and above ZFS probblems
+17.27	Solaris 10 and above ZFS problems
 
 17.27.1	Why does Configure warn that ZFS support is not enabled?
 
@@ -7578,7 +7578,7 @@ ______________________________________________________________________
 	-- usually called prdata.h.
 
 18.2	How do I disable the device cache file feature or alter
-	it's behavior?
+	its behavior?
 
 	To disable the device cache file feature for a dialect,
 	remove the HASDCACHE definition from the machine.h file of

00PORTING

@@ -1195,7 +1195,7 @@ possibilities
 
     HASTCPUDPSTATE	is defined when the dialect has support for
 			TCP and UDP state, including the "-s p:s"
-			option and associated speed ehancements.
+			option and associated speed enhancements.
 
     HASTFS		indicates that the Pyramid dialect has TFS
 			file system support.
@@ -1390,7 +1390,7 @@ possibilities
 
     NOWARNBLKDEV        specifies that no warning is to be issued
 			when no block devices are found.  This
-			definiton is used only when HASBLKDEV is
+			definition is used only when HASBLKDEV is
 			also defined.
 
     OFFDECDIG           specifies how many decimal digits will be

00README

@@ -562,7 +562,7 @@ compile-time definitions for the dialect's machine.h header file:
 	HASKERNIDCK		the build-time to run-time kernel
 				identity check
 	HASSECURITY		the security option
-	HASNOSOCKSECURITY	the open socket listing option whe
+	HASNOSOCKSECURITY	the open socket listing option when
 				HASSECURITY is defined
 	WARNDEVACCESS		/dev (or /devices) warning message
 				control
@@ -825,8 +825,8 @@ of tests/, with:
 	$ make opt
     or	$ make optional
 
-It's possible to excute individual tests, too.  See the 00TEST file
-of this distribution for more informaiton on the tests, what they
+It's possible to execute individual tests, too.  See the 00TEST file
+of this distribution for more information on the tests, what they
 do, and how to run and possibly customize each test.
 
 It's possible to run the tests, using an lsof other than the one
@@ -1336,7 +1336,7 @@ to read memory devices such as /dev/kmem, /dev/mem, or /dev/swap,
 or it may be authorization to read entries in the /proc file system.
 
 Memory device access can usually be provided by setting the modes
-of the lsof executable so that it's effective group identifier when
+of the lsof executable so that its effective group identifier when
 it runs is the same as the group that has permission to read the
 memory devices -- i.e., it is setgid-group.  The privileged group
 is usually kmem, sys, or system.

00TEST

@@ -816,7 +816,7 @@ These files may be created by suite tests.
 
     config.LTnlink*	LTnlink	    for link count tests
 
-    config.LTszoff*     LTszoff     for small file size and and
+    config.LTszoff*     LTszoff     for small file size and
 				    offset reporting
 
     config.LT[01]U*     LTunix      two UNIX domain sockets, used

00XCONFIG

@@ -33,7 +33,7 @@ Marty says:
 
 	LINUX_KERNEL=/some/other/kernel LSOF_VERS=2142 ./Configure linux
 
-     Comments?  Its very convenient when running multiple kernels.
+     Comments?  It's very convenient when running multiple kernels.
      (It would be (have been) very handy when the structures changed
      between 2.0.2* and 2.0.30 , or whatever.)
 
@@ -151,7 +151,7 @@ LSOF_HOST       may be used to specify a value in lsof's -v output
 			 hostname or uname -n
 
 LSOF_INCLUDE    is the path to a tree of header files that is an exact
-		image of the the standard header file tree for the
+		image of the standard header file tree for the
 		target dialect.  You may need to specify it if you
 		want Configure to test header files in a tree different
 		from /usr/include and compile its test programs with
@@ -181,7 +181,7 @@ LSOF_LOGNAME    may be used to specify a value in lsof's -v output
 
 LSOF_MAKE	is the path to the make command.
 
-		deafult: the output of `which make`, if it is not NULL;
+		default: the output of `which make`, if it is not NULL;
 			 otherwise the string "make".
 
 LSOF_MKC        may be used to specify an alternate method of
@@ -527,7 +527,7 @@ LINUX_CONF_CC		specifies the location of the C compiler to use during
 LINUX_HASSELINUX	If this environment variable has a value of "Y" or "y",
 			Configure unconditionally activates SELinux support.
 			If it has any other value, Configure unconditionally
-			inhibits SELinux suport.
+			inhibits SELinux support.
 
 			Default: assumed to be "Y" if <selinux/selinux.h>
 				 exists

Configure

@@ -243,7 +243,7 @@ Usage: Configure <options> <target-dialect>
     linux                   : Linux
     netbsd                  : NetBSD
     openbsd                 : OpenBSD
-    osr|sco                 : SCO OpenServer < 6.0.0, SCO devloper's compiler
+    osr|sco                 : SCO OpenServer < 6.0.0, SCO developer's compiler
     osrgcc|scogcc           : SCO OpenServer < 6.0.0, gcc compiler
     osr6                    : SCO OpenServer 6.0.0, SCO compiler
     solaris|solariscc       : Solaris gcc (solaris) or cc (solariscc)

Customize

@@ -641,7 +641,7 @@ users.  Press ENTER to use the current value of HASENVDC:
 HASPERSDC is a format that specifies how the personal device cache
 path is constructed.  Consult the 00DCACHE and 00FAQ files of the
 lsof distribution for information on the conversions supported in
-HASPERSDC.  Press ENTER to use the curent HASPERSDC format:
+HASPERSDC.  Press ENTER to use the current HASPERSDC format:
 
 .CAT_MARK
 

Doxyfile

@@ -85,7 +85,7 @@ CREATE_SUBDIRS         = NO
 # level increment doubles the number of directories, resulting in 4096
 # directories at level 8 which is the default and also the maximum value. The
 # sub-directories are organized in 2 levels, the first level always has a fixed
-# numer of 16 directories.
+# number of 16 directories.
 # Minimum value: 0, maximum value: 8, default value: 8.
 # This tag requires that the tag CREATE_SUBDIRS is set to YES.
 

docs/faq.md

@@ -664,7 +664,7 @@ may complain that it finds errors in system header files
 Errors like the above are most likely not problems in the
 system's header files, but in the private copies of them
 that were created when gcc was made or installed.  Note
-the presense of
+the presence of
 ".../gcc-3.2.1/lib/gcc-lib/sparcv9-sun-solaris2/3.2.1/include/..."
 in the paths for user.h and task.h.  It indicates both
 header files are gcc-specific.
@@ -928,7 +928,7 @@ may be found in the answer to the "How are protocol state name
 exclusion and inclusion used?" question.
 
 Your UNIX dialect may not support "-s p:s" and its associated
-performance improvments to Internet-only file processing.  You
+performance improvements to Internet-only file processing.  You
 can find more information on those topics in the answer to the
 "Why doesn't my dialect support state name exclusion and
 inclusion?" question.
@@ -984,7 +984,7 @@ when lsof runs setuid-root, it makes sure the file's
 ownerships are changed to that of the real user and group.
 In addition, lsof checks the file carefully before using
 it (See the question "How do I disable the device cache
-file feature or alter it's behavior?" for a description of
+file feature or alter its behavior?" for a description of
 the checks.); discards the file if it fails the scrutiny;
 complains about the condition of the file; then rebuilds
 the file.
@@ -1577,7 +1577,7 @@ for the file system.
 
 If the mounted-on device is a block device (the permission
 field in output of `ls -l <device>` starts with a `b/),
-you can specify it's name, too -- e.g.,
+you can specify its name, too -- e.g.,
 
 	$ lsof /dev/sd0a
 
@@ -2299,7 +2299,7 @@ command RE, you'll get this response:
 	$ lsof -s/.\// ...
 	lsof: invalid regexp modifier: /
 
-Lsof is complaining the the first character it found after
+Lsof is complaining the first character it found after
 the second slash isn't an lsof command RE modifier -- 'b',
 'i', or 'x'.
 

docs/getting-started.md

@@ -24,7 +24,7 @@ You should use the legacy build system if you are building lsof on old OSes or d
 - linux                   : Linux
 - netbsd                  : NetBSD
 - openbsd                 : OpenBSD
-- osr|sco                 : SCO OpenServer < 6.0.0, SCO devloper's compiler
+- osr|sco                 : SCO OpenServer < 6.0.0, SCO developer's compiler
 - osrgcc|scogcc           : SCO OpenServer < 6.0.0, gcc compiler
 - osr6                    : SCO OpenServer 6.0.0, SCO compiler
 - solaris|solariscc       : Solaris gcc (solaris) or cc (solariscc)
@@ -104,4 +104,4 @@ If you use NixOS/nix-based Linux distros:
 
 ```shell
 nix-env -i lsof
-```
+```

docs/maintaining.md

@@ -131,7 +131,7 @@ in bash.
 
 About the original test mechanism, see tests/00README.
 
-About the the github test mechanism, see tests/case-00-hello.bash .
+About the github test mechanism, see tests/case-00-hello.bash .
 You can put a test case non-dialect specific, put tests/.
 dialects/linux/tests/ is for testing linux specific code.
 

include/lsof.h

@@ -260,7 +260,7 @@ struct lsof_file {
     uint64_t flags;
 
     /* FD column */
-    /** File desciptor type */
+    /** File descriptor type */
     enum lsof_fd_type fd_type;
 
     /** File descriptor number, valid if \ref fd_type == \ref LSOF_FD_NUMERIC */
@@ -551,7 +551,7 @@ enum lsof_error lsof_freeze(struct lsof_context *ctx);
 
 /** List open files, grouped by processes
  *
- * The result is a struct lsof_result, saved into `result` paramter.
+ * The result is a struct lsof_result, saved into `result` parameter.
  *
  * You should not alter the content of `result`, nor call `free()` to
  * pointers within. You should free `result` by calling
@@ -583,4 +583,4 @@ void lsof_destroy(struct lsof_context *ctx);
  */
 void lsof_free_result(struct lsof_result *result);
 
-#endif
+#endif

lib/dialects/aix/dlsof.h

@@ -36,7 +36,7 @@
 #    define AIX_LSOF_H 1
 
 /*
- * AIXA stands for AIX architecure.  It is given these values in the
+ * AIXA stands for AIX architecture.  It is given these values in the
  * aix stanza of the lsof Configure script:
  *
  *     0	The AIX version is < 5, or the AIX architecture is power and

lib/dialects/aix/machine.h

@@ -291,7 +291,7 @@ typedef long long aligned_offset_t __attribute__((aligned(8)));
 /* #define	NCACHELDSFX	??? */
 
 /*
- * HASNLIST is defined for those dialects that use nlist() to acccess
+ * HASNLIST is defined for those dialects that use nlist() to access
  * kernel symbols.  (AIX lsof doesn't use nlist, it uses knlist.)
  */