diff --git a/overview/workflows.rst b/overview/workflows.rst
index dfe9497..8a0a149 100644
--- a/overview/workflows.rst
+++ b/overview/workflows.rst
@@ -20,8 +20,8 @@
 Given that NEM is not available in a plain VOLTHA deployment the user has to ensure proper config in the right places,
 and then triggering of api's themselves.
 
-To deploy a specific workflow follow the steps in the voltha-helm-charts
-`README <./../voltha-helm-charts/README.md#deploying-a-different-workflow>`_.
+To deploy a specific workflow follow the steps under `deploying-a-different-workflow` in the `voltha-helm-charts
+README <../voltha-helm-charts/README.md>`_.
 
 A workflow in VOLTHA entails different elements: Customer tag allocation, Technology profile, Bandwidth profile,
 Flow and Group Management
@@ -43,8 +43,11 @@
 Subscriber Services on an OpenFlow managed Logical Switch overlaid upon an OLT
 or other technology specific platform.
 
-More on Technology profiles here:
-https://wiki.opencord.org/display/CORD/Technology+Profiles#TechnologyProfiles-IntroductiontoTechnologyProfiles
+More information on Technology profiles can be found here:
+`2018/03/22 VOLTHA TST on Technology profile <https://youtu.be/L0JBJ3R1Mag>`_
+`VOLTHA technical notes on Technology profile <https://wiki-archive.opencord.org/attachments/4981667/4981671.docx>`_
+`VOLTHA Implementation of Technology profiles <https://wiki-archive.opencord.org/attachments/4981667/4981670.docx>`_
+`Technology profile instance example <https://wiki-archive.opencord.org/Technology-Profile-Instance_4982088.html>`_
 
 Technology profiles in VOLTHA are stored in ETCD. If you want to load a custom
 Technology profile in your stack you can do so by: