"upper case" -> "uppercase"

diff --git a/sudoers.pod b/sudoers.pod
index 4d31fa5615c10e8e5a5f4a8f73001f5e0791cc47..70b994229a89f1d7160095011c5c116dc6c3ab76 100644 (file)
--- a/sudoers.pod
+++ b/sudoers.pod
@@ -109,9 +109,9 @@ Each I<alias> definition is of the form
  Alias_Type NAME = item1, item2, ...
 
 where I<Alias_Type> is one of C<User_Alias>, C<Runas_Alias>, C<Host_Alias>,
-or C<Cmnd_Alias>.  A C<NAME> is a string of upper case letters, numbers,
+or C<Cmnd_Alias>.  A C<NAME> is a string of uppercase letters, numbers,
 and the underscore characters ('_').  A C<NAME> B<must> start with an
-upper case letter.  It is possible to put several alias definitions
+uppercase letter.  It is possible to put several alias definitions
 of the same type on a single line, joined by a colon (':').  E.g.,
 
  Alias_Type NAME = item1, item2, item3 : NAME = item4, item5

diff --git a/visudo.pod b/visudo.pod
index 120d4b7e32341a1c9c597d9e6784c0b3c21c2f4a..baeb153b83d43ecca848746ee08a56c9398bcc52 100644 (file)
--- a/visudo.pod
+++ b/visudo.pod
@@ -88,7 +88,7 @@ B<visudo> accepts the following command line options:
 Enable B<strict> checking of the I<sudoers> file.  If an alias is
 used before it is defined, B<visudo> will consider this a parse
 error.  Note that it is not possible to differentiate between an
-alias and a hostname or username that consists solely of upper case
+alias and a hostname or username that consists solely of uppercase
 letters, digits, and the underscore ('_') character.
 
 =item -V
@@ -118,7 +118,7 @@ Your userid does not appear in the system passwd file.
 
 Either you are using a {User,Runas,Host,Cmnd}_Alias before
 defining it or you have a user or hostname listed that
-consists solely of upper case letters, digits, and the
+consists solely of uppercase 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.