X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fdevelopment%2Fdevtools%2Fdevtools.rst;h=cef06796d03ed7b4526a0a4236a938ab05ee3592;hb=e8a4d3adf8847a2eefdad7d167295b56d85407c4;hp=0cf11a4ce2771d01ec5c496b11083d29c005be81;hpb=5c851605e1037be1f3f3ad5a38fb1559478674c3;p=policy%2Fparent.git

diff --git a/docs/development/devtools/devtools.rst b/docs/development/devtools/devtools.rst
index 0cf11a4c..cef06796 100644
--- a/docs/development/devtools/devtools.rst
+++ b/docs/development/devtools/devtools.rst
@@ -58,7 +58,7 @@ ONAP Policy Framework has dependencies to the ONAP Parent *oparent* module, the
     policy/xacml-pdp \
     policy/distribution \
     policy/gui \
-    policy/engine "
+    policy/clamp "
 
     ##
     ## Help screen and exit condition (i.e. too few arguments)
@@ -152,7 +152,7 @@ Execution of the script above results in the following directory hierarchy in yo
     *  ~/git/onap/policy/docker
     *  ~/git/onap/policy/drools-applications
     *  ~/git/onap/policy/drools-pdp
-    *  ~/git/onap/policy/engine
+    *  ~/git/onap/policy/clamp
     *  ~/git/onap/policy/apex-pdp
     *  ~/git/onap/policy/xacml-pdp
     *  ~/git/onap/policy/distribution
@@ -198,10 +198,7 @@ Building ONAP Policy Framework Components
             <module>drools-applications</module>
             <module>distribution</module>
             <module>gui</module>
-            <!-- The engine repo is being deprecated,
-            and can be ommitted if not working with
-            legacy api and components. -->
-            <module>engine</module>
+            <module>clamp</module>
         </modules>
     </project>
 
@@ -233,7 +230,7 @@ Developing and Debugging each Policy Component
 Running a MariaDb Instance
 ++++++++++++++++++++++++++
 
-The Policy Framework requires a MariaDb instance running. The easiest way to do this is to run a docker image locally. 
+The Policy Framework requires a MariaDb instance running. The easiest way to do this is to run a docker image locally.
 
 One example on how to do this is to use the scripts used by the policy/api S3P tests.
 
@@ -276,7 +273,12 @@ familiar with the Policy Framework components and test any local changes.
 .. toctree::
    :maxdepth: 1
 
-..
+   policy-gui-controlloop-smoke.rst
+   db-migrator-smoke.rst
+   cl-participants-smoke.rst
+   clamp-smoke.rst
+   clamp-cl-participant-protocol-smoke.rst
+   policy-participant-smoke.rst
    api-smoke.rst
 
 ..
@@ -294,8 +296,6 @@ familiar with the Policy Framework components and test any local changes.
 ..
    distribution-smoke.rst
 
-..
-   clamp-smoke.rst
 
 Running the Stability/Performance Tests
 ***************************************
@@ -315,7 +315,7 @@ familiar with the Policy Framework components and test any local changes.
    clamp-s3p.rst
 
 Running the Pairwise Tests
-***********************
+**************************
 
 The following links contain instructions on how to run the pairwise tests. These may be helpful to developers check that
 the Policy Framework works in a full ONAP deployment.
@@ -323,6 +323,12 @@ the Policy Framework works in a full ONAP deployment.
 .. toctree::
    :maxdepth: 1
 
+   clamp-policy.rst
+
+   clamp-dcae.rst
+
+   policy-cds.rst
+
 ..
    api-pairwise.rst
 
@@ -341,9 +347,6 @@ the Policy Framework works in a full ONAP deployment.
 ..
    distribution-pairwise.rst
 
-..
-   clamp-pairwise.rst
-
 
 Generating Swagger Documentation
 ********************************