doc: fix uses of non-neutral gender pronouns

10 files changed, 21 insertions, 21 deletions

diff --git a/doc/adg/Linux-PAM_ADG.xml b/doc/adg/Linux-PAM_ADG.xml
index 337b2563..0f1957ec 100644
--- a/doc/adg/Linux-PAM_ADG.xml
+++ b/doc/adg/Linux-PAM_ADG.xml
@@ -524,8 +524,8 @@ cc -o application .... -lpam -lpam_misc
         <term>Authentication token</term>
         <listitem>
           <para>
-            Generally, this is a password. However, a user can authenticate
-            him/herself in a variety of ways. Updating the user's
+            Generally, this is a password. However, users can authenticate
+            themselves in a variety of ways. Updating the user's
             authentication token thus corresponds to
             <emphasis>refreshing</emphasis> the object they use to
             authenticate themselves with the system. The word password is
@@ -746,4 +746,4 @@ TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
 USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
     </programlisting>
   </chapter>
-</book>
\ No newline at end of file
+</book>
diff --git a/doc/sag/Linux-PAM_SAG.xml b/doc/sag/Linux-PAM_SAG.xml
index e49d7951..205ab98e 100644
--- a/doc/sag/Linux-PAM_SAG.xml
+++ b/doc/sag/Linux-PAM_SAG.xml
@@ -131,9 +131,9 @@
     </para>
     <para>
       To illustrate the flexibility you face, consider the following
-      situation: a system administrator (parent) wishes to improve the
-      mathematical ability of her users (children). She can configure
-      their favorite ``Shoot 'em up game'' (PAM-aware of course) to
+      situation: system administrators (parents) wish to improve the
+      mathematical ability of their users (children). Their favorite
+      ``Shoot 'em up game'' (PAM-aware of course) can be configured to
       authenticate them with a request for the product of a couple of
       random numbers less than 12. It is clear that if the game is any
       good they will soon learn their
@@ -252,7 +252,7 @@ other   session  required       pam_deny.so
          is invoked so unless the users of a system contact the
          administrator when failing to execute a service application,
          the administrator may go for a long while in ignorance of the
-         fact that his system is misconfigured.
+         fact that the system is misconfigured.
        </para>
        <para>
          The addition of the following line before those in the above
diff --git a/doc/specs/rfc86.0.txt b/doc/specs/rfc86.0.txt
index b8c635a6..3451eaf5 100644
--- a/doc/specs/rfc86.0.txt
+++ b/doc/specs/rfc86.0.txt
@@ -402,7 +402,7 @@
 
 
 
