Correct bad reference links in user guide/pre-onboarding section

[doc.git] / docs / guides / onap-user / design / pre-onboarding / index.rst

diff --git a/docs/guides/onap-user/design/pre-onboarding/index.rst b/docs/guides/onap-user/design/pre-onboarding/index.rst
index 796c4f3..2509ee7 100644 (file)
--- a/docs/guides/onap-user/design/pre-onboarding/index.rst
+++ b/docs/guides/onap-user/design/pre-onboarding/index.rst
@@ -22,8 +22,9 @@ Generate Manifest and Package Artifacts
    to create TOSCA based VNF or PNF Onboarding Packages are not described
    here
 
    to create TOSCA based VNF or PNF Onboarding Packages are not described
    here
 

-The for onboarding the zip-file requires besides the HEAT template also a MANIFEST.json file, which describes the content of the package.
-To generate a MANIFEST.json file a script can be used offered by the SDC project:
+The for onboarding the zip-file requires besides the Heat template also a
+MANIFEST.json file, which describes the content of the package. To generate a
+MANIFEST.json file a script can be used offered by the SDC project:

 `generate-manifest.py`_
 
 These steps are performed outside SDC.
 `generate-manifest.py`_
 
 These steps are performed outside SDC.


@@ -32,7 +33,7 @@ These steps are performed outside SDC.
 onboarding. The requirements are found in the following document.
 
 
 onboarding. The requirements are found in the following document.
 
 

-`Heat requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter5/Heat/index.html>`_
+:ref:`Heat requirements<onap-vnfrqts-requirements:heat_requirements>`

 
 #. Put the Heat, ENV, nested Heat, and other files used by get-file in templates
    in a directory on a host, which supports python.
 
 #. Put the Heat, ENV, nested Heat, and other files used by get-file in templates
    in a directory on a host, which supports python.


@@ -72,9 +73,11 @@ Validate xNF Package (VNF/PNF)
 
 VNF and PNF packages have to follow the requirements described in:
 
 
 VNF and PNF packages have to follow the requirements described in:
 

-`VNF and PNF Modeling Requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter5/index.html>`_
+:ref:`VNF and PNF Modeling Requirements
+<onap-vnfrqts-requirements:tosca_requirements>`

 
 

-`ONAP Management Requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter7/index.html>`_
+:ref:`ONAP Management Requirements
+<onap-vnfrqts-requirements:onap_management_requirements>`

 
 For Validation of VNF and PNF packages the tools delivered by VNFSDK can be
 used:
 
 For Validation of VNF and PNF packages the tools delivered by VNFSDK can be
 used:


@@ -107,4 +110,4 @@ No VF functionality testing is performed at this stage.
 
 
 .. _generate-manifest.py: https://git.onap.org/sdc/tree/openecomp-be/tools/scripts/generate-manifest.py
 
 
 .. _generate-manifest.py: https://git.onap.org/sdc/tree/openecomp-be/tools/scripts/generate-manifest.py

-.. _example-packages: https://git.onap.org/sdc/tree/test-apis-ci/sdc-api-tests/chef-repo/cookbooks/sdc-api-tests/files/default/Files
\ No newline at end of file
+.. _example-packages: https://git.onap.org/sdc/tree/test-apis-ci/sdc-api-tests/chef-repo/cookbooks/sdc-api-tests/files/default/Files