Remove indent workaround in man page RST sources

docutils 0.10 properly adds indentation to example blocks in man
pages, so we do not need to force an extra indentation level.  Get rid
of the workaround wherever we use it.

ticket: 7954 (new)
target_version: 1.12.2
tags: pullup

5 files changed, 11 insertions, 31 deletions

diff --git a/doc/user/user_commands/klist.rst b/doc/user/user_commands/klist.rst
index 00ad0ffe5..c24c74132 100644
--- a/doc/user/user_commands/klist.rst
+++ b/doc/user/user_commands/klist.rst
@@ -44,9 +44,7 @@ OPTIONS
 
 **-f**
     Shows the flags present in the credentials, using the following
-    abbreviations:
-
-     ::
+    abbreviations::
 
         F    Forwardable
         f    forwarded
diff --git a/doc/user/user_commands/krb5-config.rst b/doc/user/user_commands/krb5-config.rst
index b4a87ff08..ee0fceaa3 100644
--- a/doc/user/user_commands/krb5-config.rst
+++ b/doc/user/user_commands/krb5-config.rst
@@ -71,9 +71,7 @@ krb5-config is particularly useful for compiling against a Kerberos
 installation that was installed in a non-standard location.  For example,
 a Kerberos installation that is installed in ``/opt/krb5/`` but uses
 libraries in ``/usr/local/lib/`` for text localization would produce
-the following output:
-
- ::
+the following output::
 
     shell% krb5-config --libs krb5
     -L/opt/krb5/lib -Wl,-rpath -Wl,/opt/krb5/lib -L/usr/local/lib -lkrb5 -lk5crypto -lcom_err
diff --git a/doc/user/user_commands/ksu.rst b/doc/user/user_commands/ksu.rst
index d1a8091b2..975c8989f 100644
--- a/doc/user/user_commands/ksu.rst
+++ b/doc/user/user_commands/ksu.rst
@@ -86,8 +86,7 @@ user's home directory, ksu attempts to access two authorization files:
 contains the name of a principal that is authorized to access the
 account.
 
-For example:
- ::
+For example::
 
     jqpublic@USC.EDU
     jqpublic/secure@USC.EDU
@@ -221,9 +220,7 @@ OPTIONS
     defined the source cache name is set to ``krb5cc_<source uid>``.
     The target cache name is automatically set to ``krb5cc_<target
     uid>.(gen_sym())``, where gen_sym generates a new number such that
-    the resulting cache does not already exist.  For example:
-
-     ::
+    the resulting cache does not already exist.  For example::
 
         krb5cc_1984.2
 
@@ -283,9 +280,7 @@ Ticket granting ticket options:
 **-e** *command* [*args* ...]
     ksu proceeds exactly the same as if it was invoked without the
     **-e** option, except instead of executing the target shell, ksu
-    executes the specified command. Example of usage:
-
-     ::
+    executes the specified command. Example of usage::
 
         ksu bob -e ls -lag
 
@@ -304,9 +299,7 @@ Ticket granting ticket options:
     list of commands that the principal is authorized to execute.  A
     principal name followed by a ``*`` means that the user is
     authorized to execute any command.  Thus, in the following
-    example:
-
-     ::
+    example::
 
         jqpublic@USC.EDU ls mail /local/kerberos/klist
         jqpublic/secure@USC.EDU *
@@ -338,9 +331,7 @@ Ticket granting ticket options:
     thus all options intended for ksu must precede **-a**.
 
     The **-a** option can be used to simulate the **-e** option if
-    used as follows:
-
-     ::
+    used as follows::
 
         -a -c [command [arguments]].
 
@@ -376,8 +367,7 @@ ksu can be compiled with the following four flags:
     called to obtain the names of "legal shells".  Note that the
     target user's shell is obtained from the passwd file.
 
-Sample configuration:
- ::
+Sample configuration::
 
     KSU_OPTS = -DGET_TGT_VIA_PASSWD -DPRINC_LOOK_AHEAD -DCMD_PATH='"/bin /usr/ucb /local/bin"
 
diff --git a/doc/user/user_config/k5identity.rst b/doc/user/user_config/k5identity.rst
index 21c340eab..cf5d95e56 100644
--- a/doc/user/user_config/k5identity.rst
+++ b/doc/user/user_config/k5identity.rst
@@ -51,9 +51,7 @@ The following example .k5identity file selects the client principal
 ``alice@KRBTEST.COM`` if the server principal is within that realm,
 the principal ``alice/root@EXAMPLE.COM`` if the server host is within
 a servers subdomain, and the principal ``alice/mail@EXAMPLE.COM`` when
-accessing the IMAP service on ``mail.example.com``:
-
- ::
+accessing the IMAP service on ``mail.example.com``::
 
     alice@KRBTEST.COM       realm=KRBTEST.COM
     alice/root@EXAMPLE.COM  host=*.servers.example.com
diff --git a/doc/user/user_config/k5login.rst b/doc/user/user_config/k5login.rst
index 90e486593..8a9753da3 100644
--- a/doc/user/user_config/k5login.rst
+++ b/doc/user/user_config/k5login.rst
@@ -18,9 +18,7 @@ EXAMPLES
 --------
 
 Suppose the user ``alice`` had a .k5login file in her home directory
-containing just the following line:
-
- ::
+containing just the following line::
 
     bob@FOOBAR.ORG
 
@@ -35,9 +33,7 @@ machine's default realm to access the ``alice`` account.
 
 Let us further suppose that ``alice`` is a system administrator.
 Alice and the other system administrators would have their principals
-in root's .k5login file on each host:
-
- ::
+in root's .k5login file on each host::
 
     alice@BLEEP.COM