From 5f41948de9de64269bac91e91a9d7a609f38a661 Mon Sep 17 00:00:00 2001
From: "Todd C. Miller" <Todd.Miller@courtesan.com>
Date: Sat, 17 Oct 1998 20:19:08 +0000
Subject: [PATCH] environmental variable -> environment variable

---
 TROUBLESHOOTING | 4 ++--
 sudo.pod        | 8 ++++----
 visudo.pod      | 2 +-
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/TROUBLESHOOTING b/TROUBLESHOOTING
index 45a77632c..9c11fafbd 100644
--- a/TROUBLESHOOTING
+++ b/TROUBLESHOOTING
@@ -49,11 +49,11 @@ Q) When I run visudo it uses vi as the editor and I hate vi.  How
    can I make it use another editor?
 A) Your best bet is to run configure with the --with-env-editor switch.
    This will make visudo use the editor specified by the user's
-   EDITOR environmental variable.  Alternately, you can run configure
+   EDITOR environment variable.  Alternately, you can run configure
    with the --with-editor=path_to_your_editor.
 
 Q) Sudo appears to be removing some variables from my environment, why?
-A) Sudo removes the following "dangerous" environmental variables
+A) Sudo removes the following "dangerous" environment variables
    to guard against shared library spoofing, shell voodoo, and
    kerberos server spoofing.
      IFS
diff --git a/sudo.pod b/sudo.pod
index c62e41505..2ccfc28f3 100644
--- a/sudo.pod
+++ b/sudo.pod
@@ -89,12 +89,12 @@ I<username>, use "#uid".
 =item -s
 
 The C<-s> (I<shell>) option runs the shell specified by the I<SHELL>
-environmental variable if it is set or the shell as specified
+environment variable if it is set or the shell as specified
 in passwd(5).
 
 =item -H
 
-The C<-H> (I<HOME>) option sets the I<HOME> environmental variable
+The C<-H> (I<HOME>) option sets the I<HOME> environment variable
 to the homedir of the target user (root by default) as specified
 in passwd(5).
 
@@ -126,7 +126,7 @@ B<sudo> tries to be safe when executing external commands.
 Variables that control how dynamic loading and binding is
 done can be used to subvert the program that B<sudo> runs.
 To combat this the C<LD_*>, C<SHLIB_PATH> (HP-UX only),
-C<LIBPATH> (AIX only), and C<_RLD_*> environmental variables are
+C<LIBPATH> (AIX only), and C<_RLD_*> environment variables are
 removed from the environment passed on to all commands executed.
 B<sudo> will also remove the C<IFS>, C<ENV>, C<BASH_ENV>
 and C<KRB_CONF> variables as they too can pose a threat.
@@ -134,7 +134,7 @@ and C<KRB_CONF> variables as they too can pose a threat.
 To prevent command spoofing, B<sudo> checks "." and "" (both
 denoting current directory) last when searching for a command
 in the user's PATH (if one or both are in the PATH).
-Note, however, that the actual PATH environmental variable
+Note, however, that the actual PATH environment variable
 is I<not> modified and is passed unchanged to the program that
 B<sudo> executes.
 
diff --git a/visudo.pod b/visudo.pod
index 9b4c7f302..8fad47639 100644
--- a/visudo.pod
+++ b/visudo.pod
@@ -19,7 +19,7 @@ for parse errors.  If the I<sudoers> file is currently being
 edited you will receive a message to try again later.  In the
 default configuration, the vi(1) editor is used, but there is
 a compile time option to allow use of whatever editor the
-environmental variables C<EDITOR> or C<VISUAL> are set to.
+environment variables C<EDITOR> or C<VISUAL> are set to.
 
 B<visudo> parses the I<sudoers> file after the edit and will
 not save the changes if there is a syntax error.  Upon finding
-- 
2.40.0