Merge "Updating the Kafka listener compliance to could events and legacy"

[cps.git] / docs / architecture.rst

diff --git a/docs/architecture.rst b/docs/architecture.rst
index 26a8c63..8dde47a 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -21,7 +21,7 @@ In this release CPS is no longer a stand alone component and is released along w
 Project page describing eventual scope and ambition is here:
 `Configuration Persistence Service Project <https://wiki.onap.org/display/DW/Configuration+Persistence+Service+Project>`_
 
-This page reflects the state for Istanbul-R9 release.
+This page reflects the state for the latest release.
 
 .. image:: _static/star.png
     :class: float-left
@@ -61,9 +61,9 @@ Configuration Persistence Service provides the following interfaces.
    * - CPS-E-04
      - Change Notification
      - - Kafka is used as the event messaging system
-       - running instance is supplied independently from ONAP DMaaP component or any Kafka instance deployed from ONAP
+       - running instance is supplied independently from any Kafka instance deployed from ONAP
        - published events contain Timestamp, Dataspace, Schema set, Anchor and JSON Data Payload
-     - DMaaP
+     - Kafka
    * - CPS-E-05
      - xNF Data Access
      - - read xNF data