3 files changed, 17 insertions, 17 deletions
diff --git a/man5/core.5 b/man5/core.5
index 886e88a927..0c3bcfec21 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -153,7 +153,7 @@ For backward compatibility, if
 does not include "%p" and
 .I /proc/sys/kernel/core_uses_pid
 (see below)
-is non-zero, then .PID will be appended to the core filename.
+is nonzero, then .PID will be appended to the core filename.
 
 Since version 2.4, Linux has also provided
 a more primitive method of controlling
@@ -162,7 +162,7 @@ If the
 .I /proc/sys/kernel/core_uses_pid
 file contains the value 0, then a core dump file is simply named
 .IR core .
-If this file contains a non-zero value, then the core dump file includes
+If this file contains a nonzero value, then the core dump file includes
 the process ID in a name of the form
 .IR core.PID .
 .SS Piping core dumps to a program
diff --git a/man5/elf.5 b/man5/elf.5
index b8471b9acc..72d2b499d9 100644
--- a/man5/elf.5
+++ b/man5/elf.5
@@ -1098,7 +1098,7 @@ the section occupies
 bytes in the file.
 A section of type
 .BR SHT_NOBITS
-may have a non-zero size, but it occupies no space in the file.
+may have a nonzero size, but it occupies no space in the file.
 .TP
 .IR sh_link
 This member holds a section header table index link, whose interpretation
@@ -1480,7 +1480,7 @@ order.
 This member holds an index into the object file's symbol string table,
 which holds character representations of the symbol names.
 If the value
-is non-zero, it represents a string table index that gives the symbol
+is nonzero, it represents a string table index that gives the symbol
 name.
 Otherwise, the symbol table has no name.
 .TP
diff --git a/man5/proc.5 b/man5/proc.5
index 997a2a0ac3..09b2ce512a 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -1769,7 +1769,7 @@ can be reclaimed when memory is short.
 .IP *
 .I want_pages
 .\" looks like this is unused in kernels 2.2 to 2.6
-is non-zero when the kernel has called shrink_dcache_pages() and the
+is nonzero when the kernel has called shrink_dcache_pages() and the
 dcache isn't pruned yet.
 .RE
 .TP
@@ -1877,7 +1877,7 @@ because Linux allocates them one page full at a time.
 .I nr_free_inodes
 represents the number of free inodes.
 .I preshrink
-is non-zero when the
+is nonzero when the
 .I nr_inodes
 >
 .I inode-max
@@ -1906,7 +1906,7 @@ This file can be used to enable or disable file leases
 .RB ( fcntl (2))
 on a system-wide basis.
 If this file contains the value 0, leases are disabled.
-A non-zero value enables leases.
+A nonzero value enables leases.
 .TP
 .IR /proc/sys/fs/mqueue " (since Linux 2.6.6)"
 This directory contains files
@@ -2077,7 +2077,7 @@ see the
 man page.
 .TP
 .I /proc/sys/kernel/htab-reclaim
-(PowerPC only) If this file is set to a non-zero value,
+(PowerPC only) If this file is set to a nonzero value,
 the PowerPC htab
 (see kernel file
 .IR Documentation/powerpc/ppc_htab.txt )
@@ -2089,7 +2089,7 @@ each time the system hits the idle loop.
 contains a flag that controls the L2 cache of G3 processor
 boards.
 If 0, the cache is disabled.
-Enabled if non-zero.
+Enabled if nonzero.
 .TP
 .I /proc/sys/kernel/modprobe
 This file contains the path for the kernel module loader.
@@ -2135,7 +2135,7 @@ and
 .I /proc/sys/kernel/panic
 This file gives read/write access to the kernel variable
 .IR panic_timeout .
-If this is zero, the kernel will loop on a panic; if non-zero
+If this is zero, the kernel will loop on a panic; if nonzero
 it indicates that the kernel should autoreboot after this number
 of seconds.
 When you use the
@@ -2151,7 +2151,7 @@ delays a few seconds (to give klogd time to record the oops output)
 and then panics.
 If the
 .I /proc/sys/kernel/panic
-file is also non-zero then the machine will be rebooted.
+file is also nonzero then the machine will be rebooted.
 .TP
 .IR /proc/sys/kernel/pid_max " (since Linux 2.5.34)"
 This file specifies the value at which PIDs wrap around
@@ -2334,7 +2334,7 @@ threads (tasks) that can be created on the system.
 .IR /proc/sys/kernel/zero-paged " (PowerPC only) "
 This file
 contains a flag.
-When enabled (non-zero), Linux-PPC will pre-zero pages in
+When enabled (nonzero), Linux-PPC will pre-zero pages in
 the idle loop, possibly speeding up get_free_pages.
 .TP
 .I /proc/sys/net
@@ -2392,7 +2392,7 @@ The default value is 60.
 .TP
 .IR /proc/sys/vm/legacy_va_layout " (since Linux 2.6.9)"
 .\" The following is from Documentation/filesystems/proc.txt
-If non-zero, this disables the new 32-bit memory-mapping layout;
+If nonzero, this disables the new 32-bit memory-mapping layout;
 the kernel will use the legacy (2.4) layout for all processes.
 .TP
 .IR /proc/sys/vm/oom_dump_tasks " (since Linux 2.6.25)"
@@ -2416,7 +2416,7 @@ it may not be feasible to dump the memory state information for each one.
 Such systems should not be forced to incur a performance penalty in
 OOM situations when the information may not be desired.
 
-If this is set to non-zero, this information is shown whenever the
+If this is set to nonzero, this information is shown whenever the
 OOM-killer actually kills a memory-hogging task.
 
 The default value is 0.
@@ -2431,13 +2431,13 @@ tasklist and select a task based on heuristics to kill.
 This normally selects a rogue memory-hogging task that
 frees up a large amount of memory when killed.
 
-If this is set to non-zero, the OOM-killer simply kills the task that
+If this is set to nonzero, the OOM-killer simply kills the task that
 triggered the out-of-memory condition.
 This avoids a possibly expensive tasklist scan.
 
 If
 .I /proc/sys/vm/panic_on_oom
-is non-zero, it takes precedence over whatever value is used in
+is nonzero, it takes precedence over whatever value is used in
 .IR /proc/sys/vm/oom_kill_allocating_task .
 
 The default value is 0.
@@ -2460,7 +2460,7 @@ with
 .B MAP_NORESERVE
 are not checked, and the default check is very weak,
 leading to the risk of getting a process "OOM-killed".
-Under Linux 2.4 any non-zero value implies mode 1.
+Under Linux 2.4 any nonzero value implies mode 1.
 In mode 2 (available since Linux 2.6), the total virtual address space
 on the system is limited to (SS + RAM*(r/100)),
 where SS is the size of the swap space, and RAM