M #-: remove versioning from RNs

Remove 7.0 RNs

Author: tinova

content/getting_started/understand_opennebula/opennebula_concepts/key_features.md

@@ -17,7 +17,7 @@ weight: "2"
 
 OpenNebula offers a simple but feature-rich and flexible solution to build and manage data center virtualization and enterprise clouds. This page provides a summary of its key features(\*).
 
-To learn more about the infrastructure platforms and services supported in each version of OpenNebula, please refer to the [Platform Notes]({{% relref "../../../software/release_information/release_notes_70/platform_notes.md#uspng" %}}) for each version.
+To learn more about the infrastructure platforms and services supported in each version of OpenNebula, please refer to the [Platform Notes]({{% relref "../../../software/release_information/release_notes/platform_notes.md#uspng" %}}) for each version.
 
 For high-level overviews and in-depth technical guides, please refer to OpenNebula’s [White Papers](https://opennebula.io/white-papers/).
 

content/getting_started/understand_opennebula/opennebula_concepts/opennebula_overview.md

@@ -130,7 +130,7 @@ The interactions between OpenNebula and the underlying cloud infrastructure are
 * **Networking**: The hypervisor is also prepared with the network configuration for each Virtual Machine.
 * **Event Bus**: A generic message bus where OpenNebula publishes resource events. The message bus is used to synchronize OpenNebula services as well as to integrate custom applications.
 
-The OpenNebula documentation provides a summary of its [key features]({{% relref "key_features#key-features" %}}). The [Platform Notes]({{% relref "../../../software/release_information/release_notes_70/platform_notes#uspng" %}}) list the infrastructure platforms and resources supported by each OpenNebula release. Because OpenNebula leverages the functionality exposed by the underlying platform services, its functionality and performance may be affected by the limitations imposed by those services.
+The OpenNebula documentation provides a summary of its [key features]({{% relref "key_features#key-features" %}}). The [Platform Notes]({{% relref "../../../software/release_information/release_notes/platform_notes#uspng" %}}) list the infrastructure platforms and resources supported by each OpenNebula release. Because OpenNebula leverages the functionality exposed by the underlying platform services, its functionality and performance may be affected by the limitations imposed by those services.
 
 ## Next Steps
 

content/product/cluster_configuration/backup_system/veeam.md

@@ -55,7 +55,7 @@ The OpenNebula-Veeam® Backup Integration works by exposing a native **oVirt-
 
 ## Compatibility
 
-The oVirtAPI module is compatible with the Veeam Backup & Replication version specified in the [Platform Notes]({{% relref "../../../software/release_information/release_notes_70/platform_notes/#monitoring-and-backups" %}}).
+The oVirtAPI module is compatible with the Veeam Backup & Replication version specified in the [Platform Notes]({{% relref "../../../software/release_information/release_notes/platform_notes/#monitoring-and-backups" %}}).
 
 The following table summarizes the supported backup modes for each storage system:
 
@@ -109,7 +109,7 @@ Here is a list of the limitations affecting the Veeam integration with OpenNebul
 - During image transfers, you may see a warning message stating ``Unable to use transfer URL for image transfer: Switched to proxy URL. Backup performance may be affected``. This is expected and shouldn't affect performance.
 - Spaces are not allowed in Virtual Machine names in the integration, so avoid using them (even if they are allowed in OpenNebula itself), otherwise you may face issues when performing an in-place restores of said VMs.
 
-If facing other issues or bugs, we highly encourage to check the Veeam section of the [Known Issues page]({{% relref "../../../software/release_information/release_notes_70/known_issues/#backups---veeam" %}}).
+If facing other issues or bugs, we highly encourage to check the Veeam section of the [Known Issues page]({{% relref "../../../software/release_information/release_notes/known_issues/#backups---veeam" %}}).
 
 ## Architecture
 
@@ -140,7 +140,7 @@ The minimum hardware specifications are:
 
 - **CPU:** 8 cores
 - **Memory:** 16 GB RAM
-- **Disk:** Sufficient storage to hold all active backup operations. See more details regarding the storage requirement in the next section. 
+- **Disk:** Sufficient storage to hold all active backup operations. See more details regarding the storage requirement in the next section.
 
 ### Storage Requirements
 

content/software/installation_process/manual_installation/overview.md

@@ -12,7 +12,7 @@ weight: "1"
 
 <!--# Overview -->
 
-The Front-end is the central part of an OpenNebula installation and is the very first thing that needs to be deployed (or upgraded). Typically it’s a Host where the OpenNebula server-side components are installed and which is responsible for the management of an entire virtualization stack. It can be a physical Host or a Virtual Machine (this decision is left up to the cloud administrator) as long as it matches the [requirements]({{% relref "../../../software/release_information/release_notes_72/platform_notes#uspng" %}}).
+The Front-end is the central part of an OpenNebula installation and is the very first thing that needs to be deployed (or upgraded). Typically it’s a Host where the OpenNebula server-side components are installed and which is responsible for the management of an entire virtualization stack. It can be a physical Host or a Virtual Machine (this decision is left up to the cloud administrator) as long as it matches the [requirements]({{% relref "../../../software/release_information/release_notes/platform_notes#uspng" %}}).
 
 ## How Should I Read This Chapter