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

public/develop/deployment_guide/deployment_guide/index.html

@@ -427,7 +427,7 @@ controller.</p>
 <li><a href="#111-physical-server">Physical Server</a></li>
 <li><a href="#112-oracle-virtual-box">Oracle Virtual Box</a></li>
 <li><a href="#113-vmware-fusion">VMWare Fusion</a></li>
-<li><a href="#114-openstack1-1-4-openstack">OpenStack'</a></li>
+<li><a href="#114-openstack">OpenStack</a></li>
 <li><a href="#115-vagrant-box">Vagrant Box</a></li>
 </ul>
 <h3 id="111-physical-server"><strong>1.1.1. Physical Server</strong></h3>
@@ -935,28 +935,30 @@ second), run the following command:</p>
 <p>First, we need to enable the community plugins (maintained by third parties):</p>
 <pre><code class="language-bash">microk8s.enable community
 </code></pre>
-<p>The Addons to be enabled are:
-- <code>dns</code>: enables resolving the pods and services by name
-- <code>helm3</code>: required to install NATS
-- <code>hostpath-storage</code>: enables providing storage for the pods (required by <code>registry</code>)
-- <code>ingress</code>: deploys an ingress controller to expose the microservices outside Kubernetes
-- <code>registry</code>: deploys a private registry for the TFS controller images
-- <code>linkerd</code>: deploys the <a href="https://linkerd.io">linkerd service mesh</a> used for load balancing among replicas
-- <code>prometheus</code>: set of tools that enable TFS observability through per-component instrumentation
-- <code>metrics-server</code>: deploys the <a href="https://github.com/kubernetes-sigs/metrics-server">Kubernetes metrics server</a> for API access to service metrics</p>
+<p>The Addons to be enabled are:</p>
+<ul>
+<li><code>dns</code>: enables resolving the pods and services by name</li>
+<li><code>helm3</code>: required to install NATS</li>
+<li><code>hostpath-storage</code>: enables providing storage for the pods (required by <code>registry</code>)</li>
+<li><code>ingress</code>: deploys an ingress controller to expose the microservices outside Kubernetes</li>
+<li><code>registry</code>: deploys a private registry for the TFS controller images</li>
+<li><code>linkerd</code>: deploys the <a href="https://linkerd.io">linkerd service mesh</a> used for load balancing among replicas</li>
+<li><code>prometheus</code>: set of tools that enable TFS observability through per-component instrumentation</li>
+<li><code>metrics-server</code>: deploys the <a href="https://github.com/kubernetes-sigs/metrics-server">Kubernetes metrics server</a> for API access to service metrics</li>
+</ul>
 <pre><code class="language-bash">microk8s.enable dns helm3 hostpath-storage ingress registry prometheus metrics-server linkerd
 </code></pre>
-<p><strong>Important</strong>: Enabling some of the addons might take few minutes.
-Do not proceed with next steps until the addons are ready.
-Otherwise, the deployment might fail.
-To confirm everything is up and running:
-1. Periodically
-   <a href="./1.2.-Install-MicroK8s#check-status-of-kubernetes-and-addons">Check the status of Kubernetes</a>
-   until you see the addons [dns, ha-cluster, helm3, hostpath-storage, ingress, linkerd, metrics-server, prometheus, registry, storage] in the enabled block.
-2. Periodically
-   <a href="./1.2.-Install-MicroK8s#check-all-resources-in-kubernetes">Check Kubernetes resources</a>
-   until all pods are <strong>Ready</strong> and <strong>Running</strong>.
-3. If it takes too long for the Pods to be ready, <strong>we observed that rebooting the machine may help</strong>.</p>
+<p><strong>Important</strong>: Enabling some of the addons might take few minutes. Do not proceed with next steps until the addons are ready. Otherwise, the deployment might fail.
+To confirm everything is up and running:</p>
+<ol>
+<li>Periodically
+   <a href="#12-install-microk8s">Check the status of Kubernetes</a>
+   until you see the addons [dns, ha-cluster, helm3, hostpath-storage, ingress, linkerd, metrics-server, prometheus, registry, storage] in the enabled block.</li>
+<li>Periodically
+   <a href="">Check Kubernetes resources</a>
+   until all pods are <strong>Ready</strong> and <strong>Running</strong>.</li>
+<li>If it takes too long for the Pods to be ready, <strong>we observed that rebooting the machine may help</strong>.</li>
+</ol>
 <p>Then, create aliases to make the commands easier to access:</p>
 <pre><code class="language-bash">sudo snap alias microk8s.helm3 helm3
 sudo snap alias microk8s.linkerd linkerd