Update participant documentation

Issue-ID: POLICY-4061
Change-Id: If22d8c14d82c34a407fb3394118aa327feabf7a3
Signed-off-by: Wayne Dunican <wayne.dunican@est.tech>

1 files changed, 11 insertions, 11 deletions

diff --git a/docs/clamp/acm/design-impl/participants/policy-framework-participant.rst b/docs/clamp/acm/design-impl/participants/policy-framework-participant.rst
index 56b2844f..1ef38b3e 100644
--- a/docs/clamp/acm/design-impl/participants/policy-framework-participant.rst
+++ b/docs/clamp/acm/design-impl/participants/policy-framework-participant.rst
@@ -1,6 +1,6 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 
-.. _clamp-controlloop-policy-framework-participant:
+.. _clamp-acm-policy-framework-participant:
 
 The CLAMP Policy Framework Participant
 ######################################
@@ -8,11 +8,11 @@ The CLAMP Policy Framework Participant
 .. contents::
     :depth: 3
 
-Control Loop Elements in the Policy Framework Participant are configured using TOSCA metadata defined for the Policy Control Loop Element type.
+Automation Composition Elements in the Policy Framework Participant are configured using TOSCA metadata defined for the Policy Automation Composition Element type.
 
 The Policy Framework participant receives messages through participant-intermediary common code, and handles them by invoking REST APIs towards policy-framework.
 
-For example, When a ControlLoopUpdate message is received by policy participant, it contains full ToscaServiceTemplate describing all components participating in a control loop. When the control loop element state changed from UNINITIALIZED to PASSIVE, the Policy-participant triggers the creation of policy-types and policies in Policy-Framework.
+For example, When a AutomationCompositionUpdate message is received by policy participant, it contains full ToscaServiceTemplate describing all components participating in an automation composition. When the automation composition element state changed from UNINITIALIZED to PASSIVE, the Policy-participant triggers the creation of policy-types and policies in Policy-Framework.
 
 When the state changes from PASSIVE to UNINITIALIZED, Policy-Participant deletes the policies, policy-types by invoking REST APIs towards the policy-framework.
 
@@ -31,9 +31,9 @@ Distributing Policies
 
 The Policy Framework participant uses the Policy PAP API to deploy and undeploy policies.
 
-When a Policy Framework Control Loop Element changes from state PASSIVE to state RUNNING, the policy is deployed. When it changes from state RUNNING to state PASSIVE, the policy is undeployed.
+When a Policy Framework Automation Composition Element changes from state UNINITIALISED to state PASSIVE, the policy is deployed. When it changes from state PASSIVE to state UNINITIALISED, the policy is undeployed.
 
-The PDP group to which the policy should be deployed is specified in the Control Loop Element metadata, see the Policy Control Loop Element type definition. If the PDP group specified for policy deployment does not exist, an error is reported.
+The PDP group to which the policy should be deployed is specified in the Automation Composition Element metadata, see the Policy Automation Composition Element type definition. If the PDP group specified for policy deployment does not exist, an error is reported.
 
 The PAP Policy Status API and Policy Deployment Status API are used to retrieve data to report on the deployment status of policies in Participant Status messages.
 
@@ -42,19 +42,19 @@ The PDP Statistics API is used to get statistics for statistics report from the
 Policy Type and Policy References
 +++++++++++++++++++++++++++++++++
 
-The Policy Framework uses the policyType and policyId properties defined in the Policy Control Loop Element type references to specify what policy type and policy should be used by a Policy Control Loop Element.
+The Policy Framework uses the policyType and policyId properties defined in the Policy Automation Composition Element type references to specify what policy type and policy should be used by a Policy Automation Composition Element.
 
-The Policy Type and Policy specified in the policyType and policyId reference must of course be available in the Policy Framework in order for them to be used in Control Loop instances. In some cases, the Policy Type and/or the Policy may be already loaded in the Policy Framework. In other cases, the Policy Framework participant must load the Policy Type and/or policy.
+The Policy Type and Policy specified in the policyType and policyId reference must of course be available in the Policy Framework in order for them to be used in Automation Composition instances. In some cases, the Policy Type and/or the Policy may be already loaded in the Policy Framework. In other cases, the Policy Framework participant must load the Policy Type and/or policy.
 
 Policy Type References
 **********************
 
 The Policy Participant uses the following steps for Policy Type References:
 
-#. The Policy Participant reads the Policy Type ID from the policyType property specified for the Control Loop Element.
+#. The Policy Participant reads the Policy Type ID from the policyType property specified for the Automation Composition Element.
 
 #. It checks if a Policy Type with that Policy Type ID has been specified in the ToscaServiceTemplateFragment field in
-   the ControLoopElement definition in the ControlLoopUpdate message, see :ref:`controlloop-participant-protocol-label`.
+   the AutomationCompositionElement definition in the AutomationCompositionUpdate message, see :ref:`clampacm-participant-protocol-label`.
 
   #. If the Policy Type has been specified, the Participant stores the Policy Type in the Policy framework. If the
      Policy Type is successfully stored, execution proceeds, otherwise an error is reported.
@@ -67,10 +67,10 @@ Policy References
 
 The Policy Participant uses the following steps for Policy References:
 
-#. The Policy Participant reads the Policy ID from the policyId property specified for the Control Loop Element.
+#. The Policy Participant reads the Policy ID from the policyId property specified for the Automation Composition Element.
 
 #. It checks if a Policy with that Policy ID has been specified in the ToscaServiceTemplateFragment field in the
-   ControLoopElement definition in the ControlLoopUpdate message, :ref:`controlloop-participant-protocol-label`.
+   AutomationCompositionElement definition in the AutomationCompositionUpdate message, :ref:`clampacm-participant-protocol-label`.
 
   #. If the Policy has been specified, the Participant stores the Policy in the Policy framework. If the Policy is
      successfully stored, execution proceeds, otherwise an error is reported.