getitimer.2, getrusage.2, times.2, utimensat.2, pthread_create.3, pthreads.7, utf-8.7: Global fix: s/non-conform/nonconform/

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>

man2/getitimer.2

@@ -207,7 +207,7 @@ However, in kernels up to and including 2.6.21,
 Linux does not give an error, but instead silently
 adjusts the corresponding seconds value for the timer.
 From kernel 2.6.22 onwards,
-this non-conformance has been repaired:
+this nonconformance has been repaired:
 an improper
 .I tv_usec
 value results in an

man2/getrusage.2

@@ -28,7 +28,7 @@
 .\" now covered in its own getrusage.2.  For older details of change
 .\" history, etc., see getrlimit.2
 .\"
-.\" Modified 2004-11-16, mtk, Noted that the non-conformance
+.\" Modified 2004-11-16, mtk, Noted that the nonconformance
 .\"	when SIGCHLD is being ignored is fixed in 2.6.9.
 .\" 2008-02-22, Sripathi Kodi <sripathik@in.ibm.com>: Document RUSAGE_THREAD
 .\" 2008-05-25, mtk, clarify RUSAGE_CHILDREN + other clean-ups.
@@ -134,7 +134,7 @@ then the resource usages of child processes
 are automatically included in the value returned by
 .BR RUSAGE_CHILDREN ,
 although POSIX.1-2001 explicitly prohibits this.
-This non-conformance is rectified in Linux 2.6.9 and later.
+This nonconformance is rectified in Linux 2.6.9 and later.
 .\" See the description of getrusage() in XSH.
 .\" A similar statement was also in SUSv2.
 .LP

man2/times.2

@@ -28,7 +28,7 @@
 .\" Modified 001213 by Michael Haardt (michael@moria.de)
 .\" Modified 13 Jun 02, Michael Kerrisk <mtk.manpages@gmail.com>
 .\"	Added note on nonstandard behavior when SIGCHLD is ignored.
-.\" Modified 2004-11-16, mtk, Noted that the non-conformance when
+.\" Modified 2004-11-16, mtk, Noted that the nonconformance when
 .\"	SIGCHLD is being ignored is fixed in 2.6.9; other minor changes
 .\" Modified 2004-12-08, mtk, in 2.6 times() return value changed
 .\" 2005-04-13, mtk
@@ -136,7 +136,7 @@ fields, although POSIX.1-2001 says that this should only happen
 if the calling process
 .BR wait (2)s
 on its children.
-This non-conformance is rectified in Linux 2.6.9 and later.
+This nonconformance is rectified in Linux 2.6.9 and later.
 .\" See the description of times() in XSH, which says:
 .\"	The times of a terminated child process are included... when wait()
 .\"	or waitpid() returns the process ID of this terminated child.

man2/utimensat.2

@@ -452,7 +452,7 @@ Several bugs afflict
 and
 .BR futimens ()
 on kernels before 2.6.26.
-These bugs are either non-conformances with the POSIX.1 draft specification
+These bugs are either nonconformances with the POSIX.1 draft specification
 or inconsistencies with historical Linux behavior.
 .IP * 2
 POSIX.1 specifies that if one of the

man3/pthread_create.3

@@ -362,7 +362,7 @@ main(int argc, char *argv[])
 In the obsolete LinuxThreads implementation,
 each of the threads in a process has a different process ID.
 This is in violation of the POSIX threads specification,
-and is the source of many other non-conformances to the standard; see
+and is the source of many other nonconformances to the standard; see
 .BR pthreads (7).
 .SH SEE ALSO
 .BR getrlimit (2),

man7/pthreads.7

@@ -778,16 +778,16 @@ NPTL makes internal use of the first two real-time signals
 .BR signal (7));
 these signals cannot be used in applications.
 
-NPTL still has at least one non-conformance with POSIX.1:
+NPTL still has at least one nonconformance with POSIX.1:
 .IP \- 3
 Threads do not share a common nice value.
-.\" FIXME . bug report filed for NPTL nice non-conformance
+.\" FIXME . bug report filed for NPTL nice nonconformance
 .\" http://bugzilla.kernel.org/show_bug.cgi?id=6258
 .\" Sep 08: there is a patch by Denys Vlasenko to address this
 .\" "make setpriority POSIX compliant; introduce PRIO_THREAD extension"
 .\" Monitor this to see if it makes it into mainline.
 .PP
-Some NPTL non-conformances only occur with older kernels:
+Some NPTL nonconformances only occur with older kernels:
 .IP \- 3
 The information returned by
 .BR times (2)
@@ -864,7 +864,7 @@ By specifying a kernel version that does not
 provide the support required by NPTL, we can force the use
 of LinuxThreads.
 (The most likely reason for doing this is to run a
-(broken) application that depends on some non-conformant behavior
+(broken) application that depends on some nonconformant behavior
 in LinuxThreads.)
 For example:
 .nf

man7/utf-8.7

@@ -274,7 +274,7 @@ The
 standards require that producers of
 .B UTF-8
 shall use the shortest form possible, for example, producing a two-byte
-sequence with first byte 0xc0 is non-conforming.
+sequence with first byte 0xc0 is nonconforming.
 .B Unicode 3.1
 has added the requirement that conforming programs must not accept
 non-shortest forms in their input.