Refer the user to the "Command Environment" section in description

of sudo's -i option.

diff --git a/doc/sudo.pod b/doc/sudo.pod
index d6cfef90e6b9843a37d7d725be665cb8aae6b244..092146046983b0fc07c9090067111f7740d363be 100644 (file)
--- a/doc/sudo.pod
+++ b/doc/sudo.pod
@@ -243,7 +243,10 @@ If no command is specified, an interactive shell is executed.
 B<sudo> attempts to change to that user's home directory before
 running the shell.  The security policy shall initialize the
 environment to a minimal set of variables, similar to what is present
-when a user logs in.
+when a user logs in.  The I<Command Environment> section in the
+L<sudoers(5)> manual documents how the B<-i> option affects the
+environment in which a command is run when the I<sudoers> policy
+is in use.
 
 =item -K
 

diff --git a/doc/sudoers.pod b/doc/sudoers.pod
index f538e7a744fccd6176f329f505f49ad5305e002b..4cd7dda941335e36acd56494362ee134ea136cb8 100644 (file)
--- a/doc/sudoers.pod
+++ b/doc/sudoers.pod
@@ -115,7 +115,7 @@ C<LIBPATH>, C<SHLIB_PATH>, and others.  These type of variables are
 removed from the environment before B<sudo> even begins execution
 and, as such, it is not possible for B<sudo> to preserve them.
 
-As a special case, If B<sudo>'s B<-i> option (initial login) is
+As a special case, if B<sudo>'s B<-i> option (initial login) is
 specified, I<sudoers> will initialize the environment regardless
 of the value of I<env_reset>.  The I<DISPLAY>, I<PATH> and I<TERM>
 variables remain unchanged; I<HOME>, I<MAIL>, I<SHELL>, I<USER>,