Deployed e1778265 to develop in public with MkDocs 1.6.1 and mike 2.1.3

public/develop/deployment_guide/deployment_guide/index.html

@@ -921,7 +921,7 @@ To retrieve the status of Kubernetes <strong>once</strong>, run the following co
 following command:</p>
 <pre><code class="language-bash">watch -n 1 microk8s.status --wait-ready
 </code></pre>
-<h3><u>Check all resources in Kubernetes</h3>
+<h3><u id="check-all-resources-in-kubernetes">Check all resources in Kubernetes</h3>
 <p></u>
 To retrieve the status of the Kubernetes resources <strong>once</strong>, run the following command:</p>
 <pre><code class="language-bash">kubectl get all --all-namespaces
@@ -1098,9 +1098,9 @@ EOF
 <p>Confirm everything is up and running:</p>
 <ol>
 <li>Periodically <a href="#check-status-of-kubernetes-and-addons">Check the status of Kubernetes</a> until you see the addons [dns, ha-cluster, helm3, hostpath-storage, ingress, registry, storage] in the enabled block.</li>
-<li>Periodically <a href="/1.-Deployment-Guide/1.2.-Install-MicroK8s#check-all-resources-in-kubernetes">Check Kubernetes resources</a> until all pods are <strong>Ready</strong> and <strong>Running</strong>.</li>
+<li>Periodically <a href="#check-all-resources-in-kubernetes">Check Kubernetes resources</a> until all pods are <strong>Ready</strong> and <strong>Running</strong>.</li>
 </ol>
-<h3><u>Deploy TFS controller</h3>
+<h3><u id="deploy-tfs-controller">Deploy TFS controller</h3>
 <p></u>
 First, source the deployment settings defined in the previous section.
 This way, you do not need to specify the environment variables in each and every command you execute to operate the TFS controller.
@@ -1136,20 +1136,22 @@ source my_deploy.sh
 </li>
 <li>Initialize and configure the Grafana dashboards (if Monitoring component is deployed)</li>
 <li>Report a summary of the deployment</li>
-<li>See <a href="./1.5.-Show-Deployment-and-Logs">Show Deployment and Logs</a></li>
+<li>See <a href="#15-show-deployment-and-logs">Show Deployment and Logs</a></li>
 </ul>
 <h2 id="14-webui-and-grafana-dashboards"><strong>1.4. WebUI and Grafana Dashboards</strong></h2>
 <p>This section describes how to get access to the TeraFlowSDN controller WebUI and the monitoring Grafana dashboards.</p>
 <h3><u>Access the TeraFlowSDN WebUI</h3>
 <p></u>
 If you followed the installation steps based on MicroK8s, you got an ingress controller installed that exposes on TCP port 80.</p>
-<p>Besides, the ingress controller defines the following reverse proxy paths (on your local machine):
-- <code>http://127.0.0.1/webui</code>: points to the WebUI of TeraFlowSDN.
-- <code>http://127.0.0.1/grafana</code>: points to the Grafana dashboards.
+<p>Besides, the ingress controller defines the following reverse proxy paths (on your local machine):</p>
+<ul>
+<li><code>http://127.0.0.1/webui</code>: points to the WebUI of TeraFlowSDN.</li>
+<li><code>http://127.0.0.1/grafana</code>: points to the Grafana dashboards.
   This endpoint brings access to the monitoring dashboards of TeraFlowSDN.
-  The credentials for the <code>admin</code>user are those defined in the <code>my_deploy.sh</code> script, in the <code>TFS_GRAFANA_PASSWORD</code> variable.
-- <code>http://127.0.0.1/restconf</code>: points to the Compute component NBI based on RestCONF. 
-  This endpoint enables connecting external software, such as ETSI OpenSourceMANO NFV Orchestrator, to TeraFlowSDN.</p>
+  The credentials for the <code>admin</code>user are those defined in the <code>my_deploy.sh</code> script, in the <code>TFS_GRAFANA_PASSWORD</code> variable.</li>
+<li><code>http://127.0.0.1/restconf</code>: points to the Compute component NBI based on RestCONF. 
+  This endpoint enables connecting external software, such as ETSI OpenSourceMANO NFV Orchestrator, to TeraFlowSDN.</li>
+</ul>
 <p><strong>Note</strong>: In the creation of the VM, a forward from host TCP port 8080 to VM's TCP port 80 is configured, so the WebUIs and REST APIs of TeraFlowSDN should be exposed on the endpoint <code>127.0.0.1:8080</code> of your local machine instead of <code>127.0.0.1:80</code>.</p>
 <h2 id="15-show-deployment-and-logs"><strong>1.5. Show Deployment and Logs</strong></h2>
 <p>This section presents some helper scripts to inspect the status of the deployment and 
@@ -1158,7 +1160,7 @@ These scripts are particularly helpful for troubleshooting during execution of
 experiments, development, and debugging.</p>
 <h3><u>Report the deployment of the TFS controller</h3>
 <p></u></p>
-<p>The summary report given at the end of the <a href="./1.3.-Deploy-TeraFlowSDN#deploy-tfs-controller">Deploy TFS controller</a>
+<p>The summary report given at the end of the <a href="#deploy-tfs-controller">Deploy TFS controller</a>
 procedure can be generated manually at any time by running the following command.
 You can avoid sourcing <code>my_deploy.sh</code> if it has been already done.</p>
 <pre><code class="language-bash">cd ~/tfs-ctrl