Reformat RST to avoid sphinx warnings

Old versions of docutils will see inline markup (e.g., :ref:`foo`)
at the beginning of a line in the content of a directive block
and attempt to interpret that markup as options or arguments
to the directive.  RST intended as inline markup (as opposed to
modifying the behavior of the directive) will not be interpretable
in this context, and causes Sphinx to emit a warning.

Work around this behavior by always leaving a blank line before
the content of a directive block, forcing it to be interpreted
as content and not options or arguments.

The buggy behavior was only encountered in note environments, but
for consistency of style, also reformat warning and error blocks.

Note the new style constraint in doc/README.

ticket: 7469 (new)
title: doc buildslave generates sphinx warnings
tags: pullup
target_version: 1.11

1 files changed, 6 insertions, 2 deletions

diff --git a/doc/admin/troubleshoot.rst b/doc/admin/troubleshoot.rst
index 7dc25795d8..3e1cbd64f5 100644
--- a/doc/admin/troubleshoot.rst
+++ b/doc/admin/troubleshoot.rst
@@ -31,10 +31,14 @@ of the :ref:`kvno(1)` command::
 List
 ----
 
-.. error:: KDC has no support for encryption type while getting
+.. error::
+
+           KDC has no support for encryption type while getting
            initial credentials
 
-.. error:: credential verification failed: KDC has no support for
+.. error::
+
+           credential verification failed: KDC has no support for
            encryption type
 
 This most commonly happens when trying to use a principal with only