Grammatical fixes from Paul Janzen

diff --git a/sudo.pod b/sudo.pod
index b62bea87e345060f08d7ed4f3c87589e30ac3724..e8427662d33b39891aa8344e5e91894d8796498a 100644 (file)
--- a/sudo.pod
+++ b/sudo.pod
@@ -74,7 +74,7 @@ to run sudo with the B<-l> or B<-v> flags.  This allows users to
 determine for themselves whether or not they are allowed to use
 B<sudo>.
 
-B<sudo> can log both successful an unsuccessful attempts (as well
+B<sudo> can log both successful and unsuccessful attempts (as well
 as errors) to syslog(3), a log file, or both.  By default B<sudo>
 will log via syslog(3) but this is changeable at configure time
 or via the I<sudoers> file.
@@ -147,7 +147,7 @@ with resources limited by the specified login class.  The I<class>
 argument can be either a class name as defined in /etc/login.conf,
 or a single '-' character.  Specifying a I<class> of C<-> indicates
 that the command should be run restricted by the default login
-capibilities for the user the command is run as.  If the I<class>
+capabilities for the user the command is run as.  If the I<class>
 argument specifies an existing user class, the command must be run
 as root, or the B<sudo> command must be run from a shell that is already
 root.  This option is only available on systems with BSD login classes
@@ -237,7 +237,7 @@ B<sudo> will check the ownership of its timestamp directory
 (F<@timedir@> by default) and ignore the directory's contents if
 it is not owned by root and only writable by root.  On systems that
 allow non-root users to give away files via chown(2), if the timestamp
-directory is located in a directory writable by anyone (eg: F</tmp>),
+directory is located in a directory writable by anyone (e.g.: F</tmp>),
 it is possible for a user to create the timestamp directory before
 B<sudo> is run.  However, because B<sudo> checks the ownership and
 mode of the directory and its contents, the only damage that can

diff --git a/visudo.pod b/visudo.pod
index 13fe9fa9000f88545d1dd7ead0db1e07150f4bc3..120d4b7e32341a1c9c597d9e6784c0b3c21c2f4a 100644 (file)
--- a/visudo.pod
+++ b/visudo.pod
@@ -52,7 +52,7 @@ for parse errors.  If the I<sudoers> file is currently being
 edited you will receive a message to try again later.
 
 There is a hard-coded list of editors that B<visudo> will use set
-at compile time that may be overridden via the I<editor> I<sudoers>
+at compile-time that may be overridden via the I<editor> I<sudoers>
 C<Default> variable.  This list defaults to the path to vi(1) on
 your system, as determined by the I<configure> script.  Normally,
 B<visudo> does not honor the C<EDITOR> or C<VISUAL> environment
@@ -65,22 +65,21 @@ execute any program they wish simply by setting C<EDITOR> or C<VISUAL>.
 
 B<visudo> parses the I<sudoers> file after the edit and will
 not save the changes if there is a syntax error.  Upon finding
-an error, a message will be printed stating the line number(s)
+an error, B<visudo> will print a message stating the line number(s)
 where the error occurred and the user will receive the
 "What now?" prompt.  At this point the user may enter "e"
-to re-edit the I<sudoers> file, enter "x" to exit without
+to re-edit the I<sudoers> file, "x" to exit without
 saving the changes, or "Q" to quit and save changes.  The
 "Q" option should be used with extreme care because if B<visudo>
 believes there to be a parse error, so will B<sudo> and no one
-will be able to execute B<sudo> again until the error is fixed.
-Any other command at this prompt will print a short help message.
-When editing the I<sudoers> file after a parse error has been
-detected the cursor will be placed on the line where the error
-occurred (if the editor supports this feature).
+will be able to B<sudo> again until the error is fixed.
+If "e" is typed to edit the  I<sudoers> file after a parse error
+has been detected, the cursor will be placed on the line where the
+error occurred (if the editor supports this feature).
 
 =head1 OPTIONS
 
-B<visudo> accepts the following command line option:
+B<visudo> accepts the following command line options:
 
 =over 4
 
@@ -94,7 +93,7 @@ letters, digits, and the underscore ('_') character.
 
 =item -V
 
-The B<-V> (version) option causes B<visudo> to print the version number
+The B<-V> (version) option causes B<visudo> to print its version number
 and exit.
 
 =back
@@ -122,7 +121,7 @@ defining it or you have a user or hostname listed that
 consists solely of upper case letters, digits, and the
 underscore ('_') character.  If the latter, you can ignore
 the warnings (B<sudo> will not complain).  In B<-s> (strict)
-mode these are errors not warnings.
+mode these are errors, not warnings.
 
 =back
 
@@ -131,8 +130,8 @@ mode these are errors not warnings.
 The following environment variables are used only if B<visudo>
 was configured with the I<--with-env-editor> option:
 
- EDITOR                        Used by visudo as the editor to use
- VISUAL                        Used by visudo if EDITOR is not set
+ EDITOR                        Invoked by visudo as the editor to use
+ VISUAL                        Used Invoked visudo if EDITOR is not set
 
 =head1 FILES
 
@@ -141,7 +140,7 @@ was configured with the I<--with-env-editor> option:
 
 =head1 AUTHOR
 
-Many people have worked on I<sudo> over the years, this version of
+Many people have worked on I<sudo> over the years; this version of
 B<visudo> was written by:
 
  Todd Miller           <Todd.Miller@courtesan.com>