From 8ec13b139dd270a1f2815e6e209b100586ead7ae Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Fri, 2 Oct 2026 17:00:04 +0100 Subject: [PATCH 1/2] DOC-7128: fix four callouts that merged into the one above them Four pages rendered a callout as literal "[!NOTE]" text inside the callout above it. Three had a spacer line (
,
, or  ) directly after the first callout's last line. A line that doesn't start with ">" right after a blockquote is a lazy continuation, so the spacer joined the first callout, and the second callout's lines continued the same blockquote. The fourth, in the Kubernetes Prometheus operator page, was a callout indented 4 spaces under a plain paragraph, so it read as more of that paragraph. Each spacer becomes a blank line, and the indented callout is dedented after a blank line. Found while reviewing #4197 (import-data.md). A site-wide scan of the rendered build for literal callout markers found these four and no others. After the fix, each page renders every callout in its source (main was one short on each), and no literal markers remain. Back-to-back callouts touch (0px gap) on this site, including on pages that were never broken. That's existing styling, and probably why authors added the spacers. Learned: a spacer line (
,  ) directly after a blockquote is a lazy continuation, so the next callout merges into it; separate callouts with a blank line Directive: scan rendered HTML for literal [!NOTE]/[!WARNING] text to find broken callouts Ticket: DOC-7128 Co-Authored-By: Claude Opus 5.5 --- .../kubernetes/re-clusters/connect-prometheus-operator.md | 5 +++-- .../operate/oss_and_stack/install/install-stack/homebrew.md | 2 +- content/operate/oss_and_stack/install/upgrade/cluster.md | 2 +- content/operate/rc/databases/import-data.md | 2 +- 4 files changed, 6 insertions(+), 5 deletions(-) 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 -
+ > [!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. -
+ > [!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. From 915a3e524a392bab4aefd417cc6d5cb8b2377271 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 5 Oct 2026 10:00:24 +0100 Subject: [PATCH 2/2] DOC-7128: add a gap between back-to-back callouts Two callouts in a row touched (0px gap) everywhere on the site, including on pages that were never broken. That's probably why authors added the spacer lines this PR removes, which broke the Markdown. A .alert + .alert rule adds a 1rem gap. .alert is only emitted by the three callout templates (render-blockquote.html, alert.html, alert-video.html), so it affects nothing else. Measured in a browser: adjacent callouts now sit 16px apart, and callouts separated by other content keep their spacing. Directive: separate back-to-back callouts with a blank line only; the CSS supplies the gap, so never add a spacer line Ticket: DOC-7128 Co-Authored-By: Claude Opus 5.5 --- assets/css/index.css | 5 +++++ 1 file changed, 5 insertions(+) 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;