webadmin: remove asciidoctor errors and html syntax issues

* removed rest-api docs due to it now being hosted on it's own github pages
* updated links to be relative instead of absolute
* downgraded leveloffset on certain files to disable too deep of an offset
* fixed generation of footnotes in code blocks

Signed-off-by: Jasper Berton <jasper.berton@team.blue>

Author: JasperB-TeamBlue

source/documentation/administration_guide/appe-enabling_FIPS.adoc

@@ -41,7 +41,7 @@ include::topics/proc-enabling-fips_she.adoc[leveloffset=+1]
 
 include::topics/proc-enabling-fips_rhel_hosts_and_rhvm.adoc[leveloffset=+1]
 
-== Additional resources
+.Additional resources
 
 * link:{URL_downstream_virt_product_docs}installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/index#Installing_Red_Hat_Virtualization_Hosts_SHE_cli_deploy[Installing {virt-product-fullname} Hosts]
 * link:https://www.redhat.com/en/blog/configuring-and-applying-scap-policies-during-installation[Configuring and Applying SCAP Policies During Installation]

source/documentation/administration_guide/topics/Updating_a_host_between_minor_releases.adoc

@@ -7,15 +7,15 @@
 
 You can update xref:Updating_all_hosts_in_a_cluster_admin[all hosts in a cluster], or update xref:Updating_Individual_Hosts_admin[individual hosts].
 
-include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+1]
+include::../common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc[leveloffset=+0]
 
-include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+1]
+include::../common/upgrade/proc-Updating_Individual_Hosts.adoc[leveloffset=+0]
 
 [NOTE]
 ====
 You should update the hosts from the Administration Portal. However, you can update the hosts using `dnf upgrade` instead.
 ====
 
-include::../common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+1]
+include::../common/upgrade/proc-Manually_Updating_Hosts.adoc[leveloffset=+0]
 
 :admin_minor_updates!:

source/documentation/common/install/con-Recommended_practices_for_configuring_host_networks.adoc

@@ -2,15 +2,15 @@
 [id="Recommended_practices_for_configuring_host_networks_{context}"]
 = Recommended Practices for Configuring Host Networks
 
-IMPORTANT: Always use the {virt-product-shortname} {engine-name} to modify the network configuration of hosts in your clusters. Otherwise, you might create an unsupported configuration. For details, see link:{URL_virt_product_docs}{URL_format}administration_guide/index#con-Network-Manager-Stateful-Configuration-nmstate[Network Manager Stateful Configuration (nmstate)].
+IMPORTANT: Always use the {virt-product-shortname} {engine-name} to modify the network configuration of hosts in your clusters. Otherwise, you might create an unsupported configuration. For details, see link:/documentation/administration_guide/index.html#con-Network-Manager-Stateful-Configuration-nmstate[Network Manager Stateful Configuration (nmstate)].
 
 If your network environment is complex, you may need to configure a host network manually before adding the host to the {virt-product-fullname} {engine-name}.
 
 Consider the following practices for configuring a host network:
 
 * Configure the network with Cockpit. Alternatively, you can use `nmtui` or `nmcli`.
 
-* If a network is not required for a self-hosted engine deployment or for adding a host to the {engine-name}, configure the network in the Administration Portal after adding the host to the {engine-name}. See link:{URL_virt_product_docs}{URL_format}administration_guide/index#Creating_a_new_logical_network_in_a_data_center_or_cluster[Creating a New Logical Network in a Data Center or Cluster].
+* If a network is not required for a self-hosted engine deployment or for adding a host to the {engine-name}, configure the network in the Administration Portal after adding the host to the {engine-name}. See link:/documentation/administration_guide/index.html#Creating_a_new_logical_network_in_a_data_center_or_cluster[Creating a New Logical Network in a Data Center or Cluster].
 
 * Use the following naming conventions:
 
@@ -19,13 +19,13 @@ Consider the following practices for configuring a host network:
 ** Bond interfaces: `bond__number__` (for example, `bond0`, `bond1`)
 ** VLANs on bond interfaces: `bond__number__.__VLAN_ID__` (for example, `bond0.50`, `bond1.128`)
 
