diff --git a/overview/release_process.rst b/overview/release_process.rst
index e4e6a9f..3157f7c 100644
--- a/overview/release_process.rst
+++ b/overview/release_process.rst
@@ -74,22 +74,34 @@
 ONOS Apps
 ^^^^^^^^^
 
+:ref:`_howto_release_components_onos_components`
+
 The ONOS Apps need to be released in a different manner.
 
-There is a Jenkins job to release ONOS app: https://jenkins.opencord.org/job/onos-app-release.
-It requires to be triggered with specific parameters, as an example you can check the latest job in that pipeline.
+A dedicated Jenkins job is used to release ONOS app: https://jenkins.opencord.org/job/onos-app-release.
 
-1. Build with parameters: use the name of the repo (not of the app itself)
+The job will need to be initiated using specific parameters, for an example view the lateset pipeline job.
+
+1. `Build with parameters <https://jenkins.opencord.org/job/onos-app-release>`_: use the name of the repo (not of the app itself)
+   - appRepo: sadis
+   - appName: sadis
+   - apiVersion: `sadis:5.12.0-SNAPSHOT <https://gerrit.opencord.org/plugins/gitiles/sadis/+/refs/heads/master/api/pom.xml#22>`__
+   - nextApiVersion: version+1
+   - version: `sadis:5.12.0-SNAPSHOT <https://gerrit.opencord.org/plugins/gitiles/sadis/+/refs/heads/master/app/pom.xml#20>`__
+   - nextVersion: version+1
+   - branch: master
+   - jdkDistro: java-11-amazon-corretto
+
 2. Wait for build to complete
-3. Merge the patches on gerrit https://gerrit.opencord.org/q/owner:do-not-reply%2540opennetworking.org
-
+3. Merge the component patches on gerrit
+   - `View <https://gerrit.opencord.org/q/owner:do-not-reply%2540opennetworking.org>`_
    - Two pull requests are created modifying pom.xml.
    - Approve patch one (-SNAPSHOT: no)  to initiate a release build.
    - Approve patch two (-SNAPSHOT: yes) to revert pom.xml to a non-release version.
 
-4. Approval and merge will trigger a `jenkins job <https://jenkins.opencord.org/job/maven-publish_sadis/>`_ that publish
-   an artifact into the staging repo on `sonatype <https://oss.sonatype.org>`_.  From there the artifact will need
-   to be released into maven central.
+4. Approval and merge will trigger `jenkins::maven-publish_sadis <https://jenkins.opencord.org/job/maven-publish_sadis/>`_
+   that will publish an artifact into the staging repo on `sonatype <https://oss.sonatype.org>`_.
+   Once published to the staging server the artifact will need to be released to maven central.
 
    - Login into the sonatype server (for username and password contact michelle@opennetworking.org)
    - search for org.opencord
diff --git a/overview/troubleshooting.rst b/overview/troubleshooting.rst
index f61c1a4..12404b4 100644
--- a/overview/troubleshooting.rst
+++ b/overview/troubleshooting.rst
@@ -69,7 +69,7 @@
     wget "https://wiki.wireshark.org/Contrib?action=AttachFile&do=get&target=omci.lua"
     wget "https://wiki.wireshark.org/Contrib?action=AttachFile&do=get&target=BinDecHex.lua"
 
-- IMPORTANT - Apply `this <https://ask.wireshark.org/question/4557/bindechexlua-error-bad-argument-to-module-packageseeall/?answer=4573#post-id-4573>`_ fix to BinDecHex.lua.
+- IMPORTANT - Apply `this <http://ask.wireshark.org/question/4557/bindechexlua-error-bad-argument-to-module-packageseeall/?answer=4573#post-id-4573>`_ fix to BinDecHex.lua.
 
 - TODO NOTE - The BinDecHex.lua thread is 4 years old, is the patch still
   required or has it been incorporated into the code base ?