UPDATES: updating link

doc/deployment_guide/deployment_guide.md

@@ -437,7 +437,7 @@ microk8s config > $HOME/.kube/config
 sudo reboot
 ```
 
-<h3><u>Check status of Kubernetes and addons</h3></u>
+<h3><u id="check-status-of-kubernetes-and-addons">Check status of Kubernetes and addons</h3></u>
 To retrieve the status of Kubernetes __once__, run the following command:
 ```bash
 microk8s.status --wait-ready
@@ -568,7 +568,7 @@ Please, clone from [ETSI-hosted GitLab code repository](https://labs.etsi.org/re
 
 
 <h3><u>Checkout the appropriate Git branch</h3></u>
-TeraFlowSDN controller versions can be found in the appropriate release tags and/or branches as described in [Home > Versions](/Home#versions).
+TeraFlowSDN controller versions can be found in the appropriate release tags and/or branches as described in [Home > Versions](https://tfs.etsi.org/news/).
 
 By default the branch *master* is checked out and points to the latest stable version of the TeraFlowSDN controller, while branch *develop* contains the latest developments and contributions under test and validation.
 
@@ -664,7 +664,7 @@ microk8s start
 
 Confirm everything is up and running:
 
-1. Periodically [Check the status of Kubernetes](/1.-Deployment-Guide/1.2.-Install-MicroK8s#check-status-of-kubernetes-and-addons) until you see the addons \[dns, ha-cluster, helm3, hostpath-storage, ingress, registry, storage\] in the enabled block.
+1. Periodically [Check the status of Kubernetes](#check-status-of-kubernetes-and-addons) until you see the addons \[dns, ha-cluster, helm3, hostpath-storage, ingress, registry, storage\] in the enabled block.
 2. Periodically [Check Kubernetes resources](/1.-Deployment-Guide/1.2.-Install-MicroK8s#check-all-resources-in-kubernetes) until all pods are **Ready** and **Running**.