-* Use link:{URL_virt_product_docs}{URL_format}administration_guide/index#sect-Network_Bonding[network bonding]. Network teaming is not supported in {virt-product-fullname} and will cause errors if the host is used to deploy a self-hosted engine or added to the {engine-name}.
+* Use link:/documentation/administration_guide/index#sect-Network_Bonding[network bonding]. Network teaming is not supported in {virt-product-fullname} and will cause errors if the host is used to deploy a self-hosted engine or added to the {engine-name}.
 
 * Use recommended bonding modes:
 
 ** If the `ovirtmgmt` network is not used by virtual machines, the network may use any supported bonding mode.
 ** If the `ovirtmgmt` network is used by virtual machines, see link:https://access.redhat.com/solutions/67546[_Which bonding modes work when used with a bridge that virtual machine guests or containers connect to?_].
-** {virt-product-fullname}'s default bonding mode is `(Mode 4) Dynamic Link Aggregation`. If your switch does not support Link Aggregation Control Protocol (LACP), use `(Mode 1) Active-Backup`. See link:{URL_virt_product_docs}{URL_format}administration_guide/index#Bonding_Modes[Bonding Modes] for details.
+** {virt-product-fullname}'s default bonding mode is `(Mode 4) Dynamic Link Aggregation`. If your switch does not support Link Aggregation Control Protocol (LACP), use `(Mode 1) Active-Backup`. See link:/documentation/administration_guide/index.html#Bonding_Modes[Bonding Modes] for details.
 
 * Configure a VLAN on a physical NIC as in the following example (although `nmcli` is used, you can use any tool):
 +
@@ -48,4 +48,4 @@ Consider the following practices for configuring a host network:
 
 * Do not disable `firewalld`.
 
-* Customize the firewall rules in the Administration Portal after adding the host to the {engine-name}. See link:{URL_virt_product_docs}{URL_format}administration_guide/index#Configuring_Host_Firewall_Rules[Configuring Host Firewall Rules].
+* Customize the firewall rules in the Administration Portal after adding the host to the {engine-name}. See link:/documentation/administration_guide/index.html#Configuring_Host_Firewall_Rules[Configuring Host Firewall Rules].

source/documentation/common/install/proc-customizing_engine_vm_during_deployment_auto.adoc

@@ -34,5 +34,5 @@ When you run the self-hosted-engine installer, the deployment script runs the `o
 .Additional resources
 
 * link:{URL_downstream_virt_product_docs}installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/index#Deploying_the_Self-Hosted_Engine_Using_the_CLI_install_RHVM[Deploying the self-hosted engine using the command line]
-* link:{URL_virt_product_docs}{URL_format}administration_guide/index#chap-Automating_RHV_Configuration_using_Ansible[Automating Configuration Tasks using Ansible]
+* link:/documentation/administration_guide/index#chap-Automating_RHV_Configuration_using_Ansible[Automating Configuration Tasks using Ansible]
 * link:https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html[Intro to playbooks] in the Ansible documentation

source/documentation/common/sriov/assembly-Set_Up_and_Configure_SR-IOV.adoc

@@ -71,7 +71,7 @@ The following example shows you how to get diagnostic information about the VFs
 
 // include::conc-What-are-SR-IOV-and-ARI.adoc[leveloffset=+1]
 
-== Additional Resources
+.Additional Resources
 
 * link:https://access.redhat.com/solutions/3867761[How to configure SR-IOV passthrough for RHV VM?]
 * link:https://access.redhat.com/articles/3215851[How to configure bonding with SR-IOV VF(Virtual Function) in RHV]

source/documentation/common/upgrade/proc-Updating_all_hosts_in_a_cluster.adoc

@@ -11,7 +11,7 @@ Update one cluster at a time.
 //Limitations
 include::snip-Host_update_limitations.adoc[]
 
-.Procedure
+. Procedure
 
 . In the Administration Portal, click menu:Compute[Clusters] and select the cluster. The *Upgrade status* column shows if an upgrade is available for any hosts in the cluster.
 . Click *Upgrade*.

source/documentation/common/vgpu/proc_removing-intel-vgpu-devices.adoc

@@ -39,7 +39,7 @@ echo: write error: Device or resource busy
 
 ////
 [discrete]
-== Additional resources
+.Additional resources
 
 * A bulleted list of links to other material closely related to the contents of the procedure module.
 * For more details on writing procedure modules, see the link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].

source/documentation/common/vgpu/proc_setting-up-intel-vgpu-devices.adoc

@@ -138,7 +138,7 @@ Windows only: Powering off the virtual machine from within the Windows guest ope
 
 ////
 [discrete]
-== Additional resources
+.Additional resources
 
 * A bulleted list of links to other material closely related to the contents of the procedure module.
 * For more details on writing procedure modules, see the link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].