Fix yaml code block in documentation

[policy/parent.git] / docs / clamp / acm / design-impl / clamp-runtime-acm.rst

diff --git a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
index 96dbc21..5b88edb 100755 (executable)
--- a/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
+++ b/docs/clamp/acm/design-impl/clamp-runtime-acm.rst
@@ -211,7 +211,7 @@ Example of DEPLOY order with Http_PMSHMicroserviceAutomationCompositionElement w
 In that scenario the message AUTOMATION_COMPOSITION_DEPLOY has been sent two times.
 
 Configure custom namings for TOSCA node types
-+++++++++++++++++++++++++++++++++++++++++++++
+*********************************************
 
 The node type of the AC element and the Automation composition can be customised as per the user requirement.
 These customised names can be used in the TOSCA node type definitions of AC element and composition. All the
@@ -220,10 +220,10 @@ The following parameters are provided in the config file of runtime-acm for cust
 
 .. code-block:: YAML
 
-runtime:
-  acmParameters:
-    toscaElementName: customElementType
-    toscaCompositionName: customCompositionType
+ runtime:
+   acmParameters:
+     toscaElementName: customElementType
+     toscaCompositionName: customCompositionType
 
 If there are no values provided for customisation, the default node types "org.onap.policy.clamp.acm.AutomationCompositionElement"
 and "org.onap.policy.clamp.acm.AutomationComposition" are used for the AC element and composition by the runtime-acm.
@@ -232,10 +232,9 @@ onap helm chart, the following properties can be updated in the values.yaml.
 
 .. code-block:: YAML
 
-customNaming:
-  toscaElementName: customElementName
-  toscaCompositionName: customCompositionName
-
+  customNaming:
+    toscaElementName: customElementName
+    toscaCompositionName: customCompositionName
 
 
 Design of managing messages