X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fguides%2Fonap-developer%2Fhow-to-use-docs%2Finclude-documentation.rst;h=fb32a3e369d988c6dc69b50fbad2e75fc48ab1e6;hb=7e34ab34754951cf640f09f80e523e8b340d0f2d;hp=4e76f6149d8d181e9ab93d20f323b659bd645f1e;hpb=1c0ba4b1e2ba3983fe51524e2652686b2f6a2080;p=doc.git

diff --git a/docs/guides/onap-developer/how-to-use-docs/include-documentation.rst b/docs/guides/onap-developer/how-to-use-docs/include-documentation.rst
index 4e76f6149..fb32a3e36 100644
--- a/docs/guides/onap-developer/how-to-use-docs/include-documentation.rst
+++ b/docs/guides/onap-developer/how-to-use-docs/include-documentation.rst
@@ -43,9 +43,13 @@ Setup doc project
 These steps are performed only once for the doc project and include:
 
 (1) creating in the doc repository an initial:
+
   - sphinx master document index
+
   - a directory structure aligned with the document structure
+
   - tests performed in jenkins verify jobs
+
   - sphinx configuration
 
 (2) establishing an account at readthedocs connected with the doc
@@ -217,7 +221,9 @@ Here are some conventions about GIT branches:
 The day of the release, the repository owner will create a new branch to
 fix the code and documentation. This will represent the 'stable' code of the
 release. In this context:
+
   - NEVER push a new feature on a stable branch
+
   - Only bug correction are authorized on a stable branch using cherry pick method
 
 .. image:: git_branches.png