STAC-24067: move note on using stackpacks instead of cli to more prominent place

Author: fvlankvelt

docs/latest/modules/en/pages/setup/custom-integrations/metric-bindings/cli.adoc

@@ -67,6 +67,10 @@ timestamp: 2026-01-14T13:11:07.575662922Z[Etc/UTC]
 
 == Modifying Metric Bindings
 
+[NOTE]
+====
+The recommended way of working is to store metric bindings (and any other custom resources created in {stackstate-product-name}) as YAML files in xref:/setup/custom-integrations/overview.adoc[a StackPack]. From there changes can be manually applied or it can be fully automated by using the SUSE Observability CLI in a CI/CD system like GitHub actions or GitLab pipelines.
+====
 
 === Create/update a Metric Binding
 Create a file `metric-bindings.yaml` that looks like this:
@@ -113,8 +117,3 @@ sts settings delete --ids <id>
 
 The `<id>` in this command isn't the identifier but the number in the `Id` column of the `sts settings list` output.
 
-[NOTE]
-====
-The recommended way of working is to store metric bindings (and any other custom resources created in {stackstate-product-name}) as YAML files in xref:/setup/custom-integrations/overview.adoc[a StackPack]. From there changes can be manually applied or it can be fully automated by using the SUSE Observability CLI in a CI/CD system like GitHub actions or GitLab pipelines.
-====
-

docs/latest/modules/en/pages/setup/custom-integrations/monitors/cli.adoc

@@ -144,6 +144,11 @@ Monitor health states with identifier matching exactly 1 topology element: 650
 
 == Modifying Monitors
 
+[NOTE]
+====
+The recommended way of working is to store monitors (and any other custom resources created in {stackstate-product-name}) as YAML files in xref:/setup/custom-integrations/overview.adoc[a StackPack]. From there changes can be manually applied or it can be fully automated by using the SUSE Observability CLI in a CI/CD system like GitHub actions or GitLab pipelines.
+====
+
 === Create a Monitor
 
 You can create a monitor by applying a YAML file, say `monitor.yaml`.  It must have the following outline:
@@ -174,11 +179,6 @@ You can xref:/setup/custom-integrations/monitors/index.adoc#_verifying_the_resul
 The identifier is used as the unique key of a monitor. Changing the identifier will create a new monitor instead of updating the existing one.
 ====
 
-[NOTE]
-====
-The recommended way of working is to store monitors (and any other custom resources created in {stackstate-product-name}) as YAML files in xref:/setup/custom-integrations/overview.adoc[a StackPack]. From there changes can be manually applied or it can be fully automated by using the SUSE Observability CLI in a CI/CD system like GitHub actions or GitLab pipelines.
-====
-
 === Delete a Monitor
 
 To delete a monitor use