Fix broken links

docs/user_guide/set_up_edge_infra/location/site_details.rst

@@ -27,8 +27,8 @@ To edit site details, do the following:
 The **Edit Site** page appears.
 
 You can also make changes to the
-`Deployment Metadata <./add_site.html#advanced-settings-deployment-metadata>`__
-and `Telemetry <./add_site.html#advanced_settings_telemetry>`__.
+:ref:`Deployment Metadata <user_guide/set_up_edge_infra/location/add_site:advanced settings: deployment metadata>`
+and :ref:`Telemetry <user_guide/set_up_edge_infra/location/add_site:advanced settings: telemetry>`.
 
 
 

docs/user_guide/set_up_edge_infra/location/view_region_detail.rst

@@ -20,4 +20,4 @@ Note that the **Region Id** is automatically generated and cannot be modified.
     .. figure:: ../images/region_detail.png
        :alt: Region details
 
-You can also update or edit the `advanced settings <./add_region.html#advanced-settings>`__.
+You can also update or edit the :ref:`advanced settings <user_guide/set_up_edge_infra/location/add_region:advanced settings>`.

docs/user_guide/set_up_edge_infra/onboard_dell/racadm_on_linux.rst

@@ -129,8 +129,8 @@ is set to the OS Profile name you are trying to install (e.g. `microvisor-nonrt`
 .. note::
 
    To interact with Edge Orchestrator API, you must authenticate with a user who is
-   part of the `Edge Manager Group <./../../../shared/shared_iam_groups.html#project-id-host-manager-group>`__ and obtain a JWT token
-   used here as `JWT_TOKEN` variable (see `Obtaining a JSON Web Token (JWT) <./../../../shared/shared_gs_iam.html#obtaining-a-json-web-token-jwt>`__ for instructions).
+   part of the :ref:`Edge Manager Group <shared/shared_iam_groups:<project-id>_host-manager-group>` and obtain a JWT token
+   used here as `JWT_TOKEN` variable (see :ref:`Obtaining a JSON Web Token (JWT) <shared/shared_gs_iam:obtaining a json web token (jwt)>` for instructions).
 
    The variables `CLUSTER_FQDN` are `PROJECT_NAME` should be the same as used
    for obtaining the `JTW_TOKEN` value.

docs/user_guide/set_up_edge_infra/onboard_host_details.rst

@@ -143,7 +143,7 @@ View Host Label
 ~~~~~~~~~~~~~~~~
 
 Click the **Host Labels** tab to view the host label. For information about host
-label, see `host label <./provision_host.html#host-label>`__.
+label, see :ref:`host label <user_guide/set_up_edge_infra/provision_host:host label>`.
 
 .. figure:: images/host_label.png
    :alt: View Host Label

docs/user_guide/set_up_edge_infra/onboarded_hosts.rst

@@ -11,9 +11,9 @@ view the available onboarded hosts.
 You can search for a host using the search bar at the top of the page.
 
 Once onboarded, you can provision hosts with a custom name,
-`Operating System Profile <./provision_host.html#operating-system-profile>`__
+:ref:`Operating System Profile <user_guide/set_up_edge_infra/provision_host:operating system profile>`
 and security configuration,
-`host label <./provision_host.html#host-label>`__,
+:ref:`host label <user_guide/set_up_edge_infra/provision_host:host label>`,
 and associate them with their specific
 :doc:`location </user_guide/set_up_edge_infra/location_main>`.
 

docs/user_guide/set_up_edge_infra/provision_host.rst

@@ -43,7 +43,7 @@ The **Provision Host** feature allows you to provision an OS profile onto a prev
 #. On the final page, review the details of the host to be provisioned and confirm that it is correct. If there are any errors,
    you can use the **Previous** option at the bottom of the page to navigate to the incorrect page. Click **Next** to accept
    the configuration and to provision the host. If you are configuring one host, you have the option to create a cluster
-   for that host (the user must be a part of the `Project ID Edge Manager Group <../../shared/shared_iam_groups.html#project-id-edge-manager-group>`__).
+   for that host (the user must be a part of the :ref:`Project ID Edge Manager Group <shared/shared_iam_groups:<project-id>_edge-manager-group>`).
 
    .. figure:: images/default_cluster.png
       :alt: Default Cluster

docs/user_guide/troubleshooting/operate_issues.rst

@@ -19,7 +19,7 @@ hardware, or applications of Edge Orchestrator.
 * `VM is not responding <#vm-is-not-responding>`__
 * `Cannot connect to VM through VNC console or through SSH <#cannot-connect-to-vm-through-vnc-console-or-through-ssh>`__
 * `Ingress of VMs does not work <#ingress-of-vms-does-not-work>`__
-* `Troubleshooting Interconnect (Interconnect article) <../package_software/interconnect.html#troubleshooting-interconnect>`__
+* :ref:`user_guide/package_software/interconnect:troubleshooting interconnect`
 * `Docker\* Hub returns a 429 Too Many Requests error <#docker-hub-returns-a-429-too-many-requests-error>`__
 * `Host has error status immediately after provisioning <#host-error-status-after-provision>`__
 * `Application VM can't connect to it's cloud counterpart (Exceeded MTU) <#application-vm-can-t-connect-to-it-s-cloud-counterpart-exceeded-mtu>`__
@@ -281,7 +281,7 @@ by adding the credentials to a cluster template.
 
 To add Docker Hub account credentials to a cluster template, do the following:
 
-#. `Export the cluster template <../additional_howtos/export_cluster_template.html>`__ you wish to modify.
+#. :ref:`Export the cluster template <user_guide/additional_howtos/export_cluster_template:export cluster template>` you wish to modify.
 #. Download a raw copy of this file: https://github.com/open-edge-platform/cluster-manager/blob/v2.0.3/default-cluster-templates/config.toml.tmpl
 #. Add the following lines to the file: