docs: Ensure literalinclude directive rendering

Literalinclude directive is not rendered as such unless separated from
the surrounding paragraphs by blank lines (like all paragraphs) [1].

[1] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#literal-blocks

Issue-ID: OOM-1612
Change-Id: I51e7f8f2f99dfe157b24fe7c5ae4d62281d72e86
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>

diff --git a/docs/oom_quickstart_guide.rst b/docs/oom_quickstart_guide.rst
index 9478bcd..6023565 100644 (file)
--- a/docs/oom_quickstart_guide.rst
+++ b/docs/oom_quickstart_guide.rst
@@ -131,10 +131,12 @@ setting but for the demonstration VNFs the ip asssignment strategy assumes 10.0
 
 
 Example Keystone v2.0 
+
 .. literalinclude:: example-integration-override.yaml
    :language: yaml
 
 Example Keystone v3  (required for Rocky and later releases)
+
 .. literalinclude:: example-integration-override-v3.yaml
    :language: yaml