accept.2, access.2, acct.2, clock_nanosleep.2, mbind.2, mincore.2, remap_file_pages.2, sched_setscheduler.2, set_mempolicy.2, splice.2, stat.2, syslog.2, timer_create.2, timerfd_create.2, truncate.2, fenv.3, ferror.3, fflush.3, fgetwc.3, fgetws.3, flockfile.3, fputwc.3, fputws.3, fread.3, getopt.3, gets.3, getwchar.3, glob.3, iconv.3, longjmp.3, pow.3, printf.3, puts.3, putwchar.3, regex.3, rpc.3, scanf.3, setjmp.3, termios.3, unlocked_stdio.3, wcswidth.3, hd.4, rtc.4, st.4, core.5, dir_colors.5, elf.5, proc.5, arp.7, ascii.7, boot.7, bootparam.7, charsets.7, futex.7, ip.7, iso_8859-11.7, man-pages.7, man.7, mdoc.samples.7, path_resolution.7, pipe.7, posixoptions.7, unicode.7, unix.7, uri.7, utf-8.7, ld.so.8: s/non-/non/

The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/man7/path_resolution.7 b/man7/path_resolution.7
index 11d8cc87..7c10c712 100644
--- a/man7/path_resolution.7
+++ b/man7/path_resolution.7
@@ -58,7 +58,7 @@ Pathnames starting with a \(aq/\(aq character are called absolute pathnames.
 Pathnames not starting with a \(aq/\(aq are called relative pathnames.
 .SS "Step 2: Walk along the path"
 Set the current lookup directory to the starting lookup directory.
-Now, for each non-final component of the pathname, where a component
+Now, for each nonfinal component of the pathname, where a component
 is a substring delimited by \(aq/\(aq characters, this component is looked up
 in the current lookup directory.
 
@@ -110,7 +110,7 @@ The lookup of the final component of the pathname goes just like
 that of all other components, as described in the previous step,
 with two differences: (i) the final component need not be a
 directory (at least as far as the path resolution process is concerned \(em
-it may have to be a directory, or a non-directory, because of
+it may have to be a directory, or a nondirectory, because of
 the requirements of the specific system call), and (ii) it
 is not necessarily an error if the component is not found \(em
 maybe we are just creating it.