intro.1, _syscall.2, access.2, arch_prctl.2, cacheflush.2, chown.2, clock_getres.2, clone.2, create_module.2, fcntl.2, flock.2, get_kernel_syms.2, get_robust_list.2, get_thread_area.2, getcpu.2, getpriority.2, getrlimit.2, getrusage.2, ioprio_set.2, kexec_load.2, madvise.2, mbind.2, migrate_pages.2, mknod.2, mmap.2, mount.2, move_pages.2, mprotect.2, open.2, pause.2, pciconfig_read.2, perf_event_open.2, prctl.2, ptrace.2, query_module.2, read.2, reboot.2, recv.2, s390_runtime_instr.2, sched_setscheduler.2, select_tut.2, send.2, set_mempolicy.2, setfsgid.2, setfsuid.2, sigaction.2, spu_create.2, spu_run.2, stime.2, swapon.2, syslog.2, timer_create.2, timer_getoverrun.2, times.2, tkill.2, umount.2, unimplemented.2, ustat.2, vm86.2, wait.2, abs.3, aio_read.3, aio_write.3, bsd_signal.3, catgets.3, clearenv.3, cmsg.3, dbopen.3, dirfd.3, dlopen.3, exec.3, fenv.3, ferror.3, fmemopen.3, fnmatch.3, fopen.3, futimes.3, getaddrinfo.3, getifaddrs.3, getipnodebyname.3, hsearch.3, if_nameindex.3, inet_pton.3, mblen.3, mbrlen.3, mbsrtowcs.3, mbtowc.3, mcheck.3, memfrob.3, mq_notify.3, netlink.3, posix_memalign.3, printf.3, pthread_attr_setscope.3, pthread_cleanup_push.3, pthread_kill_other_threads_np.3, pthread_self.3, pthread_setcancelstate.3, pthread_setconcurrency.3, raise.3, resolver.3, rpc.3, rtime.3, rtnetlink.3, scanf.3, setbuf.3, setnetgrent.3, shm_open.3, sigpause.3, sigset.3, sigwait.3, sockatmark.3, strcasecmp.3, strcmp.3, strdup.3, strftime.3, strptime.3, strsignal.3, strverscmp.3, sysv_signal.3, termios.3, wcrtomb.3, wcsnlen.3, wcsnrtombs.3, wcsrtombs.3, wctomb.3, wprintf.3, console_codes.4, cpuid.4, msr.4, rtc.4, sk98lin.4, st.4, tty.4, charmap.5, core.5, elf.5, hosts.equiv.5, proc.5, resolv.conf.5, services.5, slabinfo.5, arp.7, bootparam.7, capabilities.7, charsets.7, cpuset.7, ddp.7, epoll.7, feature_test_macros.7, futex.7, hier.7, icmp.7, inotify.7, ip.7, ipv6.7, man-pages.7, mdoc.7, mdoc.samples.7, netdevice.7, netlink.7, numa.7, packet.7, path_resolution.7, posixoptions.7, pthreads.7, raw.7, rtld-audit.7, rtnetlink.7, sem_overview.7, sigevent.7, socket.7, spufs.7, tcp.7, udp.7, unicode.7, uri.7, utf-8.7, intro.8, ldconfig.8, sync.8: Global fix: fix placement of word "only"

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

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

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

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.

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

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.

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.

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

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

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

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

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 ()

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

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

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

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

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

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)

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 .

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

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),

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)"

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),

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.

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

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 .

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"

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

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

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

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 ()

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

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

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

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

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

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)

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

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

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

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

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 ()

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

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

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

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

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 ,

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

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

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

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

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

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

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

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.

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.

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.

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)

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.

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.

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

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

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

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

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

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

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 ().

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.

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

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

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

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.

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

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

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

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

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?

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),

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 ,

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.

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

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

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.

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)

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

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

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

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

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.
 

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 ()

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

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.

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),

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 ,

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 ,

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

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,

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.
 

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

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

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.