diff --git a/man1/intro.1 b/man1/intro.1
index 5a7d00982..8466624c7 100644
--- a/man1/intro.1
+++ b/man1/intro.1
@@ -204,8 +204,8 @@ describing the path from the root of the tree (which is called /)
 to the file.
 For example, such a full pathname might be /home/aeb/tel.
 Always using full pathnames would be inconvenient, and the name
-of a file in the current directory may be abbreviated by only giving
-the last component.
+of a file in the current directory may be abbreviated by giving
+only the last component.
 That is why "/home/aeb/tel" can be abbreviated
 to "tel" when the current directory is "/home/aeb".
 .LP
diff --git a/man2/_syscall.2 b/man2/_syscall.2
index 34d2ac3be..82d231906 100644
--- a/man2/_syscall.2
+++ b/man2/_syscall.2
@@ -108,7 +108,7 @@ passed by-value or by-pointer (for aggregates like structs).
 .\" The preferred way to invoke system calls that glibc does not know
 .\" about yet is via
 .\" .BR syscall (2).
-.\" However, this mechanism can only be used if using a libc
+.\" However, this mechanism can be used only if using a libc
 .\" (such as glibc) that supports
 .\" .BR syscall (2),
 .\" and if the
diff --git a/man2/access.2 b/man2/access.2
index 9ad8016a1..26288bb16 100644
--- a/man2/access.2
+++ b/man2/access.2
@@ -184,7 +184,7 @@ check even if none of the execute file permission bits are set.
 .\" HPU-UX 11 and Tru64 5.1 do this.
 Linux does not do this.
 .PP
-A file is only accessible if the permissions on each of the
+A file is accessible only if the permissions on each of the
 directories in the path prefix of
 .I pathname
 grant search (i.e., execute) access.
diff --git a/man2/arch_prctl.2 b/man2/arch_prctl.2
index b5994a6e3..6f8f4b506 100644
--- a/man2/arch_prctl.2
+++ b/man2/arch_prctl.2
@@ -106,7 +106,7 @@ is a Linux/x86-64 extension and should not be used in programs intended
 to be portable.
 .SH NOTES
 .BR arch_prctl ()
-is only supported on Linux/x86-64 for 64-bit programs currently.
+is supported only on Linux/x86-64 for 64-bit programs currently.
 
 The 64-bit base changes when a new 32-bit segment selector is loaded.
 
@@ -121,7 +121,7 @@ or using the
 .BR set_thread_area (2)
 system call in kernel 2.5 or later.
 .BR arch_prctl ()
-is only needed when you want to set bases that are larger than 4GB.
+is needed only when you want to set bases that are larger than 4GB.
 Memory in the first 2GB of address space can be allocated by using
 .BR mmap (2)
 with the
diff --git a/man2/cacheflush.2 b/man2/cacheflush.2
index 8be452b39..e7cfdf33b 100644
--- a/man2/cacheflush.2
+++ b/man2/cacheflush.2
@@ -73,7 +73,7 @@ is not one of
 or
 .BR BCACHE .
 .SH CONFORMING TO
-This Linux-specific system call is only available on MIPS-based systems.
+This Linux-specific system call is available only on MIPS-based systems.
 .\" FIXME This system call was only on MIPS back in 1.2 days, but
 .\" by now it is on a number of other architectures (but not i386).
 .\" Investigate the details and update this page.
diff --git a/man2/chown.2 b/man2/chown.2
index 8a04d14aa..c62d19ccf 100644
--- a/man2/chown.2
+++ b/man2/chown.2
@@ -181,8 +181,8 @@ See above.
 .SH CONFORMING TO
 4.4BSD, SVr4, POSIX.1-2001.
 
-The 4.4BSD version can only be
-used by the superuser (that is, ordinary users cannot give away files).
+The 4.4BSD version can be
+used only by the superuser (that is, ordinary users cannot give away files).
 .\" chown():
 .\" SVr4 documents EINVAL, EINTR, ENOLINK and EMULTIHOP returns, but no
 .\" ENOMEM.  POSIX.1 does not document ENOMEM or ELOOP error conditions.
diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
index ea29a5a52..10ecd1820 100644
--- a/man2/clock_getres.2
+++ b/man2/clock_getres.2
@@ -239,7 +239,7 @@ If that is the case then
 will return
 .B ENOENT
 to signify this condition.
-The two clocks will then only be useful if it
+The two clocks will then be useful only if it
 can be ensured that a process stays on a certain CPU.
 .PP
 The processors in an SMP system do not start all at exactly the same
diff --git a/man2/clone.2 b/man2/clone.2
index 6ac95f24a..6c2e2c606 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -293,7 +293,7 @@ This flag can't be specified in conjunction with
 .TP
 .BR CLONE_NEWNET " (since Linux 2.6.24)"
 .\" FIXME Check when the implementation was completed
-(The implementation of this flag was only completed
+(The implementation of this flag was completed only
 by about kernel version 2.6.29.)
 
 If
diff --git a/man2/create_module.2 b/man2/create_module.2
index aab569172..5cf2a6cc1 100644
--- a/man2/create_module.2
+++ b/man2/create_module.2
@@ -56,7 +56,7 @@ The caller was not privileged
 .B CAP_SYS_MODULE
 capability).
 .SH VERSIONS
-This system call is only present on Linux up until kernel 2.4;
+This system call is present on Linux only up until kernel 2.4;
 it was removed in Linux 2.6.
 .\" Removed in Linux 2.5.48
 .SH CONFORMING TO
diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 2f82edfd7..e358ad03f 100644
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -786,7 +786,7 @@ This will cause the calling process to be notified when
 the file is opened for writing or is truncated.
 .\" The following became true in kernel 2.6.10:
 .\" See the man-pages-2.09 Changelog for further info.
-A read lease can only be placed on a file descriptor that
+A read lease can be placed only on a file descriptor that
 is opened read-only.
 .TP
 .B F_WRLCK
@@ -813,8 +813,8 @@ Furthermore, the lease is released by either an explicit
 operation on any of these duplicate descriptors, or when all
 such descriptors have been closed.
 .P
-Leases may only be taken out on regular files.
-An unprivileged process may only take out a lease on a file whose
+Leases may be taken out only on regular files.
+An unprivileged process may take out a lease only on a file whose
 UID (owner) matches the file system UID of the process.
 A process with the
 .B CAP_LEASE
diff --git a/man2/flock.2 b/man2/flock.2
index e08072502..ee3e1c187 100644
--- a/man2/flock.2
+++ b/man2/flock.2
@@ -94,7 +94,7 @@ An attempt to lock the file using one of these file descriptors
 may be denied by a lock that the calling process has
 already placed via another descriptor.
 
-A process may only hold one type of lock (shared or exclusive)
+A process may hold only one type of lock (shared or exclusive)
 on a file.
 Subsequent
 .BR flock ()
diff --git a/man2/get_kernel_syms.2 b/man2/get_kernel_syms.2
index 4e82de1c7..36f28b5c3 100644
--- a/man2/get_kernel_syms.2
+++ b/man2/get_kernel_syms.2
@@ -58,7 +58,7 @@ There is only one possible error return:
 .BR get_kernel_syms ()
 is not supported in this version of the kernel.
 .SH VERSIONS
-This system call is only present on Linux up until kernel 2.4;
+This system call is present on Linux only up until kernel 2.4;
 it was removed in Linux 2.6.
 .\" Removed in Linux 2.5.48
 .SH CONFORMING TO
diff --git a/man2/get_robust_list.2 b/man2/get_robust_list.2
index d82c16920..9e3bfdc34 100644
--- a/man2/get_robust_list.2
+++ b/man2/get_robust_list.2
@@ -44,7 +44,7 @@ There are no glibc wrappers for these system calls; see NOTES.
 .SH DESCRIPTION
 The robust futex implementation needs to maintain per-thread lists of robust
 futexes which are unlocked when the thread exits.
-These lists are managed in user space; the kernel is only notified about
+These lists are managed in user space; the kernel is notified about only
 the location of the head of the list.
 
 The
diff --git a/man2/get_thread_area.2 b/man2/get_thread_area.2
index 78fb91300..08589e413 100644
--- a/man2/get_thread_area.2
+++ b/man2/get_thread_area.2
@@ -49,7 +49,7 @@ is Linux-specific and should not be used in programs
 that are intended to be portable.
 .SH NOTES
 Glibc does not provide a wrapper for this system call,
-since it is generally intended only for use by threading libraries.
+since it is generally intended for use only by threading libraries.
 In the unlikely event that you want to call it directly, use
 .BR syscall (2).
 .SH SEE ALSO
diff --git a/man2/getcpu.2 b/man2/getcpu.2
index b0783d612..94c0635b2 100644
--- a/man2/getcpu.2
+++ b/man2/getcpu.2
@@ -44,7 +44,7 @@ The third argument to this system call is nowadays unused (see NOTES).
 
 The information placed in
 .I cpu
-is only guaranteed to be current at the time of the call:
+is guaranteed to be current only at the time of the call:
 unless the CPU affinity has been fixed using
 .BR sched_setaffinity (2),
 the kernel might change the CPU at any time.
@@ -128,7 +128,7 @@ migrating threads between CPUs, and so the argument is now ignored.
 .\" With a cache
 .\" .BR getcpu ()
 .\" is faster.
-.\" However, the cached information is only updated once per jiffy (see
+.\" However, the cached information is updated only once per jiffy (see
 .\" .BR time (7)).
 .\" This means that the information could theoretically be out of date,
 .\" although in practice the scheduler's attempt to maintain
diff --git a/man2/getpriority.2 b/man2/getpriority.2
index 4632c99bc..b39bdcf5f 100644
--- a/man2/getpriority.2
+++ b/man2/getpriority.2
@@ -143,7 +143,7 @@ The caller attempted to lower a process priority, but did not
 have the required privilege (on Linux: did not have the
 .B CAP_SYS_NICE
 capability).
-Since Linux 2.6.12, this error only occurs if the caller attempts
+Since Linux 2.6.12, this error occurs only if the caller attempts
 to set a process priority outside the range of the
 .B RLIMIT_NICE
 soft resource limit of the target process; see
diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index 7523ea969..06e71f2f1 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -107,7 +107,7 @@ struct rlimit {
 The soft limit is the value that the kernel enforces for the
 corresponding resource.
 The hard limit acts as a ceiling for the soft limit:
-an unprivileged process may only set its soft limit to a value in the
+an unprivileged process may set only its soft limit to a value in the
 range from 0 up to the hard limit, and (irreversibly) lower its hard limit.
 A privileged process (under Linux: one with the
 .B CAP_SYS_RESOURCE
@@ -304,8 +304,8 @@ fails with the error
 .B RLIMIT_RSS
 Specifies the limit (in pages) of the process's resident set
 (the number of virtual pages resident in RAM).
-This limit only has effect in Linux 2.4.x, x < 30, and there only
-affects calls to
+This limit has effect only in Linux 2.4.x, x < 30, and there
+affects only calls to
 .BR madvise (2)
 specifying
 .BR MADV_WILLNEED .
@@ -351,7 +351,7 @@ Specifies the limit on the number of signals
 that may be queued for the real user ID of the calling process.
 Both standard and real-time signals are counted for the purpose of
 checking this limit.
-However, the limit is only enforced for
+However, the limit is enforced only for
 .BR sigqueue (3);
 it is always possible to use
 .BR kill (2)
diff --git a/man2/getrusage.2 b/man2/getrusage.2
index 9894382d4..362d731fa 100644
--- a/man2/getrusage.2
+++ b/man2/getrusage.2
@@ -196,7 +196,7 @@ is invalid.
 SVr4, 4.3BSD.
 POSIX.1-2001 specifies
 .BR getrusage (),
-but only specifies the fields
+but specifies only the fields
 .I ru_utime
 and
 .IR ru_stime .
diff --git a/man2/ioprio_set.2 b/man2/ioprio_set.2
index e317b4deb..28818ad22 100644
--- a/man2/ioprio_set.2
+++ b/man2/ioprio_set.2
@@ -218,7 +218,7 @@ is the one that is returned by
 or
 .BR clone (2).
 
-These system calls only have an effect when used
+These system calls have an effect only when used
 in conjunction with an I/O scheduler that supports I/O priorities.
 As at kernel 2.6.17 the only such scheduler is the Completely Fair Queuing
 (CFQ) I/O scheduler.
@@ -311,7 +311,7 @@ Permission to change a process's priority is granted or denied based
 on two assertions:
 .TP
 .B "Process ownership"
-An unprivileged process may only set the I/O priority of a process
+An unprivileged process may set only the I/O priority of a process
 whose real UID
 matches the real or effective UID of the calling process.
 A process which has the
diff --git a/man2/kexec_load.2 b/man2/kexec_load.2
index d27bbc797..f820da07e 100644
--- a/man2/kexec_load.2
+++ b/man2/kexec_load.2
@@ -56,9 +56,9 @@ Execute the new kernel automatically on a system crash.
 Preserve the system hardware and
 software states before executing the new kernel.
 This could be used for system suspend.
-This flag is only available if the kernel was configured with
+This flag is available only if the kernel was configured with
 .BR CONFIG_KEXEC_JUMP ,
-and is only effective if
+and is effective only if
 .I nr_segments
 is greater than 0.
 .PP
@@ -154,7 +154,7 @@ which is not currently exported to glibc.
 .\" Check if it got accepted later.
 Therefore, these constants must be defined manually.
 
-This system call is only available if the kernel was configured with
+This system call is available only if the kernel was configured with
 .BR CONFIG_KEXEC .
 .SH SEE ALSO
 .BR reboot (2),
diff --git a/man2/madvise.2 b/man2/madvise.2
index 5814aee3a..9500179e5 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -150,14 +150,14 @@ restoring the default behavior, whereby a mapping is inherited across
 .TP
 .BR MADV_HWPOISON " (Since Linux 2.6.32)
 Poison a page and handle it like a hardware memory corruption.
-This operation is only available for privileged
+This operation is available only for privileged
 .RB ( CAP_SYS_ADMIN )
 processes.
 This operation may result in the calling process receiving a
 .B SIGBUS
 and the page being unmapped.
 This feature is intended for testing of memory error-handling code;
-it is only available if the kernel was configured with
+it is available only if the kernel was configured with
 .BR CONFIG_MEMORY_FAILURE .
 .TP
 .BR MADV_SOFT_OFFLINE " (Since Linux 2.6.33)
@@ -175,7 +175,7 @@ The effect of the
 operation is invisible to (i.e., does not change the semantics of)
 the calling process.
 This feature is intended for testing of memory error-handling code;
-it is only available if the kernel was configured with
+it is available only if the kernel was configured with
 .BR CONFIG_MEMORY_FAILURE .
 .TP
 .BR MADV_MERGEABLE " (since Linux 2.6.32)"
@@ -188,7 +188,7 @@ been marked as mergeable,
 looking for pages with identical content.
 These are replaced by a single write-protected page (which is automatically
 copied if a process later wants to update the content of the page).
-KSM only merges private anonymous pages (see
+KSM merges only private anonymous pages (see
 .BR mmap (2)).
 The KSM feature is intended for applications that generate many
 instances of the same data (e.g., virtualization systems such as KVM).
@@ -200,7 +200,7 @@ The
 .BR MADV_MERGEABLE
 and
 .BR MADV_UNMERGEABLE
-operations are only available if the kernel was configured with
+operations are available only if the kernel was configured with
 .BR CONFIG_KSM .
 .TP
 .BR MADV_UNMERGEABLE " (since Linux 2.6.32)"
@@ -219,7 +219,7 @@ Enables Transparent Huge Pages (THP) for pages in the range specified by
 .I addr
 and
 .IR length .
-Currently, Transparent Huge Pages only work with private anonymous pages (see
+Currently, Transparent Huge Pages work only with private anonymous pages (see
 .BR mmap (2)).
 The kernel will regularly scan the areas marked as huge page candidates
 to replace them with huge pages.
@@ -238,7 +238,7 @@ The
 .BR MADV_HUGEPAGE
 and
 .BR MADV_NOHUGEPAGE
-operations are only available if the kernel was configured with
+operations are available only if the kernel was configured with
 .BR CONFIG_TRANSPARENT_HUGEPAGE .
 .TP
 .BR MADV_NOHUGEPAGE " (since Linux 2.6.38)"
diff --git a/man2/mbind.2 b/man2/mbind.2
index a4d3aa515..ded226f0f 100644
--- a/man2/mbind.2
+++ b/man2/mbind.2
@@ -77,7 +77,7 @@ a memory mapped file, mapped using the
 .BR mmap (2)
 system call with the
 .B MAP_PRIVATE
-flag, pages will only be allocated according to the specified
+flag, pages will be allocated only according to the specified
 policy when the application writes [stores] to the page.
 For anonymous regions, an initial read access will use a shared
 page in the kernel containing all zeros.
@@ -115,7 +115,7 @@ for that region.
 
 By default,
 .BR mbind ()
-only has an effect for new allocations; if the pages inside
+has an effect only for new allocations; if the pages inside
 the range have been already touched before setting the policy,
 then the policy has no effect.
 This default behavior may be overridden by the
@@ -169,7 +169,7 @@ points to a bit mask of nodes containing up to
 bits.
 The bit mask size is rounded to the next multiple of
 .IR "sizeof(unsigned long)" ,
-but the kernel will only use bits up to
+but the kernel will use bits only up to
 .IR maxnode .
 A NULL value of
 .I nodemask
@@ -453,7 +453,7 @@ is ignored on huge page mappings.
 .B MPOL_MF_MOVE
 and
 .B MPOL_MF_MOVE_ALL
-are only available on Linux 2.6.16 and later.
+are available only on Linux 2.6.16 and later.
 .SH SEE ALSO
 .BR get_mempolicy (2),
 .BR getcpu (2),
diff --git a/man2/migrate_pages.2 b/man2/migrate_pages.2
index b4788c123..e88648a90 100644
--- a/man2/migrate_pages.2
+++ b/man2/migrate_pages.2
@@ -81,7 +81,7 @@ is 0, then
 .BR migrate_pages ()
 moves pages of the calling process.
 
-Pages shared with another process will only be moved if the initiating
+Pages shared with another process will be moved only if the initiating
 process has the
 .B CAP_SYS_NICE
 privilege.
diff --git a/man2/mknod.2 b/man2/mknod.2
index ffba9e0a1..5ce41d3f3 100644
--- a/man2/mknod.2
+++ b/man2/mknod.2
@@ -164,7 +164,7 @@ FIFO (named pipe), or UNIX domain socket, and the caller
 is not privileged (Linux: does not have the
 .B CAP_MKNOD
 capability);
-.\" For UNIX domain sockets and regular files, EPERM is only returned in
+.\" For UNIX domain sockets and regular files, EPERM is returned only in
 .\" Linux 2.2 and earlier; in Linux 2.4 and later, unprivileged can
 .\" use mknod() to make these files.
 also returned if the file system containing
diff --git a/man2/mmap.2 b/man2/mmap.2
index a78998ece..62244054b 100644
--- a/man2/mmap.2
+++ b/man2/mmap.2
@@ -142,7 +142,7 @@ In addition, zero or more of the following values can be ORed in
 .TP
 .BR MAP_32BIT " (since Linux 2.4.20, 2.6)"
 Put the mapping into the first 2 Gigabytes of the process address space.
-This flag is only supported on x86-64, for 64-bit programs.
+This flag is supported only on x86-64, for 64-bit programs.
 It was added to allow thread stacks to be allocated somewhere
 in the first 2GB of memory,
 so as to improve context-switch performance on some early
@@ -181,7 +181,7 @@ The use of
 .B MAP_ANONYMOUS
 in conjunction with
 .B MAP_SHARED
-is only supported on Linux since kernel 2.4.
+is supported on Linux only since kernel 2.4.
 .TP
 .B MAP_DENYWRITE
 This flag is ignored.
@@ -244,7 +244,7 @@ This flag is ignored in older kernels.
 Only meaningful in conjunction with
 .BR MAP_POPULATE .
 Don't perform read-ahead:
-only create page tables entries for pages
+create page tables entries only for pages
 that are already present in RAM.
 Since Linux 2.6.23, this flag causes
 .BR MAP_POPULATE
@@ -267,7 +267,7 @@ See also the discussion of the file
 .I /proc/sys/vm/overcommit_memory
 in
 .BR proc (5).
-In kernels before 2.6, this flag only had effect for
+In kernels before 2.6, this flag had effect only for
 private writable mappings.
 .TP
 .BR MAP_POPULATE " (since Linux 2.5.46)"
@@ -275,7 +275,7 @@ Populate (prefault) page tables for a mapping.
 For a file mapping, this causes read-ahead on the file.
 Later accesses to the mapping will not be blocked by page faults.
 .BR MAP_POPULATE
-is only supported for private mappings since Linux 2.6.23.
+is supported for private mappings only since Linux 2.6.23.
 .TP
 .BR MAP_STACK " (since Linux 2.6.27)"
 Allocate the mapping at an address suitable for a process
@@ -293,7 +293,7 @@ support can later be transparently implemented for glibc.
 .BR MAP_UNINITIALIZED " (since Linux 2.6.33)"
 Don't clear anonymous pages.
 This flag is intended to improve performance on embedded devices.
-This flag is only honored if the kernel was configured with the
+This flag is honored only if the kernel was configured with the
 .B CONFIG_MMAP_ALLOW_UNINITIALIZED
 option.
 Because of the security implications,
@@ -592,7 +592,7 @@ at any moment when the system runs out of memory.
 
 In kernels before 2.6.7, the
 .B MAP_POPULATE
-flag only has effect if
+flag has effect only if
 .I prot
 is specified as
 .BR PROT_NONE .
diff --git a/man2/mount.2 b/man2/mount.2
index 7698b1761..29802d215 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -208,7 +208,7 @@ Mount file system read-only.
 .TP
 .BR MS_RELATIME " (Since Linux 2.6.20)"
 When a file on this file system is accessed,
-only update the file's last access time (atime) if the current value
+update the file's last access time (atime) only if the current value
 of atime is less than or equal to the file's last modification time (mtime)
 or last status change time (ctime).
 This option is useful for programs, such as
@@ -411,7 +411,7 @@ The definitions of
 .BR MS_RELATIME ,
 and
 .BR MS_STRICTATIME
-were only added to glibc headers in version 2.12.
+were added to glibc headers in version 2.12.
 .\" FIXME: Definitions of the so-far-undocumented MS_UNBINDABLE, MS_PRIVATE,
 .\"  MS_SHARED, and MS_SLAVE were (also) only added to glibc headers in 2.12.
 .SH "CONFORMING TO"
diff --git a/man2/move_pages.2 b/man2/move_pages.2
index f17d69422..f6a622810 100644
--- a/man2/move_pages.2
+++ b/man2/move_pages.2
@@ -84,7 +84,7 @@ pages that need to be moved.
 
 .I status
 is an array of integers that return the status of each page.
-The array only contains valid values if
+The array contains valid values only if
 .BR move_pages ()
 did not return an error.
 
@@ -108,7 +108,7 @@ array.
 Identifies the node on which the page resides.
 .TP
 .B -EACCES
-The page is mapped by multiple processes and can only be moved if
+The page is mapped by multiple processes and can be moved only if
 .B MPOL_MF_MOVE_ALL
 is specified.
 .TP
diff --git a/man2/mprotect.2 b/man2/mprotect.2
index 220f947d4..f8e47d9b9 100644
--- a/man2/mprotect.2
+++ b/man2/mprotect.2
@@ -140,7 +140,7 @@ implies
 POSIX.1-2001 says that an implementation may permit access
 other than that specified in
 .IR prot ,
-but at a minimum can only allow write access if
+but at a minimum can allow write access only if
 .B PROT_WRITE
 has been set, and must not allow any access if
 .B PROT_NONE
diff --git a/man2/open.2 b/man2/open.2
index 942af07cc..abfa0ad08 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -175,7 +175,7 @@ generate a signal
 by default, but this can be changed via
 .BR fcntl (2))
 when input or output becomes possible on this file descriptor.
-This feature is only available for terminals, pseudoterminals,
+This feature is available only for terminals, pseudoterminals,
 sockets, and (since Linux 2.6) pipes and FIFOs.
 See
 .BR fcntl (2)
@@ -239,7 +239,7 @@ the process's
 .I umask
 in the usual way: The permissions of the created file are
 .IR "(mode\ &\ ~umask)" .
-Note that this mode only applies to future accesses of the
+Note that this mode applies only to future accesses of the
 newly created file; the
 .BR open ()
 call that creates a read-only file may well return a read/write
@@ -356,7 +356,7 @@ fails with the error
 
 On NFS,
 .B O_EXCL
-is only supported when using NFSv3 or later on kernel 2.6 or later.
+is supported only when using NFSv3 or later on kernel 2.6 or later.
 In NFS environments where
 .B O_EXCL
 support is not provided, programs that rely on it
@@ -681,7 +681,7 @@ to mean:
 check for read and write permission on the file and return a descriptor
 that can't be used for reading or writing.
 This nonstandard access mode is used by some Linux drivers to return a
-descriptor that is only to be used for device-specific
+descriptor that is to be used only for device-specific
 .BR ioctl (2)
 operations.
 .\" See for example util-linux's disk-utils/setfdprm.c
@@ -711,7 +711,7 @@ corresponding to the flags
 .BR O_DSYNC ,
 and
 .BR O_RSYNC .
-Currently (2.6.31), Linux only implements
+Currently (2.6.31), Linux implements only
 .BR O_SYNC ,
 but glibc maps
 .B O_DSYNC
@@ -860,7 +860,7 @@ Older kernels, or
 kernels configured in certain ways, may not support this combination.
 The NFS protocol does not support passing the flag to the server, so
 .B O_DIRECT
-I/O will only bypass the page cache on the client; the server may
+I/O will bypass the page cache only on the client; the server may
 still cache the I/O.
 The client asks the server to make the I/O
 synchronous to preserve the synchronous semantics of
diff --git a/man2/pause.2 b/man2/pause.2
index f3d707a56..2b011a17a 100644
--- a/man2/pause.2
+++ b/man2/pause.2
@@ -41,7 +41,7 @@ until a signal is delivered that either terminates the process or causes
 the invocation of a signal-catching function.
 .SH RETURN VALUE
 .BR pause ()
-only returns when a signal was caught and the
+returns only when a signal was caught and the
 signal-catching function returned.
 In this case
 .BR pause ()
diff --git a/man2/pciconfig_read.2 b/man2/pciconfig_read.2
index 18007d266..bcf062b4a 100644
--- a/man2/pciconfig_read.2
+++ b/man2/pciconfig_read.2
@@ -97,7 +97,7 @@ The system has not implemented these calls
 not defined).
 .TP
 .B EOPNOTSUPP
-This return value is only valid for
+This return value is valid only for
 .BR pciconfig_iobase ().
 It is returned if the value for
 .I which
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index f80cf63ef..f3850f00a 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -138,8 +138,8 @@ being set to the fd of the group leader.
 (A single event on its own is created with
 .IR group_fd " = \-1"
 and is considered to be a group with only 1 member.)
-An event group is scheduled onto the CPU as a unit: it will only
-be put onto the CPU if all of the events in the group can be put onto
+An event group is scheduled onto the CPU as a unit: it will
+be put onto the CPU ionly if all of the events in the group can be put onto
 the CPU.
 This means that the values of the member events can be
 meaningfully compared, added, divided (to get ratios), etc., with each
@@ -180,7 +180,7 @@ then a file descriptor opened on
 must be passed as the
 .I pid
 parameter.
-cgroup monitoring is only available
+cgroup monitoring is available only
 for system-wide events and may therefore require extra permissions.
 .P
 The
@@ -461,7 +461,7 @@ These required disk I/O to handle.
 This counts the number of alignment faults.
 These happen when unaligned memory accesses happen; the kernel
 can handle these but it reduces performance.
-This only happens on some architectures (never on x86).
+This happens only on some architectures (never on x86).
 .TP
 .BR PERF_COUNT_SW_EMULATION_FAULTS " (Since Linux 2.6.33)"
 This counts the number of emulation faults.
@@ -708,7 +708,7 @@ The
 .I inherit
 bit specifies that this counter should count events of child
 tasks as well as the task specified.
-This only applies to new children, not to any existing children at
+This applies only to new children, not to any existing children at
 the time the counter is created (nor to any new children of
 existing children).
 
@@ -722,7 +722,7 @@ The
 .I pinned
 bit specifies that the counter should always be on the CPU if at all
 possible.
-It only applies to hardware counters and only to group leaders.
+It applies only to hardware counters and only to group leaders.
 If a pinned counter cannot be put onto the CPU (e.g., because there are
 not enough hardware counters or because of a conflict with some other
 event), then the counter goes into an 'error' state, where reads
@@ -782,7 +782,7 @@ is used when setting up the sampling interval.
 .IR "inherit_stat"
 This bit enables saving of event counts on context switch for
 inherited tasks.
-This is only meaningful if the
+This is meaningful only if the
 .I inherit
 field is set.
 .TP
@@ -1040,7 +1040,7 @@ Total time the event was enabled and running.
 Normally these are the same.
 If more events are started
 than available counter slots on the PMU, then multiplexing
-happens and events only run part of the time.
+happens and events run only part of the time.
 In that case the
 .I time_enabled
 and
@@ -1663,8 +1663,8 @@ file descriptor argument.
 Enabling or disabling the leader of a group enables or disables the
 entire group; that is, while the group leader is disabled, none of the
 counters in the group will count.
-Enabling or disabling a member of a group other than the leader only
-affects that counter; disabling a non-leader
+Enabling or disabling a member of a group other than the leader
+affects only that counter; disabling a non-leader
 stops that counter from counting but doesn't affect any other counter.
 
 The ioctl argument is ignored.
@@ -1686,7 +1686,7 @@ Using an argument of 0 is considered undefined behavior.
 .B PERF_EVENT_IOC_RESET
 Reset the event count specified by the
 file descriptor argumentto zero.
-This only resets the counts; there is no way to reset the
+This resets only the counts; there is no way to reset the
 multiplexing
 .I time_enabled
 or
@@ -1727,7 +1727,7 @@ operations.
 This applies to all counters on the current process, whether created by
 this process or by another, and does not affect any counters that this
 process has created on other processes.
-It only enables or disables
+It enables or disables only
 the group leaders, not any other members in the groups.
 .SS perf_event related configuration files
 Files in
diff --git a/man2/prctl.2 b/man2/prctl.2
index f6bfc38c0..5403375a9 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -305,7 +305,7 @@ in the location pointed to by
 .BR PR_SET_PTRACER " (since Linux 3.4)"
 .\" commit 2d514487faf188938a4ee4fb3464eeecfbdcf8eb
 .\" commit bf06189e4d14641c0148bea16e9dd24943862215
-This is only meaningful when the Yama LSM is enabled and in mode 1
+This is meaningful only when the Yama LSM is enabled and in mode 1
 ("restricted ptrace", visible via
 .IR /proc/sys/kernel/yama/ptrace_scope ).
 When a "ptracer process ID" is passed in \fIarg2\fP,
@@ -357,7 +357,7 @@ signal.
 Strict secure computing mode is useful for number-crunching applications
 that may need to execute untrusted byte code,
 perhaps obtained by reading from a pipe or socket.
-This operation is only available
+This operation is available only
 if the kernel is configured with
 .B CONFIG_SECCOMP
 enabled.
@@ -373,7 +373,7 @@ This argument is a pointer to
 .IR "struct sock_fprog" ;
 it can be designed to filter
 arbitrary system calls and system call arguments.
-This mode is only available if the kernel is configured with
+This mode is available only if the kernel is configured with
 .B CONFIG_SECCOMP_FILTER
 enabled.
 
@@ -405,7 +405,7 @@ call will cause a
 signal to be sent to the process.
 If the caller is in filter mode, and this system call is allowed by the
 seccomp filters, it returns 2.
-This operation is only available
+This operation is available only
 if the kernel is configured with
 .B CONFIG_SECCOMP
 enabled.
@@ -613,7 +613,7 @@ Early kill means that the thread receives a
 .B SIGBUS
 signal as soon as hardware memory corruption is detected inside
 its address space.
-In late kill mode, the process is only killed when it accesses a corrupted page.
+In late kill mode, the process is killed only when it accesses a corrupted page.
 See
 .BR sigaction (2)
 for more information on the
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 959e6b85f..0d77e3fda 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -565,7 +565,7 @@ has been stopped by a
 (or other stopping signal).
 See the "group-stop" subsection for additional information.
 .B PTRACE_LISTEN
-only works on tracees attached by
+works only on tracees attached by
 .BR PTRACE_SEIZE .
 .TP
 .B PTRACE_KILL
diff --git a/man2/query_module.2 b/man2/query_module.2
index 24627a5b7..8481c5a90 100644
--- a/man2/query_module.2
+++ b/man2/query_module.2
@@ -166,7 +166,7 @@ is set to the minimum size needed.
 is not supported in this version of the kernel
 (e.g., the kernel is version 2.6 or later).
 .SH VERSIONS
-This system call is only present on Linux up until kernel 2.4;
+This system call is present on Linux only up until kernel 2.4;
 it was removed in Linux 2.6.
 .\" Removed in Linux 2.5.48
 .SH CONFORMING TO
diff --git a/man2/read.2 b/man2/read.2
index b17aadc4f..ed318e462 100644
--- a/man2/read.2
+++ b/man2/read.2
@@ -173,8 +173,8 @@ or to return the number of bytes already read.
 .SH CONFORMING TO
 SVr4, 4.3BSD, POSIX.1-2001.
 .SH NOTES
-On NFS file systems, reading small amounts of data will only update the
-timestamp the first time, subsequent calls may not do so.
+On NFS file systems, reading small amounts of data will update the
+timestamp only the first time, subsequent calls may not do so.
 This is caused
 by client side attribute caching, because most if not all NFS clients
 leave st_atime (last file access time)
diff --git a/man2/reboot.2 b/man2/reboot.2
index fed33b8c0..b25d62c98 100644
--- a/man2/reboot.2
+++ b/man2/reboot.2
@@ -111,7 +111,7 @@ data will be lost.
 .BR LINUX_REBOOT_CMD_KEXEC " (since Linux 2.6.13)"
 Execute a kernel that has been loaded earlier with
 .BR kexec_load (2).
-This option is only available if the kernel was configured with
+This option is available only if the kernel was configured with
 .BR CONFIG_KEXEC .
 .TP
 .B LINUX_REBOOT_CMD_POWER_OFF
diff --git a/man2/recv.2 b/man2/recv.2
index 38ae243ce..82c871199 100644
--- a/man2/recv.2
+++ b/man2/recv.2
@@ -352,7 +352,7 @@ struct cmsghdr {
 .fi
 .in
 .PP
-Ancillary data should only be accessed by the macros defined in
+Ancillary data should be accessed only by the macros defined in
 .BR cmsg (3).
 .PP
 As an example, Linux uses this ancillary data mechanism to pass extended
@@ -446,7 +446,7 @@ does not refer to a socket.
 4.4BSD (these function calls first appeared in 4.2BSD),
 POSIX.1-2001.
 .LP
-POSIX.1-2001 only describes the
+POSIX.1-2001 describes only the
 .BR MSG_OOB ,
 .BR MSG_PEEK ,
 and
diff --git a/man2/s390_runtime_instr.2 b/man2/s390_runtime_instr.2
index 8a5ba423a..036e808b5 100644
--- a/man2/s390_runtime_instr.2
+++ b/man2/s390_runtime_instr.2
@@ -79,7 +79,7 @@ The run-time instrumentation facility is not available.
 .SH VERSIONS
 This system call is available since Linux 3.7.
 .SH CONFORMING TO
-This Linux-specific system call is only available on the s390 architecture.
+This Linux-specific system call is available only on the s390 architecture.
 The run-time instrumentation facility is available beginning with System z EC12.
 .SH NOTES
 Glibc does not provide a wrapper for this system call, use
diff --git a/man2/sched_setscheduler.2 b/man2/sched_setscheduler.2
index bfda09b9e..f9919999f 100644
--- a/man2/sched_setscheduler.2
+++ b/man2/sched_setscheduler.2
@@ -125,7 +125,7 @@ Processes scheduled under one of the real-time policies
 \fIsched_priority\fP value in the range 1 (low) to 99 (high).
 (As the numbers imply, real-time processes always have higher priority
 than normal processes.)
-Note well: POSIX.1-2001 only requires an implementation to support a
+Note well: POSIX.1-2001 requires an implementation to support only a
 minimum 32 distinct priority levels for the real-time policies,
 and some systems supply just this minimum.
 Portable programs should use
@@ -148,11 +148,11 @@ All scheduling is preemptive: if a process with a higher static
 priority becomes ready to run, the currently running process
 will be preempted and
 returned to the wait list for its static priority level.
-The scheduling policy only determines the
-ordering within the list of runnable processes with equal static
+The scheduling policy determines the
+ordering only within the list of runnable processes with equal static
 priority.
 .SS SCHED_FIFO: First in-first out scheduling
-\fBSCHED_FIFO\fP can only be used with static priorities higher than
+\fBSCHED_FIFO\fP can be used only with static priorities higher than
 0, which means that when a \fBSCHED_FIFO\fP processes becomes runnable,
 it will always immediately preempt any currently running
 \fBSCHED_OTHER\fP, \fBSCHED_BATCH\fP, or \fBSCHED_IDLE\fP process.
@@ -199,7 +199,7 @@ preempted by a higher priority process, or it calls
 \fBSCHED_RR\fP is a simple enhancement of \fBSCHED_FIFO\fP.
 Everything
 described above for \fBSCHED_FIFO\fP also applies to \fBSCHED_RR\fP,
-except that each process is only allowed to run for a maximum time
+except that each process is allowed to run only for a maximum time
 quantum.
 If a \fBSCHED_RR\fP process has been running for a time
 period equal to or longer than the time quantum, it will be put at the
@@ -215,7 +215,7 @@ retrieved using
 .\" by the process nice value -- MTK
 .\"
 .SS SCHED_OTHER: Default Linux time-sharing scheduling
-\fBSCHED_OTHER\fP can only be used at static priority 0.
+\fBSCHED_OTHER\fP can be used at only static priority 0.
 \fBSCHED_OTHER\fP is the standard Linux time-sharing scheduler that is
 intended for all processes that do not require the special
 real-time mechanisms.
@@ -232,7 +232,7 @@ This ensures fair progress among all \fBSCHED_OTHER\fP processes.
 .\"
 .SS SCHED_BATCH: Scheduling batch processes
 (Since Linux 2.6.16.)
-\fBSCHED_BATCH\fP can only be used at static priority 0.
+\fBSCHED_BATCH\fP can be used only at static priority 0.
 This policy is similar to \fBSCHED_OTHER\fP in that it schedules
 the process according to its dynamic priority
 (based on the nice value).
@@ -253,7 +253,7 @@ interactivity causing extra preemptions (between the workload's tasks).
 .\"
 .SS SCHED_IDLE: Scheduling very low priority jobs
 (Since Linux 2.6.23.)
-\fBSCHED_IDLE\fP can only be used at static priority 0;
+\fBSCHED_IDLE\fP can be used only at static priority 0;
 the process nice value has no influence for this policy.
 
 This policy is intended for running jobs at extremely low
@@ -299,7 +299,7 @@ the nice value is reset to zero in child processes.
 After the
 .BR SCHED_RESET_ON_FORK
 flag has been enabled,
-it can only be reset if the process has the
+it can be reset only if the process has the
 .BR CAP_SYS_NICE
 capability.
 This flag is disabled in child processes created by
@@ -317,7 +317,7 @@ processes can set a nonzero static priority (i.e., set a real-time
 scheduling policy).
 The only change that an unprivileged process can make is to set the
 .B SCHED_OTHER
-policy, and this can only be done if the effective user ID of the caller of
+policy, and this can be done only if the effective user ID of the caller of
 .BR sched_setscheduler ()
 matches the real or effective user ID of the target process
 (i.e., the process specified by
diff --git a/man2/select_tut.2 b/man2/select_tut.2
index 7e5f3cfbd..1ca5d785d 100644
--- a/man2/select_tut.2
+++ b/man2/select_tut.2
@@ -384,7 +384,7 @@ If they do read/write the full amount, it's
 because you have a low traffic load and a fast stream.
 This is not always going to be the case.
 You should cope with the case of your
-functions only managing to send or receive a single byte.
+functions managing to send or receive only a single byte.
 .TP
 6.
 Never read/write only in single bytes at a time unless you are really
@@ -481,7 +481,7 @@ follows:
     select(0, NULL, NULL, NULL, &tv);
 .fi
 .PP
-This is only guaranteed to work on UNIX systems, however.
+This is guaranteed to work only on UNIX systems, however.
 .SH RETURN VALUE
 On success,
 .BR select ()
diff --git a/man2/send.2 b/man2/send.2
index 778efba56..20198578d 100644
--- a/man2/send.2
+++ b/man2/send.2
@@ -173,17 +173,17 @@ Only valid on
 .B SOCK_DGRAM
 and
 .B SOCK_RAW
-sockets and currently only implemented for IPv4 and IPv6.
+sockets and currently implemented only for IPv4 and IPv6.
 See
 .BR arp (7)
 for details.
 .TP
 .B MSG_DONTROUTE
-Don't use a gateway to send out the packet, only send to hosts on
+Don't use a gateway to send out the packet, send to hosts only on
 directly connected networks.
 This is usually used only
 by diagnostic or routing programs.
-This is only defined for protocol
+This is defined only for protocol
 families that route; packet sockets don't.
 .TP
 .BR MSG_DONTWAIT " (since Linux 2.2)"
@@ -212,7 +212,7 @@ with the difference that this flag can be set on a per-call basis.
 
 Since Linux 2.6, this flag is also supported for UDP sockets, and informs
 the kernel to package all of the data sent in calls with this flag set
-into a single datagram which is only transmitted when a call is performed
+into a single datagram which is transmitted only when a call is performed
 that does not specify this flag.
 (See also the
 .B UDP_CORK
@@ -369,7 +369,7 @@ is set.
 4.4BSD, SVr4, POSIX.1-2001.
 These function calls appeared in 4.2BSD.
 .LP
-POSIX.1-2001 only describes the
+POSIX.1-2001 describes only the
 .B MSG_OOB
 and
 .B MSG_EOR
diff --git a/man2/set_mempolicy.2 b/man2/set_mempolicy.2
index 2f8e57af9..48c31f4ed 100644
--- a/man2/set_mempolicy.2
+++ b/man2/set_mempolicy.2
@@ -68,7 +68,7 @@ and of memory mapped files mapped using the
 call with the
 .B MAP_SHARED
 flag, regardless of the access type.
-The policy is only applied when a new page is allocated
+The policy is applied only when a new page is allocated
 for the process.
 For anonymous memory this is when the page is first
 touched by the application.
@@ -117,7 +117,7 @@ points to a bit mask of node IDs that contains up to
 bits.
 The bit mask size is rounded to the next multiple of
 .IR "sizeof(unsigned long)" ,
-but the kernel will only use bits up to
+but the kernel will use bits only up to
 .IR maxnode .
 A NULL value of
 .I nodemask
diff --git a/man2/setfsgid.2 b/man2/setfsgid.2
index c0d74c91d..dbaae163e 100644
--- a/man2/setfsgid.2
+++ b/man2/setfsgid.2
@@ -53,7 +53,7 @@ Explicit calls to
 .BR setfsuid (2)
 and
 .BR setfsgid ()
-are usually only used by programs such as the Linux NFS server that
+are usually used only by programs such as the Linux NFS server that
 need to change what user and group ID is used for file access without a
 corresponding change in the real and effective user and group IDs.
 A change in the normal user IDs for a program such as the NFS server
@@ -61,7 +61,7 @@ is a security hole that can expose it to unwanted signals.
 (But see below.)
 
 .BR setfsgid ()
-will only succeed if the caller is the superuser or if
+will succeed only if the caller is the superuser or if
 .I fsgid
 matches either the real group ID, effective group ID,
 saved set-group-ID, or the current value of
diff --git a/man2/setfsuid.2 b/man2/setfsuid.2
index b7379814a..a8add872d 100644
--- a/man2/setfsuid.2
+++ b/man2/setfsuid.2
@@ -53,7 +53,7 @@ Explicit calls to
 .BR setfsuid ()
 and
 .BR setfsgid (2)
-are usually only used by programs such as the Linux NFS server that
+are usually used only by programs such as the Linux NFS server that
 need to change what user and group ID is used for file access without a
 corresponding change in the real and effective user and group IDs.
 A change in the normal user IDs for a program such as the NFS server
@@ -61,7 +61,7 @@ is a security hole that can expose it to unwanted signals.
 (But see below.)
 
 .BR setfsuid ()
-will only succeed if the caller is the superuser or if
+will succeed only if the caller is the superuser or if
 .I fsuid
 matches either the real user ID, effective user ID, saved set-user-ID, or
 the current value of
diff --git a/man2/sigaction.2 b/man2/sigaction.2
index 8f94319c8..7a362c0c2 100644
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@@ -182,7 +182,7 @@ or resume (i.e., they receive
 .BR SIGCONT )
 (see
 .BR wait (2)).
-This flag is only meaningful when establishing a handler for
+This flag is meaningful only when establishing a handler for
 .BR SIGCHLD .
 .TP
 .BR SA_NOCLDWAIT " (since Linux 2.6)"
@@ -194,7 +194,7 @@ is
 do not transform children into zombies when they terminate.
 See also
 .BR waitpid (2).
-This flag is only meaningful when establishing a handler for
+This flag is meaningful only when establishing a handler for
 .BR SIGCHLD ,
 or when setting that signal's disposition to
 .BR SIG_DFL .
@@ -214,7 +214,7 @@ on some other implementations, it is not.
 .B SA_NODEFER
 Do not prevent the signal from being received from within its own signal
 handler.
-This flag is only meaningful when establishing a signal handler.
+This flag is meaningful only when establishing a signal handler.
 .B SA_NOMASK
 is an obsolete, nonstandard synonym for this flag.
 .TP
@@ -222,18 +222,18 @@ is an obsolete, nonstandard synonym for this flag.
 Call the signal handler on an alternate signal stack provided by
 .BR sigaltstack (2).
 If an alternate stack is not available, the default stack will be used.
-This flag is only meaningful when establishing a signal handler.
+This flag is meaningful only when establishing a signal handler.
 .TP
 .BR SA_RESETHAND
 Restore the signal action to the default upon entry to the signal handler.
-This flag is only meaningful when establishing a signal handler.
+This flag is meaningful only when establishing a signal handler.
 .B SA_ONESHOT
 is an obsolete, nonstandard synonym for this flag.
 .TP
 .B SA_RESTART
 Provide behavior compatible with BSD signal semantics by making certain
 system calls restartable across signals.
-This flag is only meaningful when establishing a signal handler.
+This flag is meaningful only when establishing a signal handler.
 See
 .BR signal (7)
 for a discussion of system call restarting.
@@ -244,7 +244,7 @@ In this case,
 .I sa_sigaction
 should be set instead of
 .IR sa_handler .
-This flag is only meaningful when establishing a signal handler.
+This flag is meaningful only when establishing a signal handler.
 .\" (The
 .\" .I sa_sigaction
 .\" field was added in Linux 2.1.86.)
@@ -293,8 +293,8 @@ siginfo_t {
 are defined for all signals.
 .RI ( si_errno
 is generally unused on Linux.)
-The rest of the struct may be a union, so that one should only
-read the fields that are meaningful for the given signal:
+The rest of the struct may be a union, so that one should
+read only the fields that are meaningful for the given signal:
 .IP * 2
 Signals sent with
 .BR kill (2)
@@ -719,7 +719,7 @@ signal and perform a
 .BR wait (2)
 or similar.
 .PP
-POSIX.1-1990 only specified
+POSIX.1-1990 specified only
 .BR SA_NOCLDSTOP .
 POSIX.1-2001 added
 .BR SA_NOCLDWAIT ,
diff --git a/man2/spu_create.2 b/man2/spu_create.2
index 04db743fc..41d549381 100644
--- a/man2/spu_create.2
+++ b/man2/spu_create.2
@@ -248,7 +248,7 @@ The
 .BR spu_create ()
 system call was added to Linux in kernel 2.6.16.
 .SH CONFORMING TO
-This call is Linux-specific and only implemented on the PowerPC
+This call is Linux-specific and implemented only on the PowerPC
 architecture.
 Programs using this system call are not portable.
 .SH NOTES
diff --git a/man2/spu_run.2 b/man2/spu_run.2
index 0632f4601..b212b20d8 100644
--- a/man2/spu_run.2
+++ b/man2/spu_run.2
@@ -144,7 +144,7 @@ SPU has tried to access an invalid channel.
 The bits masked with this value contain the code returned from a
 .BR stop-and-signal
 instruction.
-These bits are only valid if the 0x02 bit is set.
+These bits are valid only if the 0x02 bit is set.
 .PP
 If
 .BR spu_run ()
@@ -190,7 +190,7 @@ The
 .BR spu_run ()
 system call was added to Linux in kernel 2.6.16.
 .SH CONFORMING TO
-This call is Linux-specific and only implemented by the PowerPC
+This call is Linux-specific and implemented only by the PowerPC
 architecture.
 Programs using this system call are not portable.
 .SH NOTES
diff --git a/man2/stime.2 b/man2/stime.2
index 022b938f6..afecfba4b 100644
--- a/man2/stime.2
+++ b/man2/stime.2
@@ -49,7 +49,7 @@ The time, pointed
 to by \fIt\fP, is measured in seconds since the
 Epoch, 1970-01-01 00:00:00 +0000 (UTC).
 .BR stime ()
-may only be executed by the superuser.
+may be executed only by the superuser.
 .SH RETURN VALUE
 On success, zero is returned.
 On error, \-1 is returned, and
diff --git a/man2/swapon.2 b/man2/swapon.2
index 766ad9b0a..b933608e5 100644
--- a/man2/swapon.2
+++ b/man2/swapon.2
@@ -80,7 +80,7 @@ if the swap device supports the discard or trim operation.
 but often it does not.)
 See also NOTES.
 .PP
-These functions may only be used by a privileged process (one having the
+These functions may be used only by a privileged process (one having the
 .B CAP_SYS_ADMIN
 capability).
 .SS Priority
diff --git a/man2/syslog.2 b/man2/syslog.2
index ed143c77f..1641c1285 100644
--- a/man2/syslog.2
+++ b/man2/syslog.2
@@ -94,7 +94,7 @@ at most \fIlen\fP bytes into the buffer pointed to by
 .IR bufp .
 The call returns the number of bytes read.
 Bytes read from the log disappear from the log buffer:
-the information can only be read once.
+the information can be read only once.
 This is the function executed by the kernel when a user program reads
 .IR /proc/kmsg .
 .TP
diff --git a/man2/timer_create.2 b/man2/timer_create.2
index 62d2a9700..67f00070f 100644
--- a/man2/timer_create.2
+++ b/man2/timer_create.2
@@ -148,7 +148,7 @@ field specifies a kernel thread ID, that is, the value returned by
 .BR clone (2)
 or
 .BR gettid (2).
-This flag is only intended for use by threading libraries.
+This flag is intended only for use by threading libraries.
 .PP
 Specifying
 .I sevp
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index ad7e9a9fc..d64255a8a 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -109,7 +109,7 @@ This allows an application to avoid the overhead of making
 a system call to obtain the overrun count,
 but is a nonportable extension to POSIX.1-2001.
 
-POSIX.1-2001 only discusses timer overruns in the context of
+POSIX.1-2001 discusses timer overruns only in the context of
 timer notifications using signals.
 .\" FIXME . Austin bug filed, 11 Feb 09
 .SH BUGS
diff --git a/man2/times.2 b/man2/times.2
index d2e0b2289..bcded0329 100644
--- a/man2/times.2
+++ b/man2/times.2
@@ -136,8 +136,8 @@ are automatically included in the
 .I tms_cstime
 and
 .I tms_cutime
-fields, although POSIX.1-2001 says that this should only happen
-if the calling process
+fields, although POSIX.1-2001 says that this should happen
+only if the calling process
 .BR wait (2)s
 on its children.
 This nonconformance is rectified in Linux 2.6.9 and later.
diff --git a/man2/tkill.2 b/man2/tkill.2
index eb586264c..968c39c4d 100644
--- a/man2/tkill.2
+++ b/man2/tkill.2
@@ -48,14 +48,14 @@ in the thread group
 .IR tgid .
 (By contrast,
 .BR kill (2)
-can only be used to send a signal to a process (i.e., thread group)
+can be used to send a signal only to a process (i.e., thread group)
 as a whole, and the signal will be delivered to an arbitrary
 thread within that process.)
 
 .BR tkill ()
 is an obsolete predecessor to
 .BR tgkill ().
-It only allows the target thread ID to be specified,
+It allows only the target thread ID to be specified,
 which may result in the wrong thread being signaled if a thread
 terminates and its thread ID is recycled.
 Avoid using this system call.
diff --git a/man2/umount.2 b/man2/umount.2
index 92c79090d..d2cabac07 100644
--- a/man2/umount.2
+++ b/man2/umount.2
@@ -152,7 +152,7 @@ The caller does not have the required privileges.
 and
 .BR MNT_EXPIRE
 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=10092
-are only available in glibc since version 2.11.
+are available in glibc since version 2.11.
 .SH CONFORMING TO
 These functions are Linux-specific and should not be used in
 programs intended to be portable.
diff --git a/man2/unimplemented.2 b/man2/unimplemented.2
index d8b329720..23f957a86 100644
--- a/man2/unimplemented.2
+++ b/man2/unimplemented.2
@@ -52,7 +52,7 @@ Some system calls, like
 .BR iopl (2),
 and
 .BR vm86 (2)
-only exist on certain architectures.
+exist only on certain architectures.
 
 Some system calls, like
 .BR ipc (2),
@@ -60,6 +60,6 @@ Some system calls, like
 .BR init_module (2),
 and
 .BR delete_module (2)
-only exist when the Linux kernel was built with support for them.
+exist only when the Linux kernel was built with support for them.
 .SH SEE ALSO
 .BR syscalls (2)
diff --git a/man2/ustat.2 b/man2/ustat.2
index c83bbd449..b8d83598d 100644
--- a/man2/ustat.2
+++ b/man2/ustat.2
@@ -95,7 +95,7 @@ SVr4.
 .\" but has no ENOSYS condition.
 .SH NOTES
 .BR ustat ()
-is deprecated and has only been provided for compatibility.
+is deprecated and has been provided only for compatibility.
 All new programs should use
 .BR statfs (2)
 instead.
diff --git a/man2/vm86.2 b/man2/vm86.2
index 3613ba0bf..ce8177c04 100644
--- a/man2/vm86.2
+++ b/man2/vm86.2
@@ -67,7 +67,7 @@ architecture.
 .B EPERM
 Saved kernel stack exists.
 (This is a kernel sanity check; the saved
-stack should only exist within vm86 mode itself.)
+stack should exist only within vm86 mode itself.)
 .SH CONFORMING TO
 This call is specific to Linux on 32-bit Intel processors,
 and should not be used in programs intended to be portable.
diff --git a/man2/wait.2 b/man2/wait.2
index 01cd2f2f0..590821472 100644
--- a/man2/wait.2
+++ b/man2/wait.2
@@ -196,7 +196,7 @@ argument that the child specified in a call to
 or
 .BR _exit (2)
 or as the argument for a return statement in main().
-This macro should only be employed if
+This macro should be employed only if
 .B WIFEXITED
 returned true.
 .TP
@@ -206,13 +206,13 @@ returns true if the child process was terminated by a signal.
 .BI WTERMSIG( status )
 returns the number of the signal that caused the child process to
 terminate.
-This macro should only be employed if
+This macro should be employed only if
 .B WIFSIGNALED
 returned true.
 .TP
 .BI WCOREDUMP( status )
 returns true if the child produced a core dump.
-This macro should only be employed if
+This macro should be employed only if
 .B WIFSIGNALED
 returned true.
 This macro is not specified in POSIX.1-2001 and is not available on
@@ -221,14 +221,14 @@ Only use this enclosed in #ifdef WCOREDUMP ... #endif.
 .TP
 .BI WIFSTOPPED( status )
 returns true if the child process was stopped by delivery of a signal;
-this is only possible if the call was done using
+this is possible only if the call was done using
 .B WUNTRACED
 or when the child is being traced (see
 .BR ptrace (2)).
 .TP
 .BI WSTOPSIG( status )
 returns the number of the signal which caused the child to stop.
-This macro should only be employed if
+This macro should be employed only if
 .B WIFSTOPPED
 returned true.
 .TP
diff --git a/man3/abs.3 b/man3/abs.3
index 222ecf242..1abc23151 100644
--- a/man3/abs.3
+++ b/man3/abs.3
@@ -81,7 +81,7 @@ Returns the absolute value of the integer argument, of the appropriate
 integer type for the function.
 .SH CONFORMING TO
 SVr4, POSIX.1-2001, 4.3BSD, C99.
-.\" POSIX.1 (1996 edition) only requires the
+.\" POSIX.1 (1996 edition) requires only the
 .\" .BR abs ()
 .\" function.
 C89 only
diff --git a/man3/aio_read.3 b/man3/aio_read.3
index 0c8eb9910..6b8f81c96 100644
--- a/man3/aio_read.3
+++ b/man3/aio_read.3
@@ -91,7 +91,7 @@ On error the request is not enqueued, \-1
 is returned, and
 .I errno
 is set appropriately.
-If an error is only detected later, it will
+If an error is detected only later, it will
 be reported via
 .BR aio_return (3)
 (returns status \-1) and
diff --git a/man3/aio_write.3 b/man3/aio_write.3
index bf6bc8164..f6e855a0a 100644
--- a/man3/aio_write.3
+++ b/man3/aio_write.3
@@ -98,7 +98,7 @@ On error the request is not enqueued, \-1
 is returned, and
 .I errno
 is set appropriately.
-If an error is only detected later, it will
+If an error is detected only later, it will
 be reported via
 .BR aio_return (3)
 (returns status \-1) and
diff --git a/man3/bsd_signal.3 b/man3/bsd_signal.3
index 94fba6973..c7738b306 100644
--- a/man3/bsd_signal.3
+++ b/man3/bsd_signal.3
@@ -88,7 +88,7 @@ for details.
 The use of
 .I sighandler_t
 is a GNU extension;
-this type is only defined if the
+this type is defined only if the
 .B _GNU_SOURCE
 feature test macro is defined.
 .SH SEE ALSO
diff --git a/man3/catgets.3 b/man3/catgets.3
index ece3bd844..059888b98 100644
--- a/man3/catgets.3
+++ b/man3/catgets.3
@@ -69,7 +69,7 @@ returns the value
 .SH CONFORMING TO
 POSIX.1-2001.
 .SH NOTES
-These functions are only available in libc.so.4.4.4c and above.
+These functions are available only in libc.so.4.4.4c and above.
 The Jan 1987 X/Open Portability Guide specifies a more subtle
 error return:
 .I message
diff --git a/man3/clearenv.3 b/man3/clearenv.3
index 7e4d86dd0..ba727fe46 100644
--- a/man3/clearenv.3
+++ b/man3/clearenv.3
@@ -67,7 +67,7 @@ and
 but changed its mind and scheduled these functions for some
 later issue of this standard (cf. B.4.6.1).
 However, POSIX.1-2001
-only adds
+adds only
 .BR putenv (3),
 and rejected
 .BR clearenv ().
diff --git a/man3/cmsg.3 b/man3/cmsg.3
index d6b4c63b1..22057c015 100644
--- a/man3/cmsg.3
+++ b/man3/cmsg.3
@@ -52,8 +52,8 @@ See their manual pages for more information.
 Ancillary data is a sequence of
 .I struct cmsghdr
 structures with appended data.
-This sequence should only be accessed
-using the macros described in this manual page and never directly.
+This sequence should be accessed
+using only the macros described in this manual page and never directly.
 See the specific protocol man pages for the available control message types.
 The maximum ancillary buffer size allowed per socket can be set using
 .IR /proc/sys/net/core/optmem_max ;
@@ -144,7 +144,7 @@ the IPv6 advanced API described in RFC\ 2292 and the SUSv2.
 .BR CMSG_ALIGN ()
 is a Linux extension.
 .SH NOTES
-For portability, ancillary data should be accessed only using the macros
+For portability, ancillary data should be accessed using only the macros
 described here.
 .BR CMSG_ALIGN ()
 is a Linux extension and should be not used in portable programs.
diff --git a/man3/dbopen.3 b/man3/dbopen.3
index a3c618797..88bd7d616 100644
--- a/man3/dbopen.3
+++ b/man3/dbopen.3
@@ -312,7 +312,7 @@ are available only for the
 .B DB_RECNO
 access method because they each imply that the access method is able to
 create new keys.
-This is only true if the keys are ordered and independent, record numbers
+This is true only if the keys are ordered and independent, record numbers
 for example.
 .IP
 The default behavior of the
diff --git a/man3/dirfd.3 b/man3/dirfd.3
index 857a5fcd6..0fe941042 100644
--- a/man3/dirfd.3
+++ b/man3/dirfd.3
@@ -58,7 +58,7 @@ returns the file descriptor associated with the directory stream
 .IR dirp .
 .LP
 This descriptor is the one used internally by the directory stream.
-As a result, it is only useful for functions which do not depend on
+As a result, it is useful only for functions which do not depend on
 or alter the file position, such as
 .BR fstat (2)
 and
@@ -89,7 +89,7 @@ This function was a BSD extension, present in 4.3BSD-Reno, not in 4.2BSD.
 .SH NOTES
 The prototype for
 .BR dirfd ()
-is only available if
+is available only if
 .B _BSD_SOURCE
 or
 .B _SVID_SOURCE
diff --git a/man3/dlopen.3 b/man3/dlopen.3
index b1f21be3d..fbd8b8c60 100644
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
@@ -128,7 +128,7 @@ One of the following two values must be included in
 Perform lazy binding.
 Only resolve symbols as the code that references them is executed.
 If the symbol is never referenced, then it is never resolved.
-(Lazy binding is only performed for function references;
+(Lazy binding is performed only for function references;
 references to variables are always immediately bound when
 the library is loaded.)
 .TP
@@ -224,7 +224,7 @@ has been called on it as many times as
 has succeeded on it.
 The
 .BR _init ()
-routine, if present, is only called once.
+routine, if present, is called only once.
 But a subsequent call with
 .B RTLD_NOW
 may force symbol resolution for a library earlier loaded with
diff --git a/man3/exec.3 b/man3/exec.3
index 9c6146088..afdf65173 100644
--- a/man3/exec.3
+++ b/man3/exec.3
@@ -183,7 +183,7 @@ with the path of the file as its first argument.
 .SH RETURN VALUE
 The
 .BR exec ()
-functions only return if an error has occurred.
+functions return only if an error has occurred.
 The return value is \-1, and
 .I errno
 is set to indicate the error.
diff --git a/man3/fenv.3 b/man3/fenv.3
index 84425cba5..be2b202ac 100644
--- a/man3/fenv.3
+++ b/man3/fenv.3
@@ -272,7 +272,7 @@ which represents an environment where every exception raised causes a
 trap to occur.
 You can test for this macro using
 .BR #ifdef .
-It is only defined if
+It is defined only if
 .B _GNU_SOURCE
 is defined.
 The C99 standard does not define a way to set individual bits in the
diff --git a/man3/ferror.3 b/man3/ferror.3
index 505035def..c78a4eac1 100644
--- a/man3/ferror.3
+++ b/man3/ferror.3
@@ -73,8 +73,7 @@ The function
 tests the end-of-file indicator for the stream pointed to by
 .IR stream ,
 returning nonzero if it is set.
-The end-of-file indicator can only be
-cleared by the function
+The end-of-file indicator can be cleared only by the function
 .BR clearerr ().
 .PP
 The function
@@ -82,7 +81,7 @@ The function
 tests the error indicator for the stream pointed to by
 .IR stream ,
 returning nonzero if it is set.
-The error indicator can only be reset by the
+The error indicator can be reset only by the
 .BR clearerr ()
 function.
 .PP
diff --git a/man3/fmemopen.3 b/man3/fmemopen.3
index ec7b3fa51..50a734c5c 100644
--- a/man3/fmemopen.3
+++ b/man3/fmemopen.3
@@ -90,7 +90,7 @@ to allow for this.
 Attempts to write more than
 .I size
 bytes to the buffer result in an error.
-(By default, such errors will only be visible when the
+(By default, such errors will be visible only when the
 .I stdio
 buffer is flushed.
 Disabling buffering with
diff --git a/man3/fnmatch.3 b/man3/fnmatch.3
index eeb40342b..508bec664 100644
--- a/man3/fnmatch.3
+++ b/man3/fnmatch.3
@@ -80,7 +80,7 @@ matched if it matches an initial segment of
 .I string
 which is followed by a slash.
 This flag is mainly for the internal
-use of glibc and is only implemented in certain cases.
+use of glibc and is implemented only in certain cases.
 .TP
 .B FNM_CASEFOLD
 If this flag (a GNU extension) is set, the pattern is matched
diff --git a/man3/fopen.3 b/man3/fopen.3
index d30ee7140..c01d8e98e 100644
--- a/man3/fopen.3
+++ b/man3/fopen.3
@@ -284,7 +284,7 @@ Currently,
 .\" As at glibc 2.4:
 use of
 .BR mmap (2)
-is only attempted for a file opened for reading.
+is attempted only for a file opened for reading.
 .TP
 .B x
 .\" Since glibc 2.0?
diff --git a/man3/futimes.3 b/man3/futimes.3
index b51f30910..b8d7ce3a5 100644
--- a/man3/futimes.3
+++ b/man3/futimes.3
@@ -92,7 +92,7 @@ is available since glibc 2.6, and is implemented using the
 system call, which is supported since kernel 2.6.22.
 .SH CONFORMING TO
 These functions are not specified in any standard.
-Other than Linux, they are only available on the BSDs.
+Other than Linux, they are available only on the BSDs.
 .SH SEE ALSO
 .BR utime (2),
 .BR utimensat (2),
diff --git a/man3/getaddrinfo.3 b/man3/getaddrinfo.3
index 3a6ee3342..dec5fca59 100644
--- a/man3/getaddrinfo.3
+++ b/man3/getaddrinfo.3
@@ -378,8 +378,8 @@ includes the
 flag, then IPv4 addresses are returned in the list pointed to by
 .I res
 only if the local system has at least one
-IPv4 address configured, and IPv6 addresses are only returned
-if the local system has at least one IPv6 address configured.
+IPv4 address configured, and IPv6 addresses are returned
+only if the local system has at least one IPv6 address configured.
 The loopback address is not considered for this case as valid
 as a configured address.
 .PP
@@ -542,7 +542,7 @@ The requested service is not available for the requested socket type.
 It may be available through another socket type.
 For example, this error could occur if
 .I service
-was "shell" (a service only available on stream sockets), and either
+was "shell" (a service available only on stream sockets), and either
 .I hints.ai_protocol
 was
 .BR IPPROTO_UDP ,
diff --git a/man3/getifaddrs.3 b/man3/getifaddrs.3
index 1003da6e0..0a67dcb43 100644
--- a/man3/getifaddrs.3
+++ b/man3/getifaddrs.3
@@ -163,9 +163,9 @@ or
 The
 .BR getifaddrs ()
 function first appeared in glibc 2.3, but before glibc 2.3.3,
-the implementation only supported IPv4 addresses;
+the implementation supported only IPv4 addresses;
 IPv6 support was added in glibc 2.3.3.
-Support of address families other than IPv4 is only available
+Support of address families other than IPv4 is available only
 on kernels that support netlink.
 .SH CONFORMING TO
 Not in POSIX.1-2001.
diff --git a/man3/getipnodebyname.3 b/man3/getipnodebyname.3
index cb615aef8..9972eaa42 100644
--- a/man3/getipnodebyname.3
+++ b/man3/getipnodebyname.3
@@ -73,7 +73,7 @@ These functions replace the
 .BR gethostbyname (3)
 and
 .BR gethostbyaddr (3)
-functions, which could only access the IPv4 network address family.
+functions, which could access only the IPv4 network address family.
 The
 .BR getipnodebyname ()
 and
diff --git a/man3/hsearch.3 b/man3/hsearch.3
index 52e029995..e66c840a1 100644
--- a/man3/hsearch.3
+++ b/man3/hsearch.3
@@ -220,7 +220,7 @@ and
 .I key
 was not found in the table.
 .PP
-POSIX.1-2001 only specifies the
+POSIX.1-2001 specifies only the
 .B ENOMEM
 error.
 .SH CONFORMING TO
diff --git a/man3/if_nameindex.3 b/man3/if_nameindex.3
index 8fa9d7aaa..bb33aa606 100644
--- a/man3/if_nameindex.3
+++ b/man3/if_nameindex.3
@@ -98,8 +98,8 @@ or
 The
 .BR if_nameindex ()
 function first appeared in glibc 2.1, but before glibc 2.3.4,
-the implementation only supported interfaces with IPv4 addresses.
-Support of interfaces that don't have IPv4 addresses is only available
+the implementation supported only interfaces with IPv4 addresses.
+Support of interfaces that don't have IPv4 addresses is available only
 on kernels that support netlink.
 .SH CONFORMING TO
 RFC\ 3493, POSIX.1-2001.
diff --git a/man3/inet_pton.3 b/man3/inet_pton.3
index cb5a9b4b1..6125de4cc 100644
--- a/man3/inet_pton.3
+++ b/man3/inet_pton.3
@@ -137,7 +137,7 @@ and
 supports IPv6 addresses.
 On the other hand,
 .BR inet_pton ()
-only accepts IPv4 addresses in dotted-decimal notation, whereas
+accepts only IPv4 addresses in dotted-decimal notation, whereas
 .BR inet_aton (3)
 and
 .BR inet_addr (3)
diff --git a/man3/mblen.3 b/man3/mblen.3
index 235df7f41..e176400c4 100644
--- a/man3/mblen.3
+++ b/man3/mblen.3
@@ -28,8 +28,7 @@ If \fIs\fP is not a NULL pointer, the
 function inspects at most
 \fIn\fP bytes of the multibyte string starting at \fIs\fP and extracts the
 next complete multibyte character.
-It uses a static anonymous shift state only
-known to the
+It uses a static anonymous shift state known only to the
 .BR mblen ()
 function.
 If the multibyte character is not the null wide
@@ -54,7 +53,7 @@ If \fIs\fP is a NULL pointer, the
 function
 .\" The Dinkumware doc and the Single UNIX specification say this, but
 .\" glibc doesn't implement this.
-resets the shift state, only known to this function, to the initial state, and
+resets the shift state, known to only this function, to the initial state, and
 returns nonzero if the encoding has nontrivial shift state, or zero if the
 encoding is stateless.
 .SH RETURN VALUE
diff --git a/man3/mbrlen.3 b/man3/mbrlen.3
index 469e351b2..da5023069 100644
--- a/man3/mbrlen.3
+++ b/man3/mbrlen.3
@@ -50,7 +50,7 @@ returns
 In this case,
 the effects on \fI*ps\fP are undefined.
 .PP
-If \fIps\fP is a NULL pointer, a static anonymous state only known to the
+If \fIps\fP is a NULL pointer, a static anonymous state known only to the
 .BR mbrlen ()
 function is used instead.
 .SH RETURN VALUE
diff --git a/man3/mbsrtowcs.3 b/man3/mbsrtowcs.3
index d0975b8b4..f1d9974f9 100644
--- a/man3/mbsrtowcs.3
+++ b/man3/mbsrtowcs.3
@@ -67,7 +67,7 @@ and that no length limit exists.
 .PP
 In both of the above cases,
 if \fIps\fP is a NULL pointer, a static anonymous
-state only known to the
+state known only to the
 .BR mbsrtowcs ()
 function is used instead.
 .PP
diff --git a/man3/mbtowc.3 b/man3/mbtowc.3
index 9f4784f1d..26156c5a7 100644
--- a/man3/mbtowc.3
+++ b/man3/mbtowc.3
@@ -32,7 +32,7 @@ bytes of the multibyte string starting at \fIs\fP,
 extracts the next complete
 multibyte character, converts it to a wide character and stores it at
 \fI*pwc\fP.
-It updates an internal shift state only known to the
+It updates an internal shift state known only to the
 .BR mbtowc ()
 function.
 If \fIs\fP does not point to a null byte (\(aq\\0\(aq), it returns the number
diff --git a/man3/mcheck.3 b/man3/mcheck.3
index 315e9a614..17b38cb4e 100644
--- a/man3/mcheck.3
+++ b/man3/mcheck.3
@@ -72,7 +72,7 @@ This can be very slow!
 The
 .BR mcheck_check_all ()
 function causes an immediate check on all allocated blocks.
-This call is only effective if
+This call is effective only if
 .BR mcheck ()
 is called beforehand.
 
diff --git a/man3/memfrob.3 b/man3/memfrob.3
index 1dc063892..732d059e0 100644
--- a/man3/memfrob.3
+++ b/man3/memfrob.3
@@ -49,7 +49,7 @@ on the
 encrypted memory area.
 .PP
 Note that this function is not a proper encryption routine as the XOR
-constant is fixed, and is only suitable for hiding strings.
+constant is fixed, and is suitable only for hiding strings.
 .SH RETURN VALUE
 The
 .BR memfrob ()
diff --git a/man3/mq_notify.3 b/man3/mq_notify.3
index ef8ecc57d..11a711f0d 100644
--- a/man3/mq_notify.3
+++ b/man3/mq_notify.3
@@ -106,11 +106,11 @@ notifications for this message queue, then the registration is removed;
 another process can then register to receive a message notification
 for this queue.
 
-Message notification only occurs when a new message arrives and
+Message notification occurs only when a new message arrives and
 the queue was previously empty.
 If the queue was not empty at the time
 .BR mq_notify ()
-was called, then a notification will only occur after
+was called, then a notification will occur only after
 the queue is emptied and a new message arrives.
 
 If another process or thread is waiting to read a message
diff --git a/man3/netlink.3 b/man3/netlink.3
index abc1bfac1..734b214e1 100644
--- a/man3/netlink.3
+++ b/man3/netlink.3
@@ -40,7 +40,7 @@ They are similar in spirit to the macros defined in
 .BR cmsg (3)
 for auxiliary data.
 The buffer passed to and from a netlink socket should
-only be accessed using these macros.
+be accessed using only these macros.
 .TP
 .BR NLMSG_ALIGN ()
 Round the length of a netlink message up to align it properly.
diff --git a/man3/posix_memalign.3 b/man3/posix_memalign.3
index ed0706241..e00cac478 100644
--- a/man3/posix_memalign.3
+++ b/man3/posix_memalign.3
@@ -243,9 +243,9 @@ Some systems provide no way to reclaim memory allocated with
 .BR memalign ()
 or
 .BR valloc ()
-(because one can only pass to
+(because one can pass to
 .BR free (3)
-a pointer obtained from
+only a pointer obtained from
 .BR malloc (3),
 while, for example,
 .BR memalign ()
@@ -265,8 +265,8 @@ reclaimed with
 
 The glibc
 .BR malloc (3)
-always returns 8-byte aligned memory addresses, so these functions are only
-needed if you require larger alignment values.
+always returns 8-byte aligned memory addresses, so these functions are
+needed only if you require larger alignment values.
 .SH SEE ALSO
 .BR brk (2),
 .BR getpagesize (2),
diff --git a/man3/printf.3 b/man3/printf.3
index 306c01f30..25986fbe2 100644
--- a/man3/printf.3
+++ b/man3/printf.3
@@ -546,7 +546,7 @@ A following integer conversion corresponds to a
 .I ptrdiff_t
 argument.
 .PP
-The SUSv2 only knows about the length modifiers
+The SUSv2 knows about only the length modifiers
 .B h
 (in
 .BR hd ,
diff --git a/man3/pthread_attr_setscope.3 b/man3/pthread_attr_setscope.3
index 523a4baa7..4d0011eee 100644
--- a/man3/pthread_attr_setscope.3
+++ b/man3/pthread_attr_setscope.3
@@ -74,7 +74,7 @@ were created with the
 .B PTHREAD_SCOPE_SYSTEM
 contention scope.
 .PP
-POSIX.1-2001 only requires that an implementation support one of these
+POSIX.1-2001 requires that an implementation support only one of these
 contention scopes, but permits both to be supported.
 Linux supports
 .BR PTHREAD_SCOPE_SYSTEM ,
diff --git a/man3/pthread_cleanup_push.3 b/man3/pthread_cleanup_push.3
index 6d7f58fbf..e0e5c1dcb 100644
--- a/man3/pthread_cleanup_push.3
+++ b/man3/pthread_cleanup_push.3
@@ -94,7 +94,7 @@ containing \(aq\fB{\fP\(aq and \(aq\fB}\fP\(aq, respectively.
 For this reason, the caller must ensure that calls to these
 functions are paired within the same function,
 and at the same lexical nesting level.
-(In other words, a clean-up handler is only established
+(In other words, a clean-up handler is established only
 during the execution of a specified section of code.)
 
 Calling
@@ -132,7 +132,7 @@ and
 functions \fIare\fP implemented as macros that expand to text
 containing \(aq\fB{\fP\(aq and \(aq\fB}\fP\(aq, respectively.
 This means that variables declared within the scope of
-paired calls to these functions will only be visible within that scope.
+paired calls to these functions will be visible within only that scope.
 
 POSIX.1
 .\" The text was actually added in the 2004 TC2
diff --git a/man3/pthread_kill_other_threads_np.3 b/man3/pthread_kill_other_threads_np.3
index a4140195c..0cfde7ec6 100644
--- a/man3/pthread_kill_other_threads_np.3
+++ b/man3/pthread_kill_other_threads_np.3
@@ -34,7 +34,7 @@ pthread_kill_other_threads_np \- terminate all other threads in process
 .fi
 .SH DESCRIPTION
 .BR pthread_kill_other_threads_np ()
-only has an effect in the LinuxThreads threading implementation.
+has an effect only in the LinuxThreads threading implementation.
 On that implementation,
 calling this function causes the immediate termination of
 all threads in the application,
diff --git a/man3/pthread_self.3 b/man3/pthread_self.3
index 47008fb10..4c85df708 100644
--- a/man3/pthread_self.3
+++ b/man3/pthread_self.3
@@ -65,7 +65,7 @@ Thread identifiers should be considered opaque:
 any attempt to use a thread ID other than in pthreads calls
 is nonportable and can lead to unspecified results.
 
-Thread IDs are only guaranteed to be unique within a process.
+Thread IDs are guaranteed to be unique only within a process.
 A thread ID may be reused after a terminated thread has been joined,
 or a detached thread has terminated.
 
diff --git a/man3/pthread_setcancelstate.3 b/man3/pthread_setcancelstate.3
index 82f3fc25a..da1f63465 100644
--- a/man3/pthread_setcancelstate.3
+++ b/man3/pthread_setcancelstate.3
@@ -143,7 +143,7 @@ if cancellation occurs in the middle of the function call.
 Consequently, clean-up handlers cease to be useful.
 Functions that can be safely asynchronously canceled are called
 .IR "async-cancel-safe functions" .
-POSIX.1-2001 only requires that
+POSIX.1-2001 requires only that
 .BR pthread_cancel (3),
 .BR pthread_setcancelstate (),
 and
diff --git a/man3/pthread_setconcurrency.3 b/man3/pthread_setconcurrency.3
index 059c974ac..618d2f097 100644
--- a/man3/pthread_setconcurrency.3
+++ b/man3/pthread_setconcurrency.3
@@ -41,7 +41,7 @@ The
 function informs the implementation of the application's
 desired concurrency level, specified in
 .IR new_level .
-The implementation only takes this as a hint:
+The implementation takes this only as a hint:
 POSIX.1 does not specify the level of concurrency that
 should be provided as a result of calling
 .BR pthread_setconcurrency ().
@@ -85,7 +85,7 @@ POSIX.1-2001.
 .SH NOTES
 The default concurrency level is 0.
 
-Concurrency levels are only meaningful for M:N threading implementations,
+Concurrency levels are meaningful only for M:N threading implementations,
 where at any moment a subset of a process's set of user-level threads
 may be bound to a smaller number of kernel-scheduling entities.
 Setting the concurrency level allows the application to
diff --git a/man3/raise.3 b/man3/raise.3
index ba62ea8df..851fa0e87 100644
--- a/man3/raise.3
+++ b/man3/raise.3
@@ -57,7 +57,7 @@ pthread_kill(pthread_self(), sig);
 .PP
 If the signal causes a handler to be called,
 .BR raise ()
-will only return after the signal handler has returned.
+will return only after the signal handler has returned.
 .SH RETURN VALUE
 .BR raise ()
 returns 0 on success, and nonzero for failure.
diff --git a/man3/resolver.3 b/man3/resolver.3
index 3c4845f64..e65a225b3 100644
--- a/man3/resolver.3
+++ b/man3/resolver.3
@@ -188,7 +188,7 @@ has been called.
 .TP
 .B RES_DEBUG
 Print debugging messages.
-This option is only available if glibc was built with debugging enabled,
+This option is available only if glibc was built with debugging enabled,
 .\" See resolv/README.
 .\" Support for RES_DEBUG was made conditional in glibc 2.2.
 which is not the default.
diff --git a/man3/rpc.3 b/man3/rpc.3
index 7a8632e18..b34be0951 100644
--- a/man3/rpc.3
+++ b/man3/rpc.3
@@ -231,7 +231,7 @@ Default timeouts are set, but can be modified using
 .BR clnt_control ().
 .IP
 Warning: Using UDP has its shortcomings.
-Since UDP-based RPC messages can only hold up to 8 Kbytes of encoded data,
+Since UDP-based RPC messages can hold only up to 8 Kbytes of encoded data,
 this transport cannot be used for procedures that take
 large arguments or return huge results.
 .LP
@@ -477,7 +477,7 @@ time until a response is received or until the call times out.
 The total time for the call to time out is specified by
 .BR clnt_call ().
 .IP
-Warning: since UDP-based RPC messages can only hold up to 8 Kbytes
+Warning: since UDP-based RPC messages can hold only up to 8 Kbytes
 of encoded data, this transport cannot be used for procedures
 that take large arguments or return huge results.
 .LP
@@ -699,7 +699,7 @@ A global variable reflecting the RPC service side's
 read file descriptor bit mask; it is suitable as a parameter to the
 .BR select (2)
 system call.
-This is only of interest if a service implementor does not call
+This is of interest only if a service implementor does not call
 .BR svc_run (),
 but rather does his own asynchronous event processing.
 This variable is read-only (do not pass its address to
@@ -754,7 +754,7 @@ of a procedure associated with the RPC service transport handle,
 .BI "void svc_getreqset(fd_set *" rdfds );
 .fi
 .IP
-This routine is only of interest if a service implementor does not call
+This routine is of interest only if a service implementor does not call
 .BR svc_run (),
 but instead implements custom asynchronous event processing.
 It is called when the
diff --git a/man3/rtime.3 b/man3/rtime.3
index eaf7675e5..2ced8166c 100644
--- a/man3/rtime.3
+++ b/man3/rtime.3
@@ -59,7 +59,7 @@ Only IPv4 is supported.
 .LP
 Some
 .I in.timed
-versions only support TCP.
+versions support only TCP.
 Try the example program with
 .I use_tcp
 set to 1.
diff --git a/man3/rtnetlink.3 b/man3/rtnetlink.3
index ea23a210b..ca6be67ba 100644
--- a/man3/rtnetlink.3
+++ b/man3/rtnetlink.3
@@ -42,8 +42,7 @@ All
 messages consist of a
 .BR netlink (7)
 message header and appended attributes.
-The attributes should be only
-manipulated using the macros provided here.
+The attributes should be manipulated only using the macros provided here.
 .PP
 .BI RTA_OK( rta ", " attrlen )
 returns true if
diff --git a/man3/scanf.3 b/man3/scanf.3
index 62695f343..e477298ad 100644
--- a/man3/scanf.3
+++ b/man3/scanf.3
@@ -708,9 +708,9 @@ if (n == 1) {
 .fi
 .in
 .PP
-As shown in the above example, it is only necessary to call
+As shown in the above example, it is necessary to call
 .BR free (3)
-if the
+only if the
 .BR scanf ()
 call successfully read a string.
 .SH SEE ALSO
diff --git a/man3/setbuf.3 b/man3/setbuf.3
index 87b150400..ad9914ffb 100644
--- a/man3/setbuf.3
+++ b/man3/setbuf.3
@@ -124,7 +124,7 @@ only the mode is affected; a new buffer will be allocated on the next read
 or write operation.
 The
 .BR setvbuf ()
-function may only be used after opening a stream and before any other
+function may be used only after opening a stream and before any other
 operations have been performed on it.
 .PP
 The other three calls are, in effect, simply aliases for calls to
diff --git a/man3/setnetgrent.3 b/man3/setnetgrent.3
index 974586728..d6907811e 100644
--- a/man3/setnetgrent.3
+++ b/man3/setnetgrent.3
@@ -75,7 +75,7 @@ that stores the strings in the supplied buffer.
 To free all allocated buffers use
 .BR endnetgrent ().
 .PP
-In most cases you only want to check if the triplet
+In most cases you want to check only if the triplet
 .RI ( hostname ", " username ", " domainname )
 is a member of a netgroup.
 The function
diff --git a/man3/shm_open.3 b/man3/shm_open.3
index 67dec98af..90991a439 100644
--- a/man3/shm_open.3
+++ b/man3/shm_open.3
@@ -81,9 +81,9 @@ and any of the other flags listed here:
 .TP 1.1i
 .B O_RDONLY
 Open the object for read access.
-A shared memory object opened in this way can only be
+A shared memory object opened in this way can be
 .BR mmap (2)ed
-for read (\fBPROT_READ\fP) access.
+only for read (\fBPROT_READ\fP) access.
 .TP
 .B O_RDWR
 Open the object for read-write access.
diff --git a/man3/sigpause.3 b/man3/sigpause.3
index 0da326b7b..2fa352d26 100644
--- a/man3/sigpause.3
+++ b/man3/sigpause.3
@@ -78,7 +78,7 @@ argument (instead of an
 On Linux, this routine is a system call only on the Sparc (sparc64)
 architecture.
 
-Libc4 and libc5 only know about the BSD version.
+Libc4 and libc5 know only about the BSD version.
 
 Glibc uses the BSD version if the
 .B _BSD_SOURCE
diff --git a/man3/sigset.3 b/man3/sigset.3
index 78f36f68a..5ff17a968 100644
--- a/man3/sigset.3
+++ b/man3/sigset.3
@@ -192,7 +192,7 @@ These functions appeared in glibc version 2.1.
 
 The
 .I sighandler_t
-type is a GNU extension; it is only used on this page to make the
+type is a GNU extension; it is used on this page only to make the
 .BR sigset ()
 prototype more easily readable.
 
diff --git a/man3/sigwait.3 b/man3/sigwait.3
index 8d9ac1d8c..913b2a28d 100644
--- a/man3/sigwait.3
+++ b/man3/sigwait.3
@@ -61,7 +61,7 @@ is the same as
 except that:
 .IP * 2
 .BR sigwait ()
-only returns the signal number, rather than a
+returns only the signal number, rather than a
 .I siginfo_t
 structure describing the signal.
 .IP *
diff --git a/man3/sockatmark.3 b/man3/sockatmark.3
index 1945911b5..ba23d23e5 100644
--- a/man3/sockatmark.3
+++ b/man3/sockatmark.3
@@ -78,7 +78,7 @@ returns 1, then the out-of-band data can be read using the
 flag of
 .BR recv (2).
 
-Out-of-band data is only supported on some stream socket protocols.
+Out-of-band data is supported only on some stream socket protocols.
 
 .BR sockatmark ()
 can safely be called from a handler for the
diff --git a/man3/strcasecmp.3 b/man3/strcasecmp.3
index c404bf1ff..802981f8e 100644
--- a/man3/strcasecmp.3
+++ b/man3/strcasecmp.3
@@ -49,8 +49,8 @@ respectively, to be less than, to match, or be greater than \fIs2\fP.
 .PP
 The
 .BR strncasecmp ()
-function is similar, except it only compares
-the first \fIn\fP bytes of \fIs1\fP.
+function is similar, except it compares
+the only first \fIn\fP bytes of \fIs1\fP.
 .SH RETURN VALUE
 The
 .BR strcasecmp ()
diff --git a/man3/strcmp.3 b/man3/strcmp.3
index 53c19fff2..24b22c461 100644
--- a/man3/strcmp.3
+++ b/man3/strcmp.3
@@ -51,8 +51,8 @@ to match, or be greater than \fIs2\fP.
 .PP
 The
 .BR strncmp ()
-function is similar, except it only compares
-the first (at most) \fIn\fP bytes of \fIs1\fP and \fIs2\fP.
+function is similar, except it compares
+the only first (at most) \fIn\fP bytes of \fIs1\fP and \fIs2\fP.
 .SH RETURN VALUE
 The
 .BR strcmp ()
diff --git a/man3/strdup.3 b/man3/strdup.3
index 4d27c17a9..67a0f5471 100644
--- a/man3/strdup.3
+++ b/man3/strdup.3
@@ -87,7 +87,7 @@ and can be freed with
 
 The
 .BR strndup ()
-function is similar, but only copies at most
+function is similar, but copies at most
 \fIn\fP bytes.
 If \fIs\fP is longer than \fIn\fP, only \fIn\fP
 bytes are copied, and a terminating null byte (\(aq\\0\(aq) is added.
@@ -98,7 +98,7 @@ and
 are similar, but use
 .BR alloca (3)
 to allocate the buffer.
-They are only available when using the GNU
+They are available only when using the GNU
 GCC suite, and suffer from the same limitations described in
 .BR alloca (3).
 .SH RETURN VALUE
diff --git a/man3/strftime.3 b/man3/strftime.3
index 3461c71a8..fde487d82 100644
--- a/man3/strftime.3
+++ b/man3/strftime.3
@@ -412,7 +412,7 @@ Convert alphabetic characters in result string to upper case.
 .TP
 .B #
 Swap the case of the result string.
-(This flag only works with certain conversion specifier characters,
+(This flag works only with certain conversion specifier characters,
 and of these, it is only really useful with
 .BR %Z .)
 .PP
diff --git a/man3/strptime.3 b/man3/strptime.3
index 9a19e1aba..c5332a8e3 100644
--- a/man3/strptime.3
+++ b/man3/strptime.3
@@ -292,7 +292,7 @@ SUSv2, POSIX.1-2001.
 .SH NOTES
 .LP
 In principle, this function does not initialize \fItm\fP but
-only stores the values specified.
+stores only the values specified.
 This means that \fItm\fP should be initialized before the call.
 Details differ a bit between different UNIX systems.
 The glibc implementation does not touch those fields which are not
diff --git a/man3/strsignal.3 b/man3/strsignal.3
index 6b4f0c057..89c0b5a92 100644
--- a/man3/strsignal.3
+++ b/man3/strsignal.3
@@ -62,8 +62,7 @@ The
 .BR strsignal ()
 function returns a string describing the signal
 number passed in the argument \fIsig\fP.
-The string can only be used
-until the next call to
+The string can be used only until the next call to
 .BR strsignal ().
 .PP
 The array \fIsys_siglist\fP holds the signal description strings
diff --git a/man3/strverscmp.3 b/man3/strverscmp.3
index b99e8fb24..60336ac86 100644
--- a/man3/strverscmp.3
+++ b/man3/strverscmp.3
@@ -54,7 +54,7 @@ Thus, the task of
 .BR strverscmp ()
 is to compare two strings and find the "right" order, while
 .BR strcmp (3)
-only finds the lexicographic order.
+finds only the lexicographic order.
 This function does not use
 the locale category
 .BR LC_COLLATE ,
diff --git a/man3/sysv_signal.3 b/man3/sysv_signal.3
index 1763cbe79..957b9d5fb 100644
--- a/man3/sysv_signal.3
+++ b/man3/sysv_signal.3
@@ -80,7 +80,7 @@ for details.
 The use of
 .I sighandler_t
 is a GNU extension;
-this type is only defined if
+this type is defined only if
 the
 .B _GNU_SOURCE
 feature test macro is defined.
diff --git a/man3/termios.3 b/man3/termios.3
index d668a4b90..4f5f3041f 100644
--- a/man3/termios.3
+++ b/man3/termios.3
@@ -104,7 +104,7 @@ cc_t     c_cc[NCCS];   /* special characters */
 The values that may be assigned to these fields are described below.
 In the case of the first four bit-mask fields,
 the definitions of some of the associated flags that may be set are
-only exposed if a specific feature test macro (see
+exposed only if a specific feature test macro (see
 .BR feature_test_macros (7))
 is defined, as noted in brackets ("[]").
 .PP
@@ -759,7 +759,7 @@ the timer is restarted after each further byte is received.
 returns either when the lesser of the number of bytes requested or
 MIN byte have been read,
 or when the inter-byte timeout expires.
-Because the timer is only started after the initial byte
+Because the timer is started only after the initial byte
 becomes available, at least one byte will be read.
 .SS Raw mode
 .LP
diff --git a/man3/wcrtomb.3 b/man3/wcrtomb.3
index 9c955e869..c82a065fd 100644
--- a/man3/wcrtomb.3
+++ b/man3/wcrtomb.3
@@ -63,7 +63,7 @@ where
 is an internal anonymous buffer.
 .PP
 In all of the above cases, if \fIps\fP is a NULL pointer, a static anonymous
-state only known to the
+state known only to the
 .BR wcrtomb ()
 function is used instead.
 .SH RETURN VALUE
diff --git a/man3/wcsnlen.3 b/man3/wcsnlen.3
index 92f40b78c..75405a8b5 100644
--- a/man3/wcsnlen.3
+++ b/man3/wcsnlen.3
@@ -54,7 +54,7 @@ but at most
 wide characters (note: this parameter is not a byte count).
 In doing this,
 .BR wcsnlen ()
-looks only at the first \fImaxlen\fP
+looks at only the first \fImaxlen\fP
 wide characters at \fIs\fP and never beyond \fIs+maxlen\fP.
 .SH RETURN VALUE
 The
diff --git a/man3/wcsnrtombs.3 b/man3/wcsnrtombs.3
index 88e59f6a7..3efeea7bc 100644
--- a/man3/wcsnrtombs.3
+++ b/man3/wcsnrtombs.3
@@ -99,7 +99,7 @@ no destination length limit exists.
 .PP
 In both of the above cases,
 if \fIps\fP is a NULL pointer, a static anonymous
-state only known to the
+state known only to the
 .BR wcsnrtombs ()
 function is used instead.
 .PP
diff --git a/man3/wcsrtombs.3 b/man3/wcsrtombs.3
index 60ab4273f..f1c2bfc69 100644
--- a/man3/wcsrtombs.3
+++ b/man3/wcsrtombs.3
@@ -74,7 +74,7 @@ no length limit exists.
 .PP
 In both of the above cases,
 if \fIps\fP is a NULL pointer, a static anonymous
-state only known to the
+state known only to the
 .BR wcsrtombs ()
 function is used instead.
 .PP
diff --git a/man3/wctomb.3 b/man3/wctomb.3
index 72a07909b..7ac76ef50 100644
--- a/man3/wctomb.3
+++ b/man3/wctomb.3
@@ -31,7 +31,7 @@ function converts the wide character
 the character array pointed to by \fIs\fP.
 It updates the shift state, which
 is stored in a static anonymous variable
-only known to the
+known only to the
 .BR wctomb ()
 function,
 and returns the length of said multibyte representation,
@@ -47,7 +47,7 @@ If \fIs\fP is NULL, the
 function
 .\" The Dinkumware doc and the Single UNIX specification say this, but
 .\" glibc doesn't implement this.
-resets the shift state, only known to this function,
+resets the shift state, known only to this function,
 to the initial state, and
 returns nonzero if the encoding has nontrivial shift state,
 or zero if the encoding is stateless.
diff --git a/man3/wprintf.3 b/man3/wprintf.3
index 8fb9b551f..6b838d1a7 100644
--- a/man3/wprintf.3
+++ b/man3/wprintf.3
@@ -204,7 +204,7 @@ category of the
 current locale.
 .PP
 If the \fIformat\fP string contains non-ASCII wide characters, the program
-will only work correctly if the
+will work correctly only if the
 .B LC_CTYPE
 category of the current locale at
 run time is the same as the
diff --git a/man4/console_codes.4 b/man4/console_codes.4
index 63073bec7..1a497fdde 100644
--- a/man4/console_codes.4
+++ b/man4/console_codes.4
@@ -396,7 +396,7 @@ point at translation table a), b), c) and d), respectively.
 .PP
 The sequence ESC c causes a terminal reset, which is what you want if the
 screen is all garbled.
-The oft-advised "echo ^V^O" will only make G0 current,
+The oft-advised "echo ^V^O" will make only G0 current,
 but there is no guarantee that G0 points at table a).
 In some distributions there is a program
 .BR reset (1)
diff --git a/man4/cpuid.4 b/man4/cpuid.4
index 74c846586..2504c938f 100644
--- a/man4/cpuid.4
+++ b/man4/cpuid.4
@@ -55,7 +55,7 @@ and on an SMP box will direct the access to CPU
 as listed in
 .IR /proc/cpuinfo .
 
-This file is protected so that it can only be read by the user
+This file is protected so that it can be read only by the user
 .IR root ,
 or members of the group
 .IR root .
diff --git a/man4/msr.4 b/man4/msr.4
index e3a46378f..f97df8959 100644
--- a/man4/msr.4
+++ b/man4/msr.4
@@ -40,7 +40,7 @@ reading or writing in chunks of 8 bytes.
 An I/O transfer of more than 8 bytes means multiple reads or writes
 of the same register.
 
-This file is protected so that it can only be read and written by the user
+This file is protected so that it can be read and written only by the user
 .IR root ,
 or members of the group
 .IR root .
diff --git a/man4/rtc.4 b/man4/rtc.4
index fd67262cd..2bca01d2e 100644
--- a/man4/rtc.4
+++ b/man4/rtc.4
@@ -307,8 +307,8 @@ it will update a designated RTC periodically every 11 minutes.
 To do so, the kernel has to briefly turn off periodic interrupts;
 this might affect programs using that RTC.
 
-An RTC's Epoch has nothing to do with the POSIX Epoch which is only
-used for the system clock.
+An RTC's Epoch has nothing to do with the POSIX Epoch which is
+used only for the system clock.
 
 If the year according to the RTC's Epoch and the year register is
 less than 1970 it is assumed to be 100 years later, that is, between 2000
diff --git a/man4/sk98lin.4 b/man4/sk98lin.4
index 9cd632be8..d818bccb5 100644
--- a/man4/sk98lin.4
+++ b/man4/sk98lin.4
@@ -18,7 +18,7 @@
 .\" GNU General Public License for more details.
 .\"
 .\" You should have received a copy of the GNU General Public
-.\" License along with this manual; if not, see
+.\" License along with this manual;if not, see
 .\" <http://www.gnu.org/licenses/>.
 .\" %%%LICENSE_END
 .\"
@@ -100,7 +100,7 @@ If loading is finished, any desired IP address can be
 assigned to the respective
 .I eth[x]
 interface using the
-.BR ifconfig (8)
+.BR only ifconfig (8)
 command.
 This causes the adapter to connect to the Ethernet and to display a status
 message on the console saying "ethx: network connection up using port y"
@@ -129,7 +129,7 @@ Those two commands might even be combined into one:
 
     ifconfig eth0 10.1.1.1 mtu 9000
 
-Note that large frames can only be used if permitted by
+Note that large frames can be used only if permitted by
 your network infrastructure.
 This means, that any switch being used in your Ethernet must
 also support large frames.
@@ -151,7 +151,7 @@ command again:
 The Marvell/SysKonnect Gigabit Ethernet driver for Linux is able to
 support VLAN and Link Aggregation according to
 IEEE standards 802.1, 802.1q, and 802.3ad.
-Those features are only available after installation of open source modules
+Those features are available only after installation of open source modules
 which can be found on the Internet:
 
 .IR VLAN \c
@@ -174,7 +174,7 @@ kind of failures or problems arising when using these modules.
 .BI Speed_A= i,j,...
 This parameter is used to set the speed capabilities of port A of an
 adapter card.
-It is only valid for Yukon copper adapters.
+It is valid only for Yukon copper adapters.
 Possible values are:
 .IR 10 ,
 .IR 100 ,
@@ -192,7 +192,7 @@ a port can be forced to a specific setting with this parameter.
 .BI Speed_B= i,j,...
 This parameter is used to set the speed capabilities of port B of
 an adapter card.
-It is only valid for Yukon copper adapters.
+It is valid only for Yukon copper adapters.
 Possible values are:
 .IR 10 ,
 .IR 100 ,
@@ -248,7 +248,7 @@ or
 whereas
 .I Both
 is the default.
-This parameter is only relevant if AutoNeg_A of port A is not set to
+This parameter is relevant only if AutoNeg_A of port A is not set to
 .IR Sense .
 If AutoNeg_A is set to
 .IR On ,
@@ -279,7 +279,7 @@ or
 whereas
 .I Both
 is the default.
-This parameter is only relevant if AutoNeg_B of port B is not set to
+This parameter is relevant only if AutoNeg_B of port B is not set to
 .IR Sense .
 If AutoNeg_B is set to
 .IR On ,
@@ -368,7 +368,7 @@ Note that this parameter is ignored if AutoNeg_B is set to
 .IR Off .
 .TP
 .BI Role_A= i,j,...
-This parameter is only valid for 1000Base-T adapter cards.
+This parameter is valid only for 1000Base-T adapter cards.
 For two 1000Base-T ports to communicate,
 one must take the role of the master (providing timing information),
 while the other must be the slave.
@@ -385,7 +385,7 @@ link establishment, but if that fails the port A of an adapter card
 can be forced to a specific setting with this parameter.
 .TP
 .BI Role_B= i,j,...
-This parameter is only valid for 1000Base-T adapter cards.
+This parameter is valid only for 1000Base-T adapter cards.
 For two 1000Base-T ports to communicate, one must take
 the role of the master (providing timing information),
 while the other must be the slave.
@@ -502,7 +502,7 @@ Possible values for this parameter are in the range of
 30...40000 (interrupts per second).
 The default value is 2000.
 
-This parameter is only used, if either static or dynamic interrupt moderation
+This parameter is used only if either static or dynamic interrupt moderation
 is enabled on a network adapter card.
 This parameter is ignored if no moderation is applied.
 
@@ -561,7 +561,7 @@ must not be any router between the ports).
 Check local port and segmentation:
 This mode supports the same functions as the CheckLocalPort
 mode and additionally checks network segmentation between the ports.
-Therefore, this mode is only to be used if Gigabit Ethernet
+Therefore, this mode is to be used only if Gigabit Ethernet
 switches are installed on the network that have been
 configured to use the Spanning Tree protocol.
 
diff --git a/man4/st.4 b/man4/st.4
index 015886347..a9f70b442 100644
--- a/man4/st.4
+++ b/man4/st.4
@@ -605,7 +605,7 @@ Otherwise the device-specific addresses are used.
 It is highly advisable to set this option if the drive supports the
 logical addresses because they count also filemarks.
 There are some
-drives that only support the logical block addresses.
+drives that support only the logical block addresses.
 .TP
 .BR MT_ST_SYSV " (Default: false)"
 When this option is enabled, the tape devices use the SystemV
diff --git a/man4/tty.4 b/man4/tty.4
index 065341532..4f9cca48b 100644
--- a/man4/tty.4
+++ b/man4/tty.4
@@ -52,7 +52,7 @@ and all processes in the current session lose their controlling tty.
 .sp
 This
 .BR ioctl (2)
-call only works on file descriptors connected
+call works only on file descriptors connected
 to \fI/dev/tty\fP.
 It is used by daemon processes when they are invoked
 by a user at a terminal.
diff --git a/man5/charmap.5 b/man5/charmap.5
index 34e7994e1..5f05e532d 100644
--- a/man5/charmap.5
+++ b/man5/charmap.5
@@ -83,7 +83,7 @@ This form defines exactly one character and its encoding.
 .TP
 .I <symbolic-name>...<symbolic-name> <encoding> <comments>
 This form defines a couple of characters.
-This is only useful for
+This is useful only for
 multibyte-characters, which are currently not implemented.
 .PP
 The last line in a charmap-definition file must contain
diff --git a/man5/core.5 b/man5/core.5
index 3b4038483..e71277dd7 100644
--- a/man5/core.5
+++ b/man5/core.5
@@ -291,7 +291,7 @@ in the parent shell before running a program, for example:
 .fi
 .in
 .PP
-This file is only provided if the kernel was built with the
+This file is provided only if the kernel was built with the
 .B CONFIG_ELF_CORE
 configuration option.
 .SH NOTES
diff --git a/man5/elf.5 b/man5/elf.5
index aade93cbd..842724442 100644
--- a/man5/elf.5
+++ b/man5/elf.5
@@ -784,7 +784,7 @@ The array element, if present, specifies the location and size of the program
 header table itself, both in the file and in the memory image of the program.
 This segment type may not occur more than once in a file.
 Moreover, it may
-only occur if the program header table is part of the memory image of the
+occur only if the program header table is part of the memory image of the
 program.
 If it is present, it must precede any loadable segment entry.
 .TP
diff --git a/man5/hosts.equiv.5 b/man5/hosts.equiv.5
index 05d4e30d4..e44f7c970 100644
--- a/man5/hosts.equiv.5
+++ b/man5/hosts.equiv.5
@@ -50,14 +50,14 @@ a wildcard character that means "any host"!
 .SH FILES
 .I /etc/hosts.equiv
 .SH NOTES
-Some systems will only honor the contents of this file when it has owner
+Some systems will honor the contents of this file only when it has owner
 root and no write permission for anybody else.
 Some exceptionally
 paranoid systems even require that there be no other hard links to the file.
 .PP
 Modern systems use the Pluggable Authentication Modules library (PAM).
-With PAM a standalone plus sign is only considered a wildcard
-character which means "any host" when the word
+With PAM a standalone plus sign is considered a wildcard
+character which means "any host" only when the word
 .I promiscuous
 is added to the auth component line in your PAM file for
 the particular service
diff --git a/man5/proc.5 b/man5/proc.5
index cef1a7075..19f355edb 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -1740,7 +1740,7 @@ 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
 .BR malloc (3)
-or similar), but only touches 300MB of that memory will show up
+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.
 This 1GB is memory which has been "committed" to by the VM
@@ -3107,7 +3107,7 @@ Processes can handle this if they want to; see
 .BR sigaction (2)
 for more details.
 
-This feature is only active on architectures/platforms with advanced machine
+This feature is active only on architectures/platforms with advanced machine
 check handling and depends on the hardware capabilities.
 
 Applications can override the
diff --git a/man5/resolv.conf.5 b/man5/resolv.conf.5
index 7efb561dd..716b3459e 100644
--- a/man5/resolv.conf.5
+++ b/man5/resolv.conf.5
@@ -136,7 +136,7 @@ sets
 .BR RES_DEBUG
 in
 .IR _res.options
-(only effective if glibc was built with debug support; see
+(effective only if glibc was built with debug support; see
 .BR resolver (3)).
 .TP
 .BI ndots: n
@@ -252,7 +252,7 @@ resolving process).
 .TP
 .BR single-request-reopen " (since glibc 2.9)"
 The resolver uses the same socket for the A and AAAA requests.
-Some hardware mistakenly only sends back one reply.
+Some hardware mistakenly sends back only one reply.
 When that happens the client system will sit and wait for the second reply.
 Turning this option on changes this behavior
 so that if two requests from the same port are not handled correctly it will
diff --git a/man5/services.5 b/man5/services.5
index 7b3f16f5d..697578d88 100644
--- a/man5/services.5
+++ b/man5/services.5
@@ -56,8 +56,8 @@ protocols when assigning a port number.
 Therefore, most entries will
 have two entries, even for TCP-only services.
 
-Port numbers below 1024 (so-called "low numbered" ports) can only be
-bound to by root (see
+Port numbers below 1024 (so-called "low numbered" ports) can be
+bound to only by root (see
 .BR bind (2),
 .BR tcp (7),
 and
diff --git a/man5/slabinfo.5 b/man5/slabinfo.5
index 13e678913..be584d56b 100644
--- a/man5/slabinfo.5
+++ b/man5/slabinfo.5
@@ -129,6 +129,6 @@ SMP per-CPU caches exist since Linux 2.4.0-test3.
 .SH NOTES
 Since Linux 2.6.16 the file
 .I /proc/slabinfo
-is only present if the
+is present only if the
 .B CONFIG_SLAB
 kernel configuration option is enabled.
diff --git a/man7/arp.7 b/man7/arp.7
index 30f7d4a09..ad1aef3a6 100644
--- a/man7/arp.7
+++ b/man7/arp.7
@@ -67,7 +67,7 @@ If that fails and an old MAC address is known, a unicast probe is sent
 times.
 If that fails too, it will broadcast a new ARP
 request to the network.
-Requests are only sent when there is data queued
+Requests are sent only when there is data queued
 for sending.
 
 Linux will automatically add a nonpermanent proxy arp entry when it
@@ -97,7 +97,7 @@ struct arpreq {
 .BR SIOCSARP ", " SIOCDARP " and " SIOCGARP
 respectively set, delete and get an ARP mapping.
 Setting and deleting ARP maps are privileged operations and may
-only be performed by a process with the
+be performed only by a process with the
 .B CAP_NET_ADMIN
 capability or an effective UID of 0.
 
diff --git a/man7/bootparam.7 b/man7/bootparam.7
index 44f61b734..fcdcbb10f 100644
--- a/man7/bootparam.7
+++ b/man7/bootparam.7
@@ -80,7 +80,7 @@ name[=value_1][,value_2]...[,value_10]
 .LP
 where 'name' is a unique keyword that is used to identify what part of
 the kernel the associated values (if any) are to be given to.
-Note the limit of 10 is real, as the present code only handles 10 comma
+Note the limit of 10 is real, as the present code handles only 10 comma
 separated parameters per keyword.
 (However, you can reuse the same
 keyword with up to an additional 10 parameters in unusually
@@ -257,7 +257,7 @@ keeps all device drivers except the driver for 'blah' from probing
 .TP
 .B "'mem=...'"
 The BIOS call defined in the PC specification that returns
-the amount of installed memory was only designed to be able
+the amount of installed memory was designed only to be able
 to report up to 64MB.
 Linux uses this BIOS call at boot to
 determine how much memory is installed.
@@ -602,7 +602,7 @@ The AdvanSys driver can accept up to four i/o addresses that will be
 probed for an AdvanSys SCSI card.
 Note that these values (if used) do
 not effect EISA or PCI probing in any way.
-They are only used for
+They are used only for
 probing ISA and VLB cards.
 In addition, if the driver has been
 compiled with debugging enabled, the level of debugging output can be
@@ -839,9 +839,9 @@ is identified automatically, but if it isn't then this may help.
 .B "Standard ST-506 Disk Driver Options ('hd=')"
 The standard disk driver can accept geometry arguments for the disks
 similar to the IDE driver.
-Note however that it only expects three
+Note however that it expects only three
 values (C/H/S); any more or any less and it will silently ignore you.
-Also, it only accepts 'hd=' as an argument, that is, 'hda='
+Also, it accepts only 'hd=' as an argument, that is, 'hda='
 and so on are not valid here.
 The format is as follows:
 .IP
@@ -1034,7 +1034,7 @@ things like shared memory address, interface selection, DMA channel
 and the like.
 
 The most common use of this parameter is to force probing for a second
-ethercard, as the default is to only probe for one.
+ethercard, as the default is to probe only for one.
 This can be accomplished with a simple:
 .IP
 ether=0,0,eth1
@@ -1277,7 +1277,7 @@ wdt=io,irq
 .SS Mouse drivers
 .TP
 .B "'bmouse=irq'"
-The busmouse driver only accepts one parameter, that being the
+The busmouse driver accepts only one parameter, that being the
 hardware IRQ value to be used.
 .TP
 .B "'msmouse=irq'"
diff --git a/man7/capabilities.7 b/man7/capabilities.7
index 1dfcd329e..e3cfdf84a 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -872,7 +872,7 @@ A thread can determine if a capability is in its bounding set using the
 .B PR_CAPBSET_READ
 operation.
 
-Removing capabilities from the bounding set is only supported if file
+Removing capabilities from the bounding set is supported only if file
 capabilities are compiled into the kernel.
 In kernels before Linux 2.6.33,
 file capabilities were an optional feature configurable via the
diff --git a/man7/charsets.7 b/man7/charsets.7
index 0cd91bb4b..e6cc907e1 100644
--- a/man7/charsets.7
+++ b/man7/charsets.7
@@ -129,7 +129,7 @@ Skolt Sami still
 needs a few more accents than these.
 .TP
 8859-11
-This only exists as a rejected draft standard.
+This exists only as a rejected draft standard.
 The draft standard
 was identical to TIS-620, which is used under Linux for Thai.
 .TP
@@ -352,7 +352,7 @@ recent version selected by ESC & @ ESC $ B.
 .LP
 ISO 4873 stipulates a narrower use of character sets, where G0
 is fixed (always ASCII), so that G1, G2 and G3
-can only be invoked for codes with the high order bit set.
+can be invoked only for codes with the high order bit set.
 In particular, \fB^N\fP and \fB^O\fP are not used anymore, ESC ( xx
 can be used only with xx=B, and ESC ) xx, ESC * xx, ESC + xx
 are equivalent to ESC \- xx, ESC . xx, ESC / xx, respectively.
diff --git a/man7/cpuset.7 b/man7/cpuset.7
index 4a066cc2f..407dc05ae 100644
--- a/man7/cpuset.7
+++ b/man7/cpuset.7
@@ -72,7 +72,7 @@ The directories and files representing cpusets have normal
 file-system permissions.
 .PP
 Every process in the system belongs to exactly one cpuset.
-A process is confined to only run on the CPUs in
+A process is confined to run only on the CPUs in
 the cpuset it belongs to, and to allocate memory only
 on the memory nodes in that cpuset.
 When a process
@@ -292,7 +292,7 @@ section, below.
 .TP
 .IR cpuset.memory_pressure_enabled " (since Linux 2.6.16)"
 Flag (0 or 1).
-This file is only present in the root cpuset, normally
+This file is present only in the root cpuset, normally
 .IR /dev/cpuset .
 If set (1), the
 .I memory_pressure
@@ -788,13 +788,13 @@ balancing off the software clock described in
 .IR time (7).
 The setting of
 .I sched_relax_domain_level
-only applies to immediate load balancing.
+applies only to immediate load balancing.
 Regardless of the
 .I sched_relax_domain_level
 setting, periodic load balancing is attempted over all CPUs
 (unless disabled by turning off
 .IR sched_load_balance .)
-In any case, of course, tasks will only be scheduled to run on
+In any case, of course, tasks will be scheduled to run only on
 CPUs allowed by their cpuset, as modified by
 .BR sched_setaffinity (2)
 system calls.
@@ -841,7 +841,7 @@ The
 .I sched_relax_domain_level
 value of zero (0) always means
 don't perform immediate load balancing,
-hence that load balancing is only done periodically,
+hence that load balancing is done only periodically,
 not immediately when a CPU becomes available or another task becomes
 runnable.
 .PP
@@ -928,13 +928,13 @@ The following rules apply to each cpuset:
 Its CPUs and memory nodes must be a (possibly equal)
 subset of its parent's.
 .IP *
-It can only be marked
+It can be marked
 .IR cpu_exclusive
-if its parent is.
+only if its parent is.
 .IP *
-It can only be marked
+It can be marked
 .IR mem_exclusive
-if its parent is.
+only if its parent is.
 .IP *
 If it is
 .IR cpu_exclusive ,
@@ -1075,7 +1075,7 @@ there as well.
 In general, the kernel prefers to violate cpuset placement,
 rather than starving a process that has had all its allowed CPUs or
 memory nodes taken offline.
-User code should reconfigure cpusets to only refer to online CPUs
+User code should reconfigure cpusets to refer only to online CPUs
 and memory nodes when using hot-plug to add or remove such resources.
 .PP
 A few kernel-critical, internal memory-allocation requests, marked
diff --git a/man7/ddp.7 b/man7/ddp.7
index 2057763b9..b1c37d8a6 100644
--- a/man7/ddp.7
+++ b/man7/ddp.7
@@ -58,7 +58,7 @@ For
 you must specify
 .BR ATPROTO_DDP .
 .PP
-Raw sockets may be only opened by a process with effective user ID 0
+Raw sockets may be opened only by a process with effective user ID 0
 or when the process has the
 .B CAP_NET_RAW
 capability.
@@ -205,7 +205,7 @@ A kernel subsystem was not configured.
 Invalid socket option passed.
 .TP
 .B ENOTCONN
-The operation is only defined on a connected socket, but the socket wasn't
+The operation is defined only on a connected socket, but the socket wasn't
 connected.
 .TP
 .B EPERM
diff --git a/man7/epoll.7 b/man7/epoll.7
index 98bea748b..7ba2eed22 100644
--- a/man7/epoll.7
+++ b/man7/epoll.7
@@ -104,8 +104,8 @@ will probably hang despite the available data still present in the file
 input buffer;
 meanwhile the remote peer might be expecting a response based on the
 data it already sent.
-The reason for this is that edge-triggered mode only
-delivers events when changes occur on the monitored file descriptor.
+The reason for this is that edge-triggered mode
+delivers events only when changes occur on the monitored file descriptor.
 So, in step
 .B 5
 the caller might end up waiting for some data that is already present inside
diff --git a/man7/feature_test_macros.7 b/man7/feature_test_macros.7
index ec2acadcc..ed5c2b59b 100644
--- a/man7/feature_test_macros.7
+++ b/man7/feature_test_macros.7
@@ -149,7 +149,7 @@ definitions for POSIX.2-1992.
 .IP \(bu
 The value 199309L or greater additionally exposes
 definitions for POSIX.1b (real-time extensions).
-.\" 199506L functionality is only available since glibc 2.1
+.\" 199506L functionality is available only since glibc 2.1
 .IP \(bu
 The value 199506L or greater additionally exposes
 definitions for POSIX.1c (threads).
diff --git a/man7/futex.7 b/man7/futex.7
index 103d9f57e..31d91a133 100644
--- a/man7/futex.7
+++ b/man7/futex.7
@@ -38,12 +38,12 @@ it is a counter that can be incremented and decremented atomically;
 processes can wait for the value to become positive.
 .PP
 Futex operation is entirely user space for the noncontended case.
-The kernel is only involved to arbitrate the contended case.
+The kernel is involved only to arbitrate the contended case.
 As any sane design will strive for noncontention,
 futexes are also optimized for this situation.
 .PP
 In its bare form, a futex is an aligned integer which is
-only touched by atomic assembler instructions.
+touched only by atomic assembler instructions.
 Processes can share this integer using
 .BR mmap (2),
 via shared memory segments or because they share memory space,
diff --git a/man7/hier.7 b/man7/hier.7
index 1c0abe9fc..05cd13f3d 100644
--- a/man7/hier.7
+++ b/man7/hier.7
@@ -44,7 +44,7 @@ single user mode and to bring the system up or repair it.
 .TP
 .I /boot
 Contains static files for the boot loader.
-This directory only holds
+This directory holds only
 the files which are needed during the boot process.
 The map installer
 and configuration files should go to
diff --git a/man7/icmp.7 b/man7/icmp.7
index 5f4c6c0d5..2c06546b7 100644
--- a/man7/icmp.7
+++ b/man7/icmp.7
@@ -176,7 +176,7 @@ should not be relied on in portable programs.
 .PP
 .B ICMP_REDIRECT
 packets are not sent when Linux is not acting as a router.
-They are also only accepted from the old gateway defined in the
+They are also accepted only from the old gateway defined in the
 routing table and the redirect routes are expired after some time.
 .PP
 The 64-bit timestamp returned by
diff --git a/man7/inotify.7 b/man7/inotify.7
index 1d6f6a762..78bb88509 100644
--- a/man7/inotify.7
+++ b/man7/inotify.7
@@ -120,7 +120,7 @@ contains bits that describe the event that occurred (see below).
 
 .I cookie
 is a unique integer that connects related events.
-Currently this is only used for rename events, and
+Currently this is used only for rename events, and
 allows the resulting pair of
 .B IN_MOVED_FROM
 and
@@ -132,7 +132,7 @@ is set to 0.
 
 The
 .I name
-field is only present when an event is returned
+field is present only when an event is returned
 for a file inside a watched directory;
 it identifies the file pathname relative to the watched directory.
 This pathname is null-terminated,
@@ -340,7 +340,7 @@ The required library interfaces were added to glibc in version 2.4.
 .BR IN_MASK_ADD ,
 and
 .B IN_ONLYDIR
-were only added in version 2.5.)
+were added in version 2.5.)
 .SH CONFORMING TO
 The inotify API is Linux-specific.
 .SH NOTES
diff --git a/man7/ip.7 b/man7/ip.7
index 9bef3bf19..ffabff08a 100644
--- a/man7/ip.7
+++ b/man7/ip.7
@@ -168,7 +168,7 @@ capability) may
 .BR bind (2)
 to these sockets.
 Note that the raw IPv4 protocol as such has no concept of a
-port, they are only implemented by higher protocols like
+port, they are implemented only by higher protocols like
 .BR tcp (7)
 and
 .BR udp (7).
@@ -197,11 +197,11 @@ and multicast addresses.
 Unicast addresses specify a single interface of a host,
 broadcast addresses specify all hosts on a network and multicast
 addresses address all hosts in a multicast group.
-Datagrams to broadcast addresses can be only sent or received when the
+Datagrams to broadcast addresses can be sent or received only when the
 .B SO_BROADCAST
 socket flag is set.
-In the current implementation, connection-oriented sockets are only allowed
-to use unicast addresses.
+In the current implementation, connection-oriented sockets are allowed
+to use only unicast addresses.
 .\" Leave a loophole for XTP @)
 
 Note that the address and the port are always stored in
@@ -434,7 +434,7 @@ refer to RFC 3376.
 .BR IP_MTU " (since Linux 2.2)"
 .\" Precisely: 2.1.124
 Retrieve the current known path MTU of the current socket.
-Only valid when the socket has been connected.
+Valid only when the socket has been connected.
 Returns an integer.
 Only valid as a
 .BR getsockopt (2).
@@ -553,7 +553,7 @@ Argument is an integer.
 .BR IP_NODEFRAG " (since Linux 2.6.36)"
 If enabled (argument is nonzero),
 the reassembly of outgoing packets is disabled in the netfilter layer.
-This option is only valid for
+This option is valid only for
 .B SOCK_RAW
 sockets.
 The argument is an integer.
@@ -1119,7 +1119,7 @@ A kernel subsystem was not configured.
 Invalid socket option passed.
 .TP
 .B ENOTCONN
-The operation is only defined on a connected socket, but the socket wasn't
+The operation is defined only on a connected socket, but the socket wasn't
 connected.
 .TP
 .B EPERM
diff --git a/man7/ipv6.7 b/man7/ipv6.7
index ab7f721fb..366ae140b 100644
--- a/man7/ipv6.7
+++ b/man7/ipv6.7
@@ -171,7 +171,7 @@ is the 128-bit IPv6 address.
 .I sin6_scope_id
 is an ID depending on the scope of the address.
 It is new in Linux 2.4.
-Linux only supports it for link-local addresses, in that case
+Linux supports it only for link-local addresses, in that case
 .I sin6_scope_id
 contains the interface index (see
 .BR netdevice (7))
@@ -205,7 +205,7 @@ socket into a socket of a different address family.
 Only
 .B AF_INET
 is currently supported for that.
-It is only allowed for IPv6 sockets
+It is allowed only for IPv6 sockets
 that are connected and bound to a v4-mapped-on-v6 address.
 The argument is a pointer to an integer containing
 .BR AF_INET .
@@ -246,8 +246,7 @@ between 0 and 255.
 .TP
 .B IPV6_MULTICAST_IF
 Set the device for outgoing multicast packets on the socket.
-This is only allowed
-for
+This is allowed only for
 .B SOCK_DGRAM
 and
 .B SOCK_RAW
diff --git a/man7/man-pages.7 b/man7/man-pages.7
index 229d5c6e1..516dbd58a 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -240,7 +240,7 @@ then the SYNOPSIS should indicate this, as described in
 .TP
 .B CONFIGURATION
 Configuration details for a device.
-This section normally only appears in Section 4 pages.
+This section normally appears only in Section 4 pages.
 .TP
 .B DESCRIPTION
 gives an explanation of what the program, function, or format does.
@@ -262,7 +262,7 @@ section.
 .B OPTIONS
 describes the command-line options accepted by a
 program and how they change its behavior.
-This section should only appear for Section 1 and 8 manual pages.
+This section should appear only for Section 1 and 8 manual pages.
 .\" .TP
 .\" .B USAGE
 .\" describes the grammar of any sublanguage this implements.
@@ -270,7 +270,7 @@ This section should only appear for Section 1 and 8 manual pages.
 .B EXIT STATUS
 lists the possible exit status values of a program and
 the conditions that cause these values to be returned.
-This section should only appear for Section 1 and 8 manual pages.
+This section should appear only for Section 1 and 8 manual pages.
 .TP
 .B RETURN VALUE
 For Section 2 and 3 pages, this section gives a
@@ -337,7 +337,7 @@ many existing manual pages don't include this information
 (since there was no policy to do so when they were written).
 Patches to remedy this are welcome,
 but, from the perspective of programmers writing new code,
-this information probably only matters in the case of kernel
+this information probably matters only in the case of kernel
 interfaces that have been added in Linux 2.4 or later
 (i.e., changes since kernel 2.2),
 and library functions that have been added to glibc since version 2.1
@@ -518,7 +518,7 @@ However, note the following:
 Example programs should be written in C.
 .TP
 *
-An example program is only necessary and useful if it demonstrates
+An example program is necessary and useful only if it demonstrates
 something beyond what can easily be provided in a textual
 description of the interface.
 An example program that does nothing
diff --git a/man7/mdoc.7 b/man7/mdoc.7
index 3d241dff1..7cebd3044 100644
--- a/man7/mdoc.7
+++ b/man7/mdoc.7
@@ -269,7 +269,7 @@ Unless stated, manual domain macros share a common syntax:
 .Pp
 .Sy Note :
 Opening and closing
-punctuation characters are only recognized as such if they are presented
+punctuation characters are recognized as such only if they are presented
 one at a time.
 The string
 .Ql "),"
diff --git a/man7/mdoc.samples.7 b/man7/mdoc.samples.7
index cd7018f4a..7f5fbc712 100644
--- a/man7/mdoc.samples.7
+++ b/man7/mdoc.samples.7
@@ -1504,7 +1504,7 @@ If formatted with
 .Xr nroff ,
 a quoted literal is always quoted.
 If formatted with
-troff, an item is only quoted if the width
+troff, an item is quoted only if the width
 of the item is less than three constant width characters.
 This is to make short strings more visible where the font change
 to literal (constant width) is less noticeable.
diff --git a/man7/netdevice.7 b/man7/netdevice.7
index b81779892..42e43be73 100644
--- a/man7/netdevice.7
+++ b/man7/netdevice.7
@@ -256,7 +256,7 @@ Changes the name of the interface specified in
 to
 .IR ifr_newname .
 This is a privileged operation.
-It is only allowed when the interface
+It is allowed only when the interface
 is not up.
 .TP
 .B SIOCGIFCONF
@@ -310,7 +310,7 @@ These are not described here.
 .SH NOTES
 Strictly speaking,
 .B SIOCGIFCONF
-and the other ioctls that only accept or return
+and the other ioctls that accept or return only
 .B AF_INET
 socket addresses,
 are IP specific and belong in
diff --git a/man7/netlink.7 b/man7/netlink.7
index f57785166..7d007f958 100644
--- a/man7/netlink.7
+++ b/man7/netlink.7
@@ -27,7 +27,7 @@ processes and an internal kernel API for kernel modules.
 The internal kernel interface is not documented in this manual page.
 There is also an obsolete netlink interface
 via netlink character devices; this interface is not documented here
-and is only provided for backward compatibility.
+and is provided only for backward compatibility.
 
 Netlink is a datagram-oriented service.
 Both
@@ -117,7 +117,7 @@ Generic netlink family for simplified netlink usage.
 Netlink messages consist of a byte stream with one or multiple
 .I nlmsghdr
 headers and associated payload.
-The byte stream should only be accessed with the standard
+The byte stream should be accessed only with the standard
 .B NLMSG_*
 macros.
 See
@@ -312,7 +312,7 @@ identifies a netlink socket, not a process.
 If a process owns several netlink
 sockets, then
 .I nl_pid
-can only be equal to the process ID for at most one socket.
+can be equal to the process ID only for at most one socket.
 There are two ways to assign
 .I nl_pid
 to a netlink socket.
diff --git a/man7/numa.7 b/man7/numa.7
index 31a86a54c..e3c250b93 100644
--- a/man7/numa.7
+++ b/man7/numa.7
@@ -93,7 +93,7 @@ The number of pages allocated on
 includes only pages currently mapped by the process.
 Page migration and memory reclaim may have temporarily unmapped pages
 associated with this memory range.
-These pages may only show up again after the process has
+These pages may show up again only after the process has
 attempted to reference them.
 If the memory range represents a shared memory area or file mapping,
 other processes may currently have additional pages mapped in a
@@ -139,7 +139,7 @@ Number of pages that have an associated entry on a swap device.
 .TP
 .I active=<pages>
 The number of pages on the active list.
-This field is only shown if different from the number of pages in this range.
+This field is shown only if different from the number of pages in this range.
 This means that some inactive pages exist in the memory range that may be
 removed from memory by the swapper soon.
 .TP
@@ -150,7 +150,7 @@ No standards govern NUMA interfaces.
 .SH NOTES
 The Linux NUMA system calls and
 .I /proc
-interface are only available
+interface are available only
 if the kernel was configured and built with the
 .BR CONFIG_NUMA
 option.
diff --git a/man7/packet.7 b/man7/packet.7
index 006f2ac33..abb1f07ba 100644
--- a/man7/packet.7
+++ b/man7/packet.7
@@ -84,7 +84,7 @@ destination address before they are queued.
 
 By default all packets of the specified protocol type
 are passed to a packet socket.
-To only get packets from a specific interface use
+To get packets only from a specific interface use
 .BR bind (2)
 specifying an address in a
 .I struct sockaddr_ll
@@ -154,7 +154,7 @@ in promiscuous mode, and
 .B PACKET_OUTGOING
 for a packet originated from the local host that is looped back to a packet
 socket.
-These types make only sense for receiving.
+These types make sense only for receiving.
 .I sll_addr
 and
 .I sll_halen
@@ -302,7 +302,7 @@ For portable programs it is suggested to use
 .B AF_PACKET
 via
 .BR pcap (3);
-although this only covers a subset of the
+although this covers only a subset of the
 .B AF_PACKET
 features.
 
diff --git a/man7/path_resolution.7 b/man7/path_resolution.7
index 14db6709b..46c1c29c5 100644
--- a/man7/path_resolution.7
+++ b/man7/path_resolution.7
@@ -221,7 +221,7 @@ Two capabilities are relevant for file permissions checks:
 (A process has these capabilities if its fsuid is 0.)
 
 The \fBCAP_DAC_OVERRIDE\fP capability overrides all permission checking,
-but only grants execute permission when at least one
+but grants execute permission only when at least one
 of the file's three execute permission bits is set.
 
 The \fBCAP_DAC_READ_SEARCH\fP capability grants read and search permission
diff --git a/man7/posixoptions.7 b/man7/posixoptions.7
index b3b79d3ca..73c685bc3 100644
--- a/man7/posixoptions.7
+++ b/man7/posixoptions.7
@@ -103,8 +103,8 @@ The following functions are present:
 .\" C development.
 .SS --- - POSIX_CHOWN_RESTRICTED
 If this option is in effect (as it always is under POSIX.1-2001)
-then only root may change the owner of a file, and nonroot can only
-set the group of a file to one of the groups it belongs to.
+then only root may change the owner of a file, and nonroot can
+set the group of a file only to one of the groups it belongs to.
 This affects the functions
 .IR chown (),
 .IR fchown ().
diff --git a/man7/pthreads.7 b/man7/pthreads.7
index 4ebfa4edd..0c4c07bb3 100644
--- a/man7/pthreads.7
+++ b/man7/pthreads.7
@@ -123,7 +123,7 @@ This identifier is returned to the caller of
 .BR pthread_create (3),
 and a thread can obtain its own thread identifier using
 .BR pthread_self (3).
-Thread IDs are only guaranteed to be unique within a process.
+Thread IDs are guaranteed to be unique only within a process.
 A thread ID may be reused after a terminated thread has been joined,
 or a detached thread has terminated.
 In all pthreads functions that accept a thread ID as an argument,
@@ -775,7 +775,7 @@ According to POSIX.1, a process-directed signal (sent using
 for example) should be handled by a single,
 arbitrarily selected thread within the process.
 LinuxThreads does not support the notion of process-directed signals:
-signals may only be sent to specific threads.
+signals may be sent only to specific threads.
 .IP \- 3
 Threads have distinct alternate signal stack settings.
 However, a new thread's alternate signal stack settings
@@ -804,7 +804,7 @@ Threads do not share a common nice value.
 .\" "make setpriority POSIX compliant; introduce PRIO_THREAD extension"
 .\" Monitor this to see if it makes it into mainline.
 .PP
-Some NPTL nonconformances only occur with older kernels:
+Some NPTL nonconformances occur only with older kernels:
 .IP \- 3
 The information returned by
 .BR times (2)
diff --git a/man7/raw.7 b/man7/raw.7
index 2408abf65..aa4a0e527 100644
--- a/man7/raw.7
+++ b/man7/raw.7
@@ -84,7 +84,7 @@ for more information.
 
 In Linux 2.2, all IP header fields and options can be set using
 IP socket options.
-This means raw sockets are usually only needed for new
+This means raw sockets are usually needed only for new
 protocols or protocols with no user interface (like ICMP).
 
 When a packet is received, it is passed to any raw sockets which have
@@ -129,7 +129,7 @@ In addition, all
 .B IPPROTO_IP
 socket options valid for datagram sockets are supported.
 .SS Error handling
-Errors originating from the network are only passed to the user when the
+Errors originating from the network are passed to the user only when the
 socket is connected or the
 .B IP_RECVERR
 flag is enabled.
diff --git a/man7/rtld-audit.7 b/man7/rtld-audit.7
index 108d08ba0..43ec73a92 100644
--- a/man7/rtld-audit.7
+++ b/man7/rtld-audit.7
@@ -401,7 +401,7 @@ invocations for this symbol return different values,
 then the maximum returned value is used.
 The
 .BR la_pltenter ()
-function is only called if this buffer is
+function is called only if this buffer is
 explicitly set to a suitable value.
 
 The return value of
diff --git a/man7/rtnetlink.7 b/man7/rtnetlink.7
index 21d2a80e4..57b1f759f 100644
--- a/man7/rtnetlink.7
+++ b/man7/rtnetlink.7
@@ -52,7 +52,7 @@ struct rtattr {
 .fi
 .in
 
-These attributes should be only manipulated using the RTA_* macros
+These attributes should be manipulated using only the RTA_* macros
 or libnetlink, see
 .BR rtnetlink (3).
 .SS Messages
diff --git a/man7/sem_overview.7 b/man7/sem_overview.7
index b030cf9cf..e9de67453 100644
--- a/man7/sem_overview.7
+++ b/man7/sem_overview.7
@@ -106,7 +106,7 @@ the semaphore should be destroyed using
 The remainder of this section describes some specific details
 of the Linux implementation of POSIX semaphores.
 .SS Versions
-Prior to kernel 2.6, Linux only supported unnamed,
+Prior to kernel 2.6, Linux supported only unnamed,
 thread-shared semaphores.
 On a system with Linux 2.6 and a glibc that provides the NPTL
 threading implementation,
diff --git a/man7/sigevent.7 b/man7/sigevent.7
index fb58610f9..9cec77e6e 100644
--- a/man7/sigevent.7
+++ b/man7/sigevent.7
@@ -62,7 +62,7 @@ The definition shown in the SYNOPSIS is approximate:
 some of the fields in the
 .I sigevent
 structure may be defined as part of a union.
-Programs should only employ those fields relevant
+Programs should employ only those fields relevant
 to the value specified in
 .IR sigev_notify .
 .PP
diff --git a/man7/socket.7 b/man7/socket.7
index bee9c3ec9..97e5a8c10 100644
--- a/man7/socket.7
+++ b/man7/socket.7
@@ -88,7 +88,7 @@ tells the socket that new connections shall be accepted, and
 .BR accept (2)
 is used to get a new socket with a new incoming connection.
 .BR socketpair (2)
-returns two connected anonymous sockets (only implemented for a few
+returns two connected anonymous sockets (implemented only for a few
 local families like
 .BR AF_UNIX )
 .PP
@@ -303,7 +303,7 @@ interface name string with the maximum size of
 If a socket is bound to an interface,
 only packets received from that particular interface are processed by the
 socket.
-Note that this only works for some socket types, particularly
+Note that this works only for some socket types, particularly
 .B AF_INET
 sockets.
 It is not supported for packet sockets (use normal
@@ -362,7 +362,7 @@ This socket option is read-only.
 Expects an integer.
 .TP
 .B SO_DONTROUTE
-Don't send via a gateway, only send to directly connected hosts.
+Don't send via a gateway, send only to directly connected hosts.
 The same effect can be achieved by setting the
 .B MSG_DONTROUTE
 flag on a socket
@@ -417,7 +417,7 @@ capability.
 .B SO_OOBINLINE
 If this option is enabled,
 out-of-band data is directly placed into the receive data stream.
-Otherwise out-of-band data is only passed when the
+Otherwise out-of-band data is passed only when the
 .B MSG_OOB
 flag is set during receiving.
 .\" don't document it because it can do too much harm.
@@ -434,7 +434,7 @@ For more information see
 .TP
 .B SO_PEERCRED
 Return the credentials of the foreign process connected to this socket.
-This is only possible for connected
+This is possible only for connected
 .B AF_UNIX
 stream sockets and
 .B AF_UNIX
@@ -726,7 +726,7 @@ See
 for a description of
 .IR "struct timeval" .
 .\"
-This ioctl should only be used if the socket option
+This ioctl should be used only if the socket option
 .B SO_TIMESTAMP
 is not set on the socket.
 Otherwise, it returns the timestamp of the
diff --git a/man7/spufs.7 b/man7/spufs.7
index ba3a461b2..fef727cbf 100644
--- a/man7/spufs.7
+++ b/man7/spufs.7
@@ -172,7 +172,7 @@ flag.
 .I /mbox
 The first SPU-to-CPU communication mailbox.
 This file is read-only and can be read in units of 4 bytes.
-The file can only be used in nonblocking mode \- even
+The file can be used only in nonblocking mode \- even
 .BR poll (2)
 cannot be used to block on this file.
 The only possible operation on an open
@@ -352,7 +352,7 @@ The contents of these files are:
 .RS
 .TP 16
 .I npc
-Next Program Counter \- only valid when the SPU is in a stopped state.
+Next Program Counter \- valid only when the SPU is in a stopped state.
 .TP
 .I decr
 SPU Decrementer
diff --git a/man7/tcp.7 b/man7/tcp.7
index 3f9564be0..aaa8fb758 100644
--- a/man7/tcp.7
+++ b/man7/tcp.7
@@ -182,7 +182,7 @@ socket option is enabled, urgent data is put into the normal
 data stream (a program can test for its location using the
 .B SIOCATMARK
 ioctl described below),
-otherwise it can be only received when the
+otherwise it can be received only when the
 .B MSG_OOB
 flag is set for
 .BR recv (2)
@@ -202,8 +202,8 @@ TCP is built on top of IP (see
 The address formats defined by
 .BR ip (7)
 apply to TCP.
-TCP only supports point-to-point
-communication; broadcasting and multicasting are not
+TCP supports point-to-point communication only;
+broadcasting and multicasting are not
 supported.
 .SS /proc interfaces
 System-wide TCP parameter settings can be accessed by files in the directory
@@ -455,7 +455,7 @@ no response is obtained from the other end.
 .\" Since 2.1.43
 The number of seconds a connection needs to be idle
 before TCP begins sending out keep-alive probes.
-Keep-alives are only sent when the
+Keep-alives are sent only when the
 .B SO_KEEPALIVE
 socket option is enabled.
 The default value is 7200 seconds (2 hours).
diff --git a/man7/udp.7 b/man7/udp.7
index dd2332c6d..1e925d39b 100644
--- a/man7/udp.7
+++ b/man7/udp.7
@@ -64,7 +64,7 @@ is not supported.
 
 IP options may be sent or received using the socket options described in
 .BR ip (7).
-They are only processed by the kernel when the appropriate
+They are processed by the kernel only when the appropriate
 .I /proc
 parameter
 is enabled (but still passed to the user even when it is turned off).
@@ -74,7 +74,7 @@ See
 When the
 .B MSG_DONTROUTE
 flag is set on sending, the destination address must refer to a local
-interface address and the packet is only sent to that interface.
+interface address and the packet is sent only to that interface.
 
 By default, Linux UDP does path MTU (Maximum Transmission Unit) discovery.
 This means the kernel
diff --git a/man7/unicode.7 b/man7/unicode.7
index ba139f4b0..f143e9d86 100644
--- a/man7/unicode.7
+++ b/man7/unicode.7
@@ -302,8 +302,8 @@ and sometimes even simple overstriking combining characters, but
 usually does not include support for scripts with right-to-left
 writing direction or ligature substitution requirements such as
 Hebrew, Arabic, or the Indic scripts.
-These scripts are currently only
-supported in certain GUI applications (HTML viewers, word processors)
+These scripts are currently
+supported only in certain GUI applications (HTML viewers, word processors)
 with sophisticated text rendering engines.
 .\" .SH AUTHOR
 .\" Markus Kuhn <mgk25@cl.cam.ac.uk>
diff --git a/man7/uri.7 b/man7/uri.7
index c3c53b29b..d372331d1 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -577,7 +577,7 @@ Such heuristics may
 change over time, particularly when new schemes are introduced.
 Since an abbreviated URI has the same syntax as a relative URL path,
 abbreviated URI references cannot be used where relative URIs are
-permitted, and can only be used when there is no defined base
+permitted, and can be used only when there is no defined base
 (such as in dialog boxes).
 Don't use abbreviated URIs as hypertext links inside a document;
 use the standard format as described here.
@@ -634,8 +634,8 @@ There is no general guarantee that a URL, which at one time
 located a given resource, will continue to do so.
 Nor is there any
 guarantee that a URL will not locate a different resource at some
-later point in time; such a guarantee can only be
-obtained from the person(s) controlling that namespace and the
+later point in time; such a guarantee can be
+obtained only from the person(s) controlling that namespace and the
 resource in question.
 .PP
 It is sometimes possible to construct a URL such that an attempt to
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 1cb8b3a14..3cdd615a1 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -119,7 +119,7 @@ encoded
 characters may be up to six bytes long, however the
 .B Unicode
 standard specifies no characters above 0x10ffff, so Unicode characters
-can only be up to four bytes long in
+can be only up to four bytes long in
 .BR UTF-8 .
 .SS Encoding
 The following byte sequences are used to represent a character.
diff --git a/man8/intro.8 b/man8/intro.8
index 55f4fe445..f209e699b 100644
--- a/man8/intro.8
+++ b/man8/intro.8
@@ -31,7 +31,7 @@
 intro \- introduction to administration and privileged commands
 .SH DESCRIPTION
 Section 8 of the manual describes commands
-which either can be or are only used by the superuser,
+which either can be or are used only by the superuser,
 like system-administration commands, daemons,
 and hardware-related commands.
 
diff --git a/man8/ldconfig.8 b/man8/ldconfig.8
index ae0845090..9d87a33c8 100644
--- a/man8/ldconfig.8
+++ b/man8/ldconfig.8
@@ -82,9 +82,9 @@ their type.
 Therefore, the
 .I /etc/ld.so.conf
 file format allows the specification of an expected type.
-This is
+This is used
 .I only
-used for those ELF libs which we can not work out.
+for those ELF libs which we can not work out.
 The format
 is "dirname=TYPE", where TYPE can be libc4, libc5, or libc6.
 (This syntax also works on the command line.)
diff --git a/man8/sync.8 b/man8/sync.8
index 136dc3a68..e486de164 100644
--- a/man8/sync.8
+++ b/man8/sync.8
@@ -67,7 +67,7 @@ POSIX.2.
 .SH NOTES
 On Linux,
 .B sync
-is only guaranteed to schedule the dirty blocks for writing; it can
+is guaranteed only to schedule the dirty blocks for writing; it can
 actually take a short time before all the blocks are finally written.
 The
 .BR reboot (8)