Work around some pod2html issue.

diff --git a/sudoers.ldap.pod b/sudoers.ldap.pod
index 05a4c47907d80d402ccc4901e1e4844c795f464d..bcbf52169520f77cd35c91bdd234355d107dafc8 100644 (file)
--- a/sudoers.ldap.pod
+++ b/sudoers.ldap.pod
@@ -457,7 +457,7 @@ See the C<ldap.conf> entry in the L<EXAMPLES> section.
 
 Unless it is disabled at build time, B<sudo> consults the Name
 Service Switch file, F<@nsswitch_conf@>, to specify the I<sudoers>
-search order.  Sudo looks for a line beginning with C<sudoers:> and
+search order.  Sudo looks for a line beginning with C<sudoers>: and
 uses this to determine the search order.  Note that B<sudo> does
 not stop searching after the first match and later matches take
 precedence over earlier ones.

diff --git a/sudoers.pod b/sudoers.pod
index 82db17e339d371bdc45fdc03662c48d2066ae9e3..f54660cd7797d4c15689b79eff28e332156ad92d 100644 (file)
--- a/sudoers.pod
+++ b/sudoers.pod
@@ -238,7 +238,7 @@ Defaults entries are parsed in the following order: generic, host
 and user Defaults first, then runas Defaults and finally command
 defaults.
 
-See L</"SUDOERS OPTIONS"> for a list of supported Defaults parameters.
+See L<"SUDOERS OPTIONS"> for a list of supported Defaults parameters.
 
 =head2 User Specification
 
@@ -449,7 +449,11 @@ the site-wide I<sudoers> will be F</etc/sudoers> and the per-machine
 one will be F</etc/sudoers.local>.  To include F</etc/sudoers.local>
 from within F</etc/sudoers> we would use the following line in F</etc/sudoers>:
 
- #include /etc/sudoers.local
+=over 4
+
+C<#include /etc/sudoers.local>
+
+=back
 
 When B<sudo> reaches this line it will suspend processing of the
 current file (F</etc/sudoers>) and switch to F</etc/sudoers.local>.