Fixed broken hyperlinks per OP-4458 (#52)

doc/applications-onboard/network-edge-applications-onboarding.md

@@ -49,7 +49,7 @@ This document will explain the build and deployment to two applications
 2. OpenVINO application: A close to real-world inference application 
 
 ## Building Sample Application images
-The sample application is available in this [location in edgeapps repository](https://github.com/open-ness/edgeapps/tree/master/sample-app), further information about the application is contained within `Readme.md` file.
+The sample application is available in this [location in edgeapps repository](https://github.com/open-ness/edgeapps/tree/master/applications/sample-app), further information about the application is contained within `Readme.md` file.
 
 To build the sample application Docker images for testing OpenNESS EAA with the consumer and producer applications the following steps are required:
 
@@ -64,7 +64,7 @@ To build the sample application Docker images for testing OpenNESS EAA with the
    docker images | grep consumer
    ```
 ## Building the OpenVINO Application images
-The OpenVINO application is available in this [location in EdgeApps repository](https://github.com/open-ness/edgeapps/tree/master/openvino), further information about the application is contained within `Readme.md` file.
+The OpenVINO application is available in this [location in EdgeApps repository](https://github.com/open-ness/edgeapps/tree/master/applications/openvino), further information about the application is contained within `Readme.md` file.
 
 To build sample application Docker images for testing OpenVINO consumer and producer applications the following steps are required:
 

doc/applications-onboard/on-premises-applications-onboarding.md

@@ -170,7 +170,7 @@ Currently the applications are limited to 4096 MB RAM and 8 cores. Memory limit
 The OpenNESS [EdgeApps](https://github.com/open-ness/edgeapps) repository provides images for OpenNESS supported applications. They should be downloaded on machine where docker is installed.
 
 ## Building the OpenVINO Application images
-The OpenVINO application is available in this [location in EdgeApps repository](https://github.com/open-ness/edgeapps/tree/master/openvino), further information about the application is contained within `Readme.md` file.
+The OpenVINO application is available in this [location in EdgeApps repository](https://github.com/open-ness/edgeapps/tree/master/applications/openvino), further information about the application is contained within `Readme.md` file.
 
 To build sample application Docker images for testing OpenVINO consumer and producer applications the following steps are required:
 

doc/applications/openness_appguide.md

@@ -119,9 +119,9 @@ OpenNESS supports this by ability to deploy public cloud IOT gateways from cloud
 
 _Figure - Example of Cloud Adapter Edge Application in OpenNESS Platform_
 
-More details about running Baidu OpenEdge as OpenNESS application can be found here [Baidu OpenEdge  Edge Application](https://github.com/open-ness/specs/blob/master/doc/openness_baiducloud.md). 
+More details about running Baidu OpenEdge as OpenNESS application can be found here [Baidu OpenEdge  Edge Application](https://github.com/open-ness/specs/blob/master/doc/cloud-adapters/openness_baiducloud.md).
 
-More details about running Amazon AWS IoT Greengrass as OpenNESS application can be found here  [Amazon AWS IoT Greengrass Edge Application](https://github.com/open-ness/specs/blob/master/doc/openness_awsgreengrass.md). 
+More details about running Amazon AWS IoT Greengrass as OpenNESS application can be found here  [Amazon AWS IoT Greengrass Edge Application](https://github.com/open-ness/specs/blob/master/doc/cloud-adapters/openness_awsgreengrass.md).
 
 ## Application On-boarding
 

doc/applications/openness_ovc.md

@@ -36,7 +36,7 @@ OpenNESS provides the underpinning network edge infrastructure which comprises o
 
 ![Smart City Architecure Deployed with OpenNESS](ovc-images/smart-city-architecture.png)
 
-The Open Visual Cloud website is located at [Open Visual Cloud project](https://01.org/openvisualcloud). The Smart City sample source code & documentation are available on [GitHub](https://github.com/OpenVisualCloud/Smart-City-Sample) and its integration with OpenNESS is available at [OpenNESS branch](https://github.com/OpenVisualCloud/Smart-City-Sample/tree/openness).
+The Open Visual Cloud website is located at [Open Visual Cloud project](https://01.org/openvisualcloud). The Smart City sample source code & documentation are available on [GitHub](https://github.com/OpenVisualCloud/Smart-City-Sample) and its integration with OpenNESS is available at [OpenNESS branch](https://github.com/open-ness/edgeapps/tree/master/applications/smart-city-app).
 
 ## The Smart City Building Blocks
 The Smart City sample consists of the following major building blocks:

doc/core-network/openness_epc.md

@@ -239,9 +239,9 @@ Further validation of this architecture will be carried out with commercial EPC
 -	[3GPP_23214]	TS 23.214 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for control and user plane separation of EPC nodes; Stage 2.
 -	[3GPP_29244]	TS 29.244 Interface between the Control Plane and the User Plane of EPC Nodes.
 -	[3GPP_29303]	TS 29.303 DNS procedures for UP function selection  
--	Control and User Plane Separation of EPC nodes (CUPS) (https://www.3gpp.org/cups)
+-	Control and User Plane Separation of EPC nodes (CUPS) (https://www.3gpp.org/news-events/1882-cups)
 -	[3GPP_23501]	3GPP TS 23.501 V15.1.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)” (2018-03)
--	[3GPP_CUPS]	"Control and User Plane Separation of EPC Nodes (CUPS)", https://www.3gpp.org/cups 
+-	[3GPP_CUPS]	"Control and User Plane Separation of EPC Nodes (CUPS)", https://www.3gpp.org/news-events/1882-cups
 -	[OpenNESS_2019]	"OpenNESS Architecture and Solution", white paper, 2019.
 
 ## List of Abbreviations

doc/getting-started/network-edge/controller-edge-node-setup.md

@@ -99,7 +99,7 @@ For example, when installing Docker, the RPM repository is added and Docker inst
 Note that there might be some leftovers created by installed software; for example, DPDK and Golang installations, found in `/opt`, are not rolled back.
 
 ### Supported EPA features
-A number of enhanced platform capabilities/features are available in OpenNESS for Network Edge. For the full list of features supported see [Enhanced Platform Awareness Features](supported-epa). The documents referenced in this list provide detailed description of the features, and step by step instructions for to enabling them. The user is advised to become familiar with the features available before executing the deployment playbooks.
+A number of enhanced platform capabilities/features are available in OpenNESS for Network Edge. For the full list of features supported see [Enhanced Platform Awareness Features](https://github.com/open-ness/specs/blob/master/doc/getting-started/network-edge/supported-epa.md). The documents referenced in this list provide detailed description of the features, and step by step instructions for to enabling them. The user is advised to become familiar with the features available before executing the deployment playbooks.
 
 ### VM support for Network Edge
 Support for VM deployment on OpenNESS for Network Edge is available and enabled by default. Certain configurations and pre-requisites may need to be satisfied in order to use all VM capabilities. The user is advised to become familiar with the VM support documentation before executing the deployment playbooks. Please see [openness-network-edge-vm-support](../../applications-onboard/openness-network-edge-vm-support) for more information.

doc/ran/openness_xran.md

@@ -17,7 +17,7 @@ Copyright © 2020 Intel Corporation
   - [xRAN Library](#xran-library)
   - [Packet Classification](#packet-classification)
   - [xRAN Library Sample Application](#xran-library-sample-application)
-  - [Precision Time Protocol Synchronization](precision-time-protocol-synchronization)
+  - [Precision Time Protocol Synchronization](#precision-time-protocol-synchronization)
   - [eCPRI DDP Profile](#ecpri-ddp-profile)
 - [xRAN Sample App Deployment in OpenNESS](#xran-sample-app-deployment-in-openness)
   - [Hardware Configuration and Checks](#hardware-configuration-and-checks)