Fix issue where the procedure for updating the operator default confi…

…g would show up under the Verification section

modules/installation/proc-rhdh-deploy-aks-operator.adoc

@@ -21,7 +21,7 @@ You can install the {product-short} Operator on {aks-short} using the https://ol
 // Procedure fragment on installing the operator using OLM on a non OCP cluster
 include::./snip-install-rhdh-operator-olm.adoc[]
 
-. Modify the default configuration of `db-statefulset.yaml` and `deployment.yaml` by adding the following fragment:
+.. Modify the default configuration of `db-statefulset.yaml` and `deployment.yaml` by adding the following fragment:
 +
 --
 [source,yaml]

modules/installation/snip-install-rhdh-operator-olm.adoc

@@ -115,10 +115,10 @@ EOF
 ----
 --
 
-.Verification
+[TIP]
+====
+Verify that the created Operator is properly running by entering the following command:
 
-. Verify that the created Operator is properly running by entering the following command:
-+
 --
 [source,terminal]
 ----
@@ -127,8 +127,6 @@ kubectl -n rhdh-operator get pods -w
 
 If the operator pod shows `ImagePullBackOff` status, then you might need permissions to pull the image directly within the Operator deployment's manifest.
 
-[TIP]
-====
 You can include the required secret name in the `deployment.spec.template.spec.imagePullSecrets` list and verify the deployment name using `kubectl get deployment -n rhdh-operator` command:
 
 [source,terminal]
@@ -140,7 +138,7 @@ kubectl -n rhdh-operator patch deployment \
 ====
 --
 
-. Update the default configuration of the operator to ensure that {product-short} resources can start correctly using the following steps:
+. When the Operator is running, update its default configuration to ensure that {product-short} resources can start correctly using the following steps:
 .. Edit the `backstage-default-config` ConfigMap in the `rhdh-operator` namespace using the following command:
 +
 --