From 12a315f76a189a4d3a00d6f0335dccf979b9608a Mon Sep 17 00:00:00 2001 From: "adheli.tavares" Date: Tue, 5 Apr 2022 14:21:40 +0100 Subject: Updating Clamp documentation - update rest apis definitions with renaming of control loop to acm - rename control loop to automation composition - fix a few cross-references missed Issue-ID: POLICY-4063 Change-Id: Ib88074e1d2d08fe38da244b5e1eb2e5783c84a86 Signed-off-by: adheli.tavares --- docs/clamp/acm/design-impl/participants/http-participant.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/clamp/acm/design-impl/participants/http-participant.rst') diff --git a/docs/clamp/acm/design-impl/participants/http-participant.rst b/docs/clamp/acm/design-impl/participants/http-participant.rst index be0349ea..f58f03d2 100644 --- a/docs/clamp/acm/design-impl/participants/http-participant.rst +++ b/docs/clamp/acm/design-impl/participants/http-participant.rst @@ -35,7 +35,7 @@ participant is running two HTTP Automation Composition Elements, one for Automat Automation Composition B. Configuring a Automation Composition Element on the HTTP participant for a Automation Composition ------------------------------------------------------------------------------ +------------------------------------------------------------------------------------------------- A *Configuration Entity* describes a concept that is managed by the HTTP participant. A Configuration Entity can be created, Read, Updated, and Deleted (CRUD). The user defines the Configuration Entities that it wants its HTTP Automation Composition Element to manage and -- cgit 1.2.3-korg