Update dmaap references in policy documentation files

Issue-ID: POLICY-4942
Change-Id: I08d9ab8e5028eab0a20999ce174d3a2fbad67967
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>

6 files changed, 6 insertions, 6 deletions

diff --git a/docs/clamp/acm/design-impl/participants/a1pms-participant.rst b/docs/clamp/acm/design-impl/participants/a1pms-participant.rst
index 23e70b9b..5afbf912 100644
--- a/docs/clamp/acm/design-impl/participants/a1pms-participant.rst
+++ b/docs/clamp/acm/design-impl/participants/a1pms-participant.rst
@@ -7,7 +7,7 @@ A1PMS Participant
 
 The A1PMS participant receives A1 policy service information from the CLAMP runtime and creates the A1 policy service in A1PMS. The participant acts as a wrapper around the A1PMS and creates the policy service.
 
-Supported message Broker are DMaap and Strimzi-Kafka.
+It supports the message Broker Kafka.
 
 .. image:: ../../images/participants/a1pms-participant.png
 
diff --git a/docs/clamp/acm/design-impl/participants/http-participant.rst b/docs/clamp/acm/design-impl/participants/http-participant.rst
index 3125e173..03605377 100644
--- a/docs/clamp/acm/design-impl/participants/http-participant.rst
+++ b/docs/clamp/acm/design-impl/participants/http-participant.rst
@@ -13,7 +13,7 @@ the microservice that runs a REST server. Once the microservice is up, the HTTP
 participant can be used to configure the microservice over its REST interface.Of course,
 the HTTP participant works towards any REST service, it is not restricted to REST
 services started by participants.
-Supported message Broker are DMaap and Strimzi-Kafka.
+It supports the message Broker Kafka.
 
 .. image:: ../../images/participants/http-participant.png
 
diff --git a/docs/clamp/acm/design-impl/participants/k8s-participant.rst b/docs/clamp/acm/design-impl/participants/k8s-participant.rst
index dae5df5d..82935bda 100644
--- a/docs/clamp/acm/design-impl/participants/k8s-participant.rst
+++ b/docs/clamp/acm/design-impl/participants/k8s-participant.rst
@@ -10,7 +10,7 @@ k8s cluster on the specified namespace. It can fetch the helm chart from remote
 that are configured on the helm client. The participant acts as a wrapper around the helm client and creates the required
 resources in the k8s cluster.
 
-Supported message Broker are DMaap and Strimzi-Kafka.
+It supports the message Broker Kafka.
 
 The kubernetes participant also exposes REST endpoints for onboarding, installing and uninstalling of helm charts from the
 local chart database which facilitates the user to also use this component as a standalone application for helm operations.
diff --git a/docs/clamp/acm/design-impl/participants/kserve-participant.rst b/docs/clamp/acm/design-impl/participants/kserve-participant.rst
index 618b7ebd..24314a3d 100644
--- a/docs/clamp/acm/design-impl/participants/kserve-participant.rst
+++ b/docs/clamp/acm/design-impl/participants/kserve-participant.rst
@@ -7,7 +7,7 @@ Kserve Participant
 
 The Kserve participant receives inference service information from CLAMP runtime and creates the inference services in the Kubernetes cluster. The participant acts as a wrapper around Kserve and creates the inference service.
 
-Supported message Broker are DMaap and Strimzi-Kafka.
+It supports the message Broker Kafka.
 
 .. image:: ../../images/participants/kserve-participant.png
 
diff --git a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst
index 891f5771..0fbaf897 100755..100644
--- a/docs/clamp/acm/design-impl/participants/participant-intermediary.rst
+++ b/docs/clamp/acm/design-impl/participants/participant-intermediary.rst
@@ -16,7 +16,7 @@ Terminology
 - Message to a participant: a message only for a participant (participantId properly filled)
 - MessageSender: a class that takes care of sending messages from participant-intermediary
 - GUI: graphical user interface, Postman or a Front-End Application
-- Message Broker: supported message Broker are DMaap and Strimzi-Kafka
+- Message Broker: It supports the message Broker Kafka
 
 Inbound messages to participants
 --------------------------------
diff --git a/docs/clamp/acm/design-impl/participants/participants.rst b/docs/clamp/acm/design-impl/participants/participants.rst
index 4dab3434..6b12b7c4 100644
--- a/docs/clamp/acm/design-impl/participants/participants.rst
+++ b/docs/clamp/acm/design-impl/participants/participants.rst
@@ -7,7 +7,7 @@ Automation Composition Participants
 
 A Participant is a component that acts as a bridge between the CLAMP Automation Composition Management runtime and components such as
 the Policy Framework, DCAE, or a Kubernetes cluster that are taking part in automation composition management. It listens
-to DMaaP to receive messages from the CLAMP runtime and performs operations towards components that
+to Kafka to receive messages from the CLAMP runtime and performs operations towards components that
 are taking part in acms. A participant has an Automation Composition Management Element for each automation composition in
 which it is taking part.