fix broken links

Change-Id: I47ad3e2f9d425a2165cb0112d58876d479cadb43
Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Issue-ID: DCAEGEN2-2291
(cherry picked from commit 7cac724fc70cc723c526d39eef1e8aaf4faf941b)

diff --git a/docs/sections/installation_oom.rst b/docs/sections/installation_oom.rst
index 1af68aa..2cb1bb0 100644 (file)
--- a/docs/sections/installation_oom.rst
+++ b/docs/sections/installation_oom.rst
@@ -25,13 +25,14 @@ DCAE charts are placed under the **dcaegen2** directory.
 
 All DCAE platform components  have corresponding Helm chart which will be used to trigger the deployment. 
 All DCAE Services are deployed through Cloudify Blueprint. The default ONAP DCAE deployment includes small subset of DCAE services deployed through Bootstrap pod to meet
-ONAP Integration usecases. Optionally operators can deploy on-demand other MS required for their usecases as described in `On-demand MS Installation
-<installation_MS_ondemand>`_.
+ONAP Integration usecases. Optionally operators can deploy on-demand other MS required for their usecases as described in :doc:`On-demand MS Installation
+<./installation_MS_ondemand>`.
+
 
 The PNDA data platform is an optional DCAE component that is placed under the **pnda**
 directory. Details for how to configure values to enable PNDA installation during Helm install
-are described in `Installing PNDA through Helm Chart
-<installation_pnda>`_.
+are described in :doc:`Installing PNDA through Helm Chart
+<./installation_pnda>`.
 
 
 DCAE Chart Organization