Fix a few RST warnings

They were detected during a deep dive in ONAP doc issues.

Issue-ID: DOC-782
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
Change-Id: Ib668d427e32a12a1d63b5405f79b99c69daf4007
(cherry picked from commit e93d7217627637d980dc76fa10fb981d61bfc1b8)

diff --git a/docs/docs_E2E_network_slicing.rst b/docs/docs_E2E_network_slicing.rst
index 2de9719..2845e12 100644 (file)
--- a/docs/docs_E2E_network_slicing.rst
+++ b/docs/docs_E2E_network_slicing.rst
@@ -1,6 +1,8 @@
 .. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
 .. Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
 
+:orphan:
+
 .. contents::
    :depth: 3
 ..

diff --git a/docs/docs_StndDefined_Events_Collection_Mechanism.rst b/docs/docs_StndDefined_Events_Collection_Mechanism.rst
index 52352b4..cc5f00e 100644 (file)
--- a/docs/docs_StndDefined_Events_Collection_Mechanism.rst
+++ b/docs/docs_StndDefined_Events_Collection_Mechanism.rst
@@ -1,10 +1,10 @@
 .. This work is licensed under a Creative Commons Attribution 4.0
    International License. http://creativecommons.org/licenses/by/4.0
 
-.. _docs_StndDefined_Events_Collection_Mechanism:
-
 :orphan:
 
+.. _docs_StndDefined_Events_Collection_Mechanism:
+
 VES Collector - Standard Defined Events Collection Mechanism
 ------------------------------------------------------------
 
@@ -24,8 +24,8 @@ and providing them for consumption by analytics applications running on top of D
 
    VES Collector orchestrated using Helm or Cloudify uses standard defined domain schema files bundled within VES collector image during image build.
    Also new Helm based installation mechanism for collectors doesn't support yet certain features available with the traditional Cloudify orchestration based mechanisms:
-      - Obtaining X.509 certificates from external CMP v2 server for secure xNF connections
-      - Exposing the Collector port in Dual Stack IPv4/IPv6 networks.
+   - Obtaining X.509 certificates from external CMP v2 server for secure xNF connections
+   - Exposing the Collector port in Dual Stack IPv4/IPv6 networks.
 
 
 How to Configure VES Collector

diff --git a/docs/integration-s3p.rst b/docs/integration-s3p.rst
index be2edfe..3675c56 100644 (file)
--- a/docs/integration-s3p.rst
+++ b/docs/integration-s3p.rst
@@ -2,6 +2,8 @@
    Creative Commons Attribution 4.0 International License.
 .. _integration-s3p:
 
+:orphan:
+
 Stability
 =========
 

diff --git a/docs/integration-tooling.rst b/docs/integration-tooling.rst
index cc80ae2..c80e1df 100644 (file)
--- a/docs/integration-tooling.rst
+++ b/docs/integration-tooling.rst
@@ -20,7 +20,7 @@ Integration Project
 -------------------
 
 Integration portal
-..................
+~~~~~~~~~~~~~~~~~~
 
 A portal is built to report the status of the different labs collaborating in
 Integration, see http://testresults.opnfv.org/onap-integration/
@@ -33,7 +33,7 @@ The code of this web site is shared on a public gitlab project.
 
 
 Communication channels
-......................
+~~~~~~~~~~~~~~~~~~~~~~
 
 The main communication channel for real time support is the official ONAP
 Slack #integration-team chan (https://onapproject.slack.com/).
@@ -42,7 +42,7 @@ You can also send a mail to onap-discuss AT lists.onap.org
 with [ONAP] [Integration] prefix in the title.
 
 Repository management
-.....................
+~~~~~~~~~~~~~~~~~~~~~
 
 Since Integration team manages few dozens of different repositories a tool was provided to aid the process of mass editing the INFO.yaml files. It can be found `here <https://git.onap.org/integration/tree/ptl/edit_committers_info>`__.