proc.5: tfix

Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man5/proc.5

@@ -1172,9 +1172,9 @@ the storage layer.
 .TP
 .IR cancelled_write_bytes :
 The big inaccuracy here is truncate.
-If a process writes 1MB to a file and then deletes the file,
+If a process writes 1 MB to a file and then deletes the file,
 it will in fact perform no writeout.
-But it will have been accounted as having caused 1MB of write.
+But it will have been accounted as having caused 1 MB of write.
 In other words: this field represents the number of bytes which this process
 caused to not happen, by truncating pagecache.
 A task can cause "negative" I/O too.
@@ -1971,7 +1971,7 @@ The "KernelPageSize" line (available since Linux 2.6.29)
 is the page size used by the kernel to back the virtual memory area.
 This matches the size used by the MMU in the majority of cases.
 However, one counter-example occurs on PPC64 kernels
-whereby a kernel using 64kB as a base page size may still use 4kB
+whereby a kernel using 64 kB as a base page size may still use 4 kB
 pages for the MMU on older processors.
 To distinguish the two attributes, the "MMUPageSize" line
 (also available since Linux 2.6.29)
@@ -3485,7 +3485,7 @@ applications, without swapping.
 .TP
 .IR Buffers " %lu"
 Relatively temporary storage for raw disk blocks that
-shouldn't get tremendously large (20MB or so).
+shouldn't get tremendously large (20 MB or so).
 .TP
 .IR Cached " %lu"
 In-memory cache for files read from the disk (the page cache).
@@ -3533,7 +3533,7 @@ It is more eligible to be reclaimed for other purposes.
 .IR HighTotal " %lu"
 (Starting with Linux 2.6.19, \fBCONFIG_HIGHMEM\fP is required.)
 Total amount of highmem.
-Highmem is all memory above ~860MB of physical memory.
+Highmem is all memory above ~860 MB of physical memory.
 Highmem areas are for use by user-space programs,
 or for the page cache.
 The kernel must use tricks to access
@@ -3646,13 +3646,13 @@ The amount of memory presently allocated on the system.
 The committed memory is a sum of all of the memory which
 has been allocated by processes, even if it has not been
 "used" by them as of yet.
-A process which allocates 1GB of memory (using
+A process which allocates 1 GB of memory (using
 .BR malloc (3)
-or similar), but touches only 300MB of that memory will show up
-as using only 300MB of memory even if it has the address space
-allocated for the entire 1GB.
+or similar), but touches only 300 MB of that memory will show up
+as using only 300 MB of memory even if it has the address space
+allocated for the entire 1 GB.
 .IP
-This 1GB is memory which has been "committed" to by the VM
+This 1 GB is memory which has been "committed" to by the VM
 and can be used at any time by the allocating application.
 With strict overcommit enabled on the system (mode 2 in
 .IR /proc/sys/vm/overcommit_memory ),
@@ -3698,7 +3698,7 @@ Non-file backed huge pages mapped into user-space page tables.
 (\fBCONFIG_TRANSPARENT_HUGEPAGE\fP is required.)
 Memory used by shared memory (shmem) and
 .BR tmpfs (5)
-allocated with huge pages
+allocated with huge pages.
 .TP
 .IR ShmemPmdMapped " %lu (since Linux 4.8)"
 (\fBCONFIG_TRANSPARENT_HUGEPAGE\fP is required.)
@@ -3742,11 +3742,11 @@ The maximum number of surplus huge pages is controlled by
 The size of huge pages.
 .TP
 .IR DirectMap4k " %lu (since Linux 2.6.27)"
-Number of bytes of RAM linearly mapped by kernel in 4kB pages.
+Number of bytes of RAM linearly mapped by kernel in 4 kB pages.
 (x86.)
 .TP
 .IR DirectMap4M " %lu (since Linux 2.6.27)"
-Number of bytes of RAM linearly mapped by kernel in 4MB pages.
+Number of bytes of RAM linearly mapped by kernel in 4 MB pages.
 (x86 with
 .BR CONFIG_X86_64
 or
@@ -3754,7 +3754,7 @@ or
 enabled.)
 .TP
 .IR DirectMap2M " %lu (since Linux 2.6.27)"
-Number of bytes of RAM linearly mapped by kernel in 2MB pages.
+Number of bytes of RAM linearly mapped by kernel in 2 MB pages.
 (x86 with neither
 .BR CONFIG_X86_64
 nor
@@ -4246,7 +4246,7 @@ in certain conditions.
 .\" Precisely: Linux 2.6.0-test4
 (6) Time servicing interrupts.
 .TP
-.IR softirq " (since Linux 2.6.0"
+.IR softirq " (since Linux 2.6.0)"
 .\" Precisely: Linux 2.6.0-test4
 (7) Time servicing softirqs.
 .TP
@@ -5305,7 +5305,7 @@ This file
 can be used to query and set the run-time limit
 on the maximum (System V IPC) shared memory segment size that can be
 created.
-Shared memory segments up to 1GB are now supported in the
+Shared memory segments up to 1 GB are now supported in the
 kernel.
 This value defaults to
 .BR SHMMAX .
@@ -5622,7 +5622,7 @@ Present only if the kernel was configured with
 .TP
 .IR /proc/sys/vm/memory_failure_recovery " (since Linux 2.6.32)"
 .\" The following is based on the text in Documentation/sysctl/vm.txt
-Enable memory failure recovery (when supported by the platform)
+Enable memory failure recovery (when supported by the platform).
 .RS
 .IP 1: 4
 Attempt recovery.
@@ -5765,12 +5765,12 @@ and
 is the amount of swap space.
 .RE
 .IP
-For example, on a system with 16GB of physical RAM, 16GB
+For example, on a system with 16 GB of physical RAM, 16 GB
 of swap, no space dedicated to huge pages, and an
 .I overcommit_ratio
 of 50, this formula yields a
 .I CommitLimit
-of 24GB.
+of 24 GB.
 .IP
 Since Linux 3.14, if the value in
 .I /proc/sys/vm/overcommit_kbytes
@@ -5834,7 +5834,7 @@ The default value is 60.
 .TP
 .IR /proc/sys/vm/user_reserve_kbytes " (since Linux 3.10)"
 .\" commit c9b1d0981fcce3d9976d7b7a56e4e0503bc610dd
-Specifies an amount of memory (in KiB) to reserve for user processes,
+Specifies an amount of memory (in KiB) to reserve for user processes.
 This is intended to prevent a user from starting a single memory hogging
 process, such that they cannot recover (kill the hog).
 The value in this file has an effect only when
@@ -6739,7 +6739,7 @@ See the kernel source file
 .RE
 .TP
 .IR /proc/zoneinfo " (since Linux 2.6.13)"
-This file display information about memory zones.
+This file displays information about memory zones.
 This is useful for analyzing virtual memory behavior.
 .\" FIXME more should be said about /proc/zoneinfo
 .SH NOTES