doc/rpm: use more inclusive language

See following inclusive language guide:
https://www.aswf.io/inclusive-language-guide/

Signed-off-by: Xavier Delaruelle <[email protected]>

Author: xdelaruelle

MIGRATING.rst

@@ -3282,8 +3282,8 @@ to guide for instance users when they try to evaluate a forbidden module:
       Software bar/1.0 is decommissioned, please now use bar/2.0
 
 When an evaluated module will soon be forbidden, a message is returned to the
-user to warn him/her of the near limit. An additional warning message can
-also be defined here with the ``--nearly-message`` option to guide users.
+user to warn them of the near limit. An additional warning message can also be
+defined here with the ``--nearly-message`` option to guide users.
 
 .. parsed-literal::
 

doc/source/cookbook/compiler-etc-dependencies.rst

@@ -8,7 +8,7 @@ for users to use, there is the problem of ensuring that the
 user is using the correct builds of everything. Generally,
 if an user is attempting to compile code making use of the system
 software collection, you want to ensure that the user is compiling
-his code with the same compiler that was used to compile the library.
+their code with the same compiler that was used to compile the library.
 This tends to be particularly true of C++ and Fortran code using modules,
 and parallel codes using MPI libraries.
 

doc/source/cookbook/modulefiles-in-git.rst

@@ -45,8 +45,8 @@ switches :envvar:`MODULEPATH` to a locally-created git clone of the
 Modulefiles. When unloaded, it switches :envvar:`MODULEPATH` back to the
 default.
 
-After this, any time a user wants to edit the Modulefiles, he works in
-his local git repo. After editing, testing, and committing to the local
+After this, any time a user wants to edit the Modulefiles, they work in
+their local git repo. After editing, testing, and committing to the local
 git repo, ``git push`` updates the main repository, which (assuming the
 user knows the password for user ``modules``) automatically updates
 ``/home/modules/modulefiles``.

doc/source/design/sticky-modules.rst

@@ -64,7 +64,7 @@ Specification
 - An error is reported when trying to unload a sticky or super-sticky module
 
   - As the expected unload is not performed
-  - So with the return code and message, user knows that what he/she asked for was not done
+  - So with the return code and message, user knows that what they asked for was not done
   - Same goes for the ``purge`` command: user expects no more module loaded
 
     - so an error is returned as after the command the sticky module is still loaded
@@ -73,7 +73,7 @@ Specification
 
     - the sticky module is unloaded as expected but a warning message is done
     - as the module was tagged not to be unloaded by default
-    - user should know he/she has done something specific
+    - user should know they have done something specific
 
 - Reporting an error during a ``purge`` may be considered inappropriate
 

doc/source/devel/add-new-maintainer.rst

@@ -6,7 +6,7 @@ Add a new maintainer
 This document is a guide on how to set a new person as a maintainer for
 Modules project.
 
-* Confirm he/she has read and understood the `Code of conduct`_ and
+* Confirm they have read and understood the `Code of conduct`_ and
   :ref:`Technical charter<CHARTER>` of the project
 * Add to the `maintainer GitHub's team`_
 * Invite to the `modules-maintainers chat room`_

share/rpm/environment-modules.spec.in

@@ -196,9 +196,9 @@ fi
 
 update-alternatives \
   --install %{_sysconfdir}/profile.d/modules.sh modules.sh %{_datadir}/Modules/init/profile.sh 40 \
-  --slave %{_sysconfdir}/profile.d/modules.csh modules.csh %{_datadir}/Modules/init/profile.csh \
-  --slave %{_datadir}/fish/vendor_conf.d/modules.fish modules.fish %{_datadir}/Modules/init/fish \
-  --slave %{_bindir}/modulecmd modulecmd %{_datadir}/Modules/libexec/modulecmd.tcl
+  --follower %{_sysconfdir}/profile.d/modules.csh modules.csh %{_datadir}/Modules/init/profile.csh \
+  --follower %{_datadir}/fish/vendor_conf.d/modules.fish modules.fish %{_datadir}/Modules/init/fish \
+  --follower %{_bindir}/modulecmd modulecmd %{_datadir}/Modules/libexec/modulecmd.tcl
 
 %postun
 if [ $1 -eq 0 ] ; then