X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=docs%2Fuse-cases.rst;h=d45a4a089001874b5fce0d6622ac49c708cd908f;hb=b472c167413a55a42fc7bfa08d2138f967a204fb;hp=4cbbed946032e4b4f3ae6a8a16aded97202e9a0c;hpb=0ed89abe5fcff73493b84d1fe1831487249d77e4;p=nonrtric.git

diff --git a/docs/use-cases.rst b/docs/use-cases.rst
index 4cbbed94..d45a4a08 100644
--- a/docs/use-cases.rst
+++ b/docs/use-cases.rst
@@ -25,7 +25,7 @@ This use case is a non-real-world closed-loop use case to demonstrate automated
 An application in the NONRTRIC senses the fault from the O-RU (O1-FM) and initiates a NETCONF reset operation (O1-CM) using the OAM controller. 
 More details about the use case can be found on the O-RAN SC wiki: `(RSAC) <https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=20878423>`_ and `(OAM) <https://wiki.o-ran-sc.org/display/OAM/Closed+loop+use+case>`_.
 
-Non-RT RIC provides two implementation versions of the recovery part of the use case. One in the form of a python
+Non-RT RIC provides multiple implementation versions of the recovery part of the use case. One in the form of a python
 script, and one utilizing the ONAP Policy Framework.
 
 Standalone Script Solution
@@ -37,13 +37,16 @@ change messages sent from the script and responds with alarm cleared messages to
 All parts are Dockerized and can be started as individual containers, in the same network, in Docker.
 
 The script based solution can be found in
-this `link <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=test/usecases/oruclosedlooprecovery/scriptversion;b=HEAD>`_.
+this `link <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=test/usecases/oruclosedlooprecovery;b=HEAD>`_.
+
+The Go implementation of the solution can also be found in
+this `link <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=test/usecases/oruclosedlooprecovery;b=HEAD>`_.
 
 ONAP Policy Solution
 ++++++++++++++++++++
 
-There is also another solution for performing the fronthaul recovery that is based on ONAP Policy Framework.
-A TOSCA Policy has been created that listens to DMaaP Message Router and sends a configuration change message via
+There is also another solution for performing the front-haul recovery that is based on `ONAP Policy Framework <https://wiki.onap.org/display/DW/Policy+Framework+Project>`_.
+A TOSCA Policy has been created that listens to DMaaP Message Router, makes a decision on an appropriate remedy and then signals the decision as a configuration change message via
 REST call to the OAM controller. The policy based solution can be
 found `here <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;a=tree;f=test/usecases/oruclosedlooprecovery/apexpolicyversion;b=HEAD>`_.
 
@@ -51,4 +54,4 @@ There is a `docker-compose <https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric.git;
 in the nonrtric repo for bringing up the complete standalone version of ONAP Policy Framework.
 
 The detailed instructions for deploying and running this policy are provided in
-the `wiki <https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=35881325>`_.
\ No newline at end of file
+the `wiki <https://wiki.o-ran-sc.org/display/RICNR/Run+O-RU+O-DU+Fronthaul++Recovery+usecase>`_.
\ No newline at end of file