-            given access to his/her account.  This function can implement
+            given access to the account.  This function can implement
             account expiration and access hour restrictions.
 
         (c) Session management: This set includes the `pam_open_session()'
diff --git a/libpam/pam_audit.c b/libpam/pam_audit.c
index 5619ba0c..1fe37c3f 100644
--- a/libpam/pam_audit.c
+++ b/libpam/pam_audit.c
@@ -44,7 +44,7 @@ _pam_audit_writelog(pam_handle_t *pamh, int audit_fd, int type,
       free(buf);
   }
 
-  /* libaudit sets errno to his own negative error code. This can be
+  /* libaudit sets errno to its own negative error code. This can be
      an official errno number, but must not. It can also be a audit
      internal error code. Which makes errno useless :-((. Try the
      best to fix it. */
diff --git a/modules/pam_env/pam_env.conf.5.xml b/modules/pam_env/pam_env.conf.5.xml
index 81fc9613..46df480f 100644
--- a/modules/pam_env/pam_env.conf.5.xml
+++ b/modules/pam_env/pam_env.conf.5.xml
@@ -58,7 +58,7 @@
       For example, ${HOME} is used below several times, but
       many PAM applications don't make it available by the time you need it.
       The special variables @{HOME} and @{SHELL} are expanded to the values
-      for the user from his <emphasis>passwd</emphasis> entry.
+      for the user from the corresponding <emphasis>passwd</emphasis> entry.
     </para>
 
     <para>
diff --git a/modules/pam_lastlog/pam_lastlog.8.xml b/modules/pam_lastlog/pam_lastlog.8.xml
index 1fd9d9dd..d9909787 100644
--- a/modules/pam_lastlog/pam_lastlog.8.xml
+++ b/modules/pam_lastlog/pam_lastlog.8.xml
@@ -289,7 +289,7 @@
     session  required  pam_lastlog.so nowtmp
       </programlisting>
     <para>
-     To reject the user if he did not login during the previous 50 days
+     To reject users if they did not login during the previous 50 days
      the following line can be used:
     </para>
       <programlisting>
@@ -337,4 +337,4 @@
       </para>
   </refsect1>
 
-</refentry>
\ No newline at end of file
+</refentry>
diff --git a/modules/pam_lastlog/pam_lastlog.c b/modules/pam_lastlog/pam_lastlog.c
index 02828033..43cc4b7d 100644
--- a/modules/pam_lastlog/pam_lastlog.c
+++ b/modules/pam_lastlog/pam_lastlog.c
@@ -677,7 +677,7 @@ pam_auth(pam_handle_t *pamh, int flags, int argc, const char **argv)
     int last_fd;
 
     /*
-     * Lock out the user if he did not login recently enough.
+     * Lock out users if they did not login recently enough.
      */
 
     ctrl = _pam_auth_parse(pamh, flags, argc, argv, &inactive_days);
diff --git a/modules/pam_limits/limits.conf.5.xml b/modules/pam_limits/limits.conf.5.xml
index 2177da1f..dd8d68bc 100644
--- a/modules/pam_limits/limits.conf.5.xml
+++ b/modules/pam_limits/limits.conf.5.xml
@@ -104,7 +104,7 @@
                 <para>
                   for enforcing <emphasis remap="B">hard</emphasis> resource limits.
                   These limits are set by the superuser and enforced by the Kernel.
-                  The user cannot raise his requirement of system resources above such values.
+                  Users cannot raise their own requirement of system resources above such values.
                 </para>
               </listitem>
             </varlistentry>
@@ -350,4 +350,4 @@ ftp             hard    nproc           0
       pam_limits was initially written by Cristian Gafton &lt;gafton@redhat.com&gt;
     </para>
   </refsect1>
-</refentry>
\ No newline at end of file
+</refentry>
diff --git a/modules/pam_sepermit/pam_sepermit.8.xml b/modules/pam_sepermit/pam_sepermit.8.xml
index 791d2bbe..114864a7 100644
--- a/modules/pam_sepermit/pam_sepermit.8.xml
+++ b/modules/pam_sepermit/pam_sepermit.8.xml
@@ -31,9 +31,9 @@
       enforcement state.
     </para>
     <para>
-      When the user which is logging in matches an entry in the config file
-      he is allowed access only when the SELinux is in enforcing mode. Otherwise
-      he is denied access. For users not matching any entry in the config file
+      When the users which are logging in match an entry in the config file
+      they are allowed access only when SELinux is in enforcing mode. Otherwise
+      they are denied access. For users not matching any entry in the config file
       the pam_sepermit module returns PAM_IGNORE return value.
     </para>
     <para>
@@ -192,4 +192,4 @@ session  required  pam_permit.so
       </para>
   </refsect1>
 
-</refentry>
\ No newline at end of file
+</refentry>
diff --git a/modules/pam_timestamp/pam_timestamp_check.8.xml b/modules/pam_timestamp/pam_timestamp_check.8.xml
index f0c09560..7f850ae0 100644
--- a/modules/pam_timestamp/pam_timestamp_check.8.xml
+++ b/modules/pam_timestamp/pam_timestamp_check.8.xml
@@ -72,7 +72,7 @@ see if the default timestamp is valid, or optionally remove it.
             <para>
                By default <command>pam_timestamp_check</command> checks or removes
                timestamps generated by <emphasis>pam_timestamp</emphasis> when
-               the user authenticates as herself. When the user authenticates as a
+               users authenticate as themselves. When the user authenticates as a
                different user, the name of the timestamp file changes to
                accommodate this. <replaceable>target_user</replaceable> allows
                one to specify this user name.
@@ -201,4 +201,4 @@ session optional pam_timestamp.so
       </para>
   </refsect1>
 
-</refentry>
\ No newline at end of file
+</refentry>