diff --git a/assets/css/index.css b/assets/css/index.css
index 2873de8615..d6c4e20f21 100644
--- a/assets/css/index.css
+++ b/assets/css/index.css
@@ -306,6 +306,11 @@ section.prose {
   @apply m-0;
 }
 
+/* Back-to-back callouts otherwise touch, which led authors to add spacer lines that break the Markdown. */
+.alert + .alert {
+  @apply mt-4;
+}
+
 select {
   background-repeat: no-repeat;
   background-size: 1.5em 1.5em;
diff --git a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md
index 221d745d3a..3e7c7bcf0a 100644
--- a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md
+++ b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md
@@ -36,8 +36,9 @@ You'll need to configure the following fields to connect Prometheus to Redis Ent
 | `spec.selector` | `matchLabels` | REC service label (`app: redis.io/service=prom-metrics`) |
 
 Apply the file in the same namespace as your Redis Enterprise cluster (REC).
-    > [!NOTE]
-    > If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters.md) for more details on cross-namespace `ServiceMonitor` configuration.
+
+> [!NOTE]
+> If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api-reference/api.md) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters.md) for more details on cross-namespace `ServiceMonitor` configuration.
 
 
 ```YAML
diff --git a/content/operate/oss_and_stack/install/install-stack/homebrew.md b/content/operate/oss_and_stack/install/install-stack/homebrew.md
index e06586fbff..2bebf4f3dc 100644
--- a/content/operate/oss_and_stack/install/install-stack/homebrew.md
+++ b/content/operate/oss_and_stack/install/install-stack/homebrew.md
@@ -16,7 +16,7 @@ weight: 6
 
 > [!NOTE]
 > Installation using Homebrew is only supported on macOS.
- 
+
 > [!NOTE]
 > If you only need the Redis CLI (`redis-cli`) and not the full Redis Open Source distribution, see [Install redis-cli](/content/operate/oss_and_stack/install/install-stack/install-redis-cli.md).
 
diff --git a/content/operate/oss_and_stack/install/upgrade/cluster.md b/content/operate/oss_and_stack/install/upgrade/cluster.md
index d7aefd2857..fc61bf3b9b 100644
--- a/content/operate/oss_and_stack/install/upgrade/cluster.md
+++ b/content/operate/oss_and_stack/install/upgrade/cluster.md
@@ -14,7 +14,7 @@ weight: 30
 > The supported upgrade paths are:
 > - Redis Open Source 7.x (with or without modules) to Redis 8 in Redis Open Source
 > - Redis Stack 7.2 or 7.4 to Redis 8 in Redis Open Source
-</br>
+
 > [!NOTE]
 > It's essential to practice upgrading Redis in a controlled environment before upgrading it in a production environment.
 > Docker is an excellent tool to use for this purpose.
diff --git a/content/operate/rc/databases/import-data.md b/content/operate/rc/databases/import-data.md
index 7ebe0a8179..90493ac5e0 100644
--- a/content/operate/rc/databases/import-data.md
+++ b/content/operate/rc/databases/import-data.md
@@ -15,7 +15,7 @@ You can import an existing dataset into your Redis Cloud instance from an existi
 > Data imported into an existing database overwrites existing data. 
 > - If you import a dataset into the target database of an [Active-Passive setup](/content/operate/rc/databases/migrate-databases.md#sync-using-active-passive), the dataset will be overwritten by any changes to the source database.
 > - If you import a dataset into one region in an [Active-Active database](/content/operate/rc/databases/active-active/_index.md), the dataset will also be replicated across regions.
-<br/>
+
 > [!NOTE]
 > Expired keys are not imported.
 > As a result, the number of keys in the source and destination databases can be different after the import is complete.