diff --git a/docs/en/enterprise-edition/content-collections/governance/custom-build-policies/code-editor.adoc b/docs/en/enterprise-edition/content-collections/governance/custom-build-policies/code-editor.adoc
index 5763e7533f..6654dc08f8 100644
--- a/docs/en/enterprise-edition/content-collections/governance/custom-build-policies/code-editor.adoc
+++ b/docs/en/enterprise-edition/content-collections/governance/custom-build-policies/code-editor.adoc
@@ -73,11 +73,10 @@ definition:
 === Key Capabilities of the Code Editor
 
 ==== Attribute-Based Policies
-+
 Attribute when defined in a policy describes attribute configurations for resources. Each resource must contain values the attribute configuration has specified or display the presence or absence of the attribute configuration. The syntax and attribute configurations used in YAML templates  is similar to Terraform.
-+
+
 In this example, the attribute defines a back-up configuration for Redshift clusters.
-+
+
 [source]
 definition:
      cond_type: "attribute"
@@ -213,11 +212,11 @@ cond_type: "secrets"
 ----
 
 ==== Connection-Based Policies
-+
+
 Connection State when defined in a policy specifies a connect or disconnect between resources of different types.
-+
+
 In this example, `aws_lb` and `aws_elb` must have connection with `aws_security_group` or `aws_default_secuirty_group` to be compliant.
-+
+
 [source]
 definition:
        cond_type: "connection"
@@ -273,11 +272,11 @@ The table below provides instructions on how to use Connection State Operators.
 |===
 
 === Logical (AND/OR) Operators 
-+
+
 A policy may include layers of defined Attributes and Connection State, or both. To define the connection between the two AND/OR logic is used. Using Code Editor you can customize the Attribute, Connection State or both at multiple layers.
-+
+
 In this example, you see the both AND/OR logic applied to Attribute.
-+
+
 [source]
 metadata:
  name: "Ensure all AWS databases have Backup Policy"