From 60ae21db4c16ab66f704a3ebbd42b3560651cfa9 Mon Sep 17 00:00:00 2001 From: Jakub Wilk Date: Sat, 16 Mar 2019 15:15:40 +0100 Subject: [PATCH] intro.1, execve.2, getcontext.3, passwd.5, bpf-helpers.7: wfix Use gender-neutral pronouns. Signed-off-by: Jakub Wilk Signed-off-by: Michael Kerrisk --- man1/intro.1 | 2 +- man2/execve.2 | 2 +- man3/getcontext.3 | 2 +- man5/passwd.5 | 2 +- man7/bpf-helpers.7 | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/man1/intro.1 b/man1/intro.1 index 03649841d..63fcf5dea 100644 --- a/man1/intro.1 +++ b/man1/intro.1 @@ -61,7 +61,7 @@ One types commands to the the command interpreter. It is not built-in, but is just a program and you can change your shell. -Everybody has her own favorite one. +Everybody has their own favorite one. The standard one is called .IR sh . See also diff --git a/man2/execve.2 b/man2/execve.2 index 7b0c5b853..313a468a5 100644 --- a/man2/execve.2 +++ b/man2/execve.2 @@ -559,7 +559,7 @@ The result of mounting a filesystem varies across Linux kernel versions: some will refuse execution of set-user-ID and set-group-ID executables when this would -give the user powers she did not have already (and return +give the user powers they did not have already (and return .BR EPERM ), some will just ignore the set-user-ID and set-group-ID bits and .BR exec () diff --git a/man3/getcontext.3 b/man3/getcontext.3 index 7e6b2f230..141b6e98a 100644 --- a/man3/getcontext.3 +++ b/man3/getcontext.3 @@ -184,7 +184,7 @@ there is no easy way to detect whether a return from is from the first call, or via a .BR setcontext () call. -The user has to invent her own bookkeeping device, and a register +The user has to invent their own bookkeeping device, and a register variable won't do since registers are restored. .PP When a signal occurs, the current user context is saved and diff --git a/man5/passwd.5 b/man5/passwd.5 index 70b1105e1..469d29260 100644 --- a/man5/passwd.5 +++ b/man5/passwd.5 @@ -67,7 +67,7 @@ the shadow record should be obtained from an NIS+ server. .PP Regardless of whether shadow passwords are used, many system administrators use an asterisk (*) in the encrypted password field to make sure -that this user can not authenticate him- or herself using a +that this user can not authenticate themself using a password. (But see NOTES below.) .PP diff --git a/man7/bpf-helpers.7 b/man7/bpf-helpers.7 index 7112b4536..6f07f476e 100644 --- a/man7/bpf-helpers.7 +++ b/man7/bpf-helpers.7 @@ -2250,7 +2250,7 @@ Depending on the BPF program type, a local storage area can be shared between multiple instances of the BPF program, running simultaneously. .sp -A user should care about the synchronization by himself. +A user should care about the synchronization by themself. For example, by using the \fBBPF_STX_XADD\fP instruction to alter the shared data. .TP