Fix indentation in examples

modules/namespace-configuration-in-a-clustergroup.adoc

@@ -24,27 +24,26 @@ The `namespace` parameter in a Kubernetes Helm chart specifies namespaces within
 [source,yaml]
 ----
 namespaces:
-    - open-cluster-management
-    - vault
-    - golang-external-secrets
-    - config-demo
-    - hello-world
+  - open-cluster-management
+  - vault
+  - golang-external-secrets
+  - config-demo
+  - hello-world
 ----
 *Namespaces with Labels and Annotations*:
 
 [source,yaml]
 ----
- namespaces:
-    open-cluster-management: {}
-    vault: {}
-    golang-external-secrets: {}
-    config-demo:
-      labels:
-        app: 'config-demo'
-        tier: 'test'
-      annotations:
-        'test/annotation': true
-    hello-world: {}
-
+namespaces:
+  open-cluster-management: {}
+  vault: {}
+  golang-external-secrets: {}
+  config-demo:
+    labels:
+      app: 'config-demo'
+      tier: 'test'
+    annotations:
+      'test/annotation': true
+  hello-world: {}
 ----
 In this example, we add “app” and “tier” labels to the config-demo app, and the annotation “test/annotation: true” to it. All other namespaces are created with defaults.

modules/subscriptions-configuration-in-a-clustergroup.adoc

@@ -4,7 +4,7 @@
 [id="subscriptions-configuration-in-a-clustergroup"]
 = Subscription configuration in a ClusterGroup
 
-Configuring subscriptions within a ClusterGroup streamlines access management and resource allocation for users and applications. It also facilitates the creation of a software bill of materials detailing the intended installations for the ClusterGroup.This capability empowers you to establish subscription plans, enforce governance policies, and ensure optimal resource utilization. Through the `subscriptions` parameter, you can define access levels, allocate resources, and promote efficient management and cost optimization within the ClusterGroup environment. 
+Configuring subscriptions within a ClusterGroup streamlines access management and resource allocation for users and applications. It also facilitates the creation of a software bill of materials detailing the intended installations for the ClusterGroup.This capability empowers you to establish subscription plans, enforce governance policies, and ensure optimal resource utilization. Through the `subscriptions` parameter, you can define access levels, allocate resources, and promote efficient management and cost optimization within the ClusterGroup environment.
 
 Subscriptions are the preferred way of including OpenShift operators in the validated patterns. Known as OLM Packages (OLM for Operator Lifecycle Manager), these subscriptions function similarly to RPM packages for RHEL, with operators responsible for software operation and upgrades.
 
@@ -49,55 +49,54 @@ subscriptions:
 [source,yaml]
 ----
 subscriptions:
-    acm:
-      name: advanced-cluster-management
-      namespace: open-cluster-management
-
-    amqbroker-prod:
-      name: amq-broker-rhel8
-      namespace: manuela-tst-all
-
-    amqstreams-prod-dev:
-      name: amq-streams
-      namespaces: 
-      - manuela-data-lake
-      - manuela-tst-all
-
-    camelk-prod-dev:
-      name: red-hat-camel-k
-      namespaces: 
-      - manuela-data-lake
-      - manuela-tst-all
-
-    seldon-prod-dev:
-      name: seldon-operator-certified
-      namespaces: 
-      - openshift-operators
-      source: certified-operators
-
-    pipelines:
-      name: openshift-pipelines-operator-rh
-      source: redhat-operators
-      
-    odh:
-      name: opendatahub-operator
-      source: community-operators
+  acm:
+    name: advanced-cluster-management
+    namespace: open-cluster-management
+
+  amqbroker-prod:
+    name: amq-broker-rhel8
+    namespace: manuela-tst-all
+
+  amqstreams-prod-dev:
+    name: amq-streams
+    namespaces:
+    - manuela-data-lake
+    - manuela-tst-all
+
+  camelk-prod-dev:
+    name: red-hat-camel-k
+    namespaces:
+    - manuela-data-lake
+    - manuela-tst-all
+
+  seldon-prod-dev:
+    name: seldon-operator-certified
+    namespaces:
+    - openshift-operators
+    source: certified-operators
+
+  pipelines:
+    name: openshift-pipelines-operator-rh
+    source: redhat-operators
+
+  odh:
+    name: opendatahub-operator
+    source: community-operators
 ----
 
 *Subscriptions for Ansible Edge GitOps (demonstrating disable and override)*:
 
 [source,yaml]
 ----
 subscriptions:
-    openshift-data-foundation:
-      disabled: true
-
-    portworx:
-      name: portworx-certified
-      namespace: portworx
-      channel: stable
-      source: certified-operators
-
+  openshift-data-foundation:
+    disabled: true
+
+  portworx:
+    name: portworx-certified
+    namespace: portworx
+    channel: stable
+    source: certified-operators
 ----
 
 In this example, the values file is intended to override the default settings in the main `values-hub.yaml`. Consequently, the `openshift-data-foundation` application is overridden and disabled, while the `portworx` application is added.