VNFRQTS - Use case links fix

Issue-ID: VNFRQTS-552

Change-Id: I225b42c6007138e4cec27b08ab8d4e201e43aa2e
Signed-off-by: Hagop Bozawglanian <hagop.bozawglanian@att.com>

diff --git a/docs/Chapter7/Configuration-Management.rst b/docs/Chapter7/Configuration-Management.rst
index f86e4c2..bce9cbd 100755 (executable)
--- a/docs/Chapter7/Configuration-Management.rst
+++ b/docs/Chapter7/Configuration-Management.rst
@@ -12,6 +12,7 @@
    See the License for the specific language governing permissions and
    limitations under the License.
 
+.. _vnf_configuration_management:
 
 Configuration Management
 ------------------------
@@ -952,6 +953,8 @@ NETCONF RFCs.
     The xNF **MUST** conform to the NETCONF RFC 6242,
     "Using the Network Configuration Protocol over Secure Shell".
 
+.. _xnf_rest_apis:
+
 xNF REST APIs
 ^^^^^^^^^^^^^^^
 
@@ -1239,6 +1242,8 @@ action request against a Chef managed xNF.
    from each node where the push job has finished by accessing the Node
    Object attribute node['PushJobOutput'].
 
+.. _ansible_playbook_requirements:
+
 Ansible Standards and Capabilities
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

diff --git a/docs/Chapter7/index.rst b/docs/Chapter7/index.rst
index 5bb8262..77edf64 100755 (executable)
--- a/docs/Chapter7/index.rst
+++ b/docs/Chapter7/index.rst
@@ -12,6 +12,7 @@
    See the License for the specific language governing permissions and
    limitations under the License.
 
+.. _onap_management_requirements:
 
 ONAP Management Requirements
 ============================