Put a note on the CLAMP/PF merge on Honoluluhonolulu

Issue-ID: POLICY-4137
Change-Id: Ic690b2c7e85da7bd4551cbed2fab3da925c4193b
Signed-off-by: liamfallon <liam.fallon@est.tech>

2 files changed, 5 insertions, 20 deletions

diff --git a/.readthedocs.yaml b/.readthedocs.yaml
deleted file mode 100644
index 3797dc8bb..000000000
--- a/.readthedocs.yaml
+++ /dev/null
@@ -1,20 +0,0 @@
----
-# .readthedocs.yml
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-# Required
-version: 2
-
-formats:
-  - htmlzip
-
-build:
-  image: latest
-
-python:
-  version: 3.7
-  install:
-    - requirements: docs/requirements-docs.txt
-
-sphinx:
-  configuration: docs/conf.py
diff --git a/README.md b/README.md
index ba194ec33..f3b10f378 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,10 @@
 # Summary
 
+---
+**NOTE**
+The merge of the CLAMP project with the Policy Framework project started in the Honolulu release.
+---
+
 CLAMP is a platform for designing and managing control loops. It is used to design a closed loop, configure it with specific parameters for a particular network service, then deploying and undeploying it.  Once deployed, the user can also update the loop with new parameters during runtime, as well as suspending and restarting it.
 
 It interacts with other systems to deploy and execute the closed loop. For example, it pushes the control loop design to the SDC catalog, associating it with the VF resource.  It requests from DCAE the instantiation of microservices to manage the closed loop flow.  Further, it creates and updates multiple policies in the Policy Engine that define the closed loop flow.