From f5180f911d7f948b226a21c810575ea8a4c3cf6b Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Fri, 2 Oct 2026 16:50:53 +0100 Subject: [PATCH] DOC-7128: convert the last odd-case image shortcodes outside RedisVL Fixes the source quirks that stopped the codemod on 10 image shortcodes, then converts them: - manage-api-keys.md: three screenshots ended with a
spacer, so they weren't alone in their paragraph. The
is removed. In a browser this shrinks the gap below each from 56-76px to the 32px gap standalone screenshots get elsewhere. - kubernetes 7.4.6 architecture: two diagrams shared one line (they already rendered stacked), so they're now on separate lines. - oss_and_stack timeseries: two images in table cells, converted by hand to inline Markdown. An image alone in a table cell reaches the hook as a block image, so it renders the same unclassed . - connect/_index.md: the width=50%" typo is fixed. It had rendered as width="50%"", which browsers tolerated as 50%. - migrate-databases.md, upgrade-essentials-pro.md: backticks are dropped from an alt text, because Markdown would have parsed them as a code span. Built main and this branch under the production baseURL and compared every image: the only changes are those alt and width values, plus 3 alts losing literal ** markers. In a browser every image renders at its old size. Ticket: DOC-7128 Co-Authored-By: Claude Opus 5.5 --- content/operate/kubernetes/7.4.6/architecture/_index.md | 4 +++- .../stack-with-enterprise/timeseries/_index.md | 2 +- content/operate/rc/api/get-started/manage-api-keys.md | 8 +++++--- content/operate/rc/databases/connect/_index.md | 3 ++- content/operate/rc/databases/migrate-databases.md | 3 ++- .../operate/rc/subscriptions/upgrade-essentials-pro.md | 3 ++- 6 files changed, 15 insertions(+), 8 deletions(-) diff --git a/content/operate/kubernetes/7.4.6/architecture/_index.md b/content/operate/kubernetes/7.4.6/architecture/_index.md index 0bf7f6bc18..49c90e5362 100644 --- a/content/operate/kubernetes/7.4.6/architecture/_index.md +++ b/content/operate/kubernetes/7.4.6/architecture/_index.md @@ -41,7 +41,9 @@ On the right-hand side of the figure (marked #2), Redis Enterprise uses network- Redis Enterprise is not only great as an in-memory database but also extremely efficient in the way it uses persistent storage, even when the user chooses to configure Redis Enterprise to write every change to the disk. Compared to a disk-based database that requires multiple interactions (in most cases) with a storage device for every read or write operation, Redis Enterprise uses a single IOPS, in most cases, for a write operation and zero IOPS for a read operation. As a result, significant performance improvements are seen in typical Kubernetes environments, as illustrated in the figures below: -{{< image filename="/images/k8s/kubernetes-overview-performance-improvements-read.png" >}}{{< image filename="/images/k8s/kubernetes-overview-performance-improvements-write.png" >}} +![](/images/k8s/kubernetes-overview-performance-improvements-read.png) + +![](/images/k8s/kubernetes-overview-performance-improvements-write.png) ## Multiple services on each pod diff --git a/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md b/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md index 89d19e87f7..cd9a2ee11a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/timeseries/_index.md @@ -36,7 +36,7 @@ Redis Open Source provides a new data type that uses chunks of memory of fixed s | Before Downsampling | After Downsampling | | --- | --- | -| {{< image filename="/images/rs/TimeSeries-downsampling1.png" >}} | {{< image filename="/images/rs/TimeSeries-downsampling2.png" >}} | +| ![](/images/rs/TimeSeries-downsampling1.png) | ![](/images/rs/TimeSeries-downsampling2.png) | If you want to keep all of your raw data points indefinitely, your data set grows linearly over time. However, if your use case allows you to have less fine-grained data further back in time, downsampling can be applied. This allows you to keep fewer historical data points by aggregating raw data for a given time window using a given aggregation function. Time series support [downsampling](/content/develop/data-types/timeseries/_index.md#aggregation) with the following aggregations: avg, sum, min, max, range, count, first, and last. diff --git a/content/operate/rc/api/get-started/manage-api-keys.md b/content/operate/rc/api/get-started/manage-api-keys.md index e522da6a39..4d6b2467d9 100644 --- a/content/operate/rc/api/get-started/manage-api-keys.md +++ b/content/operate/rc/api/get-started/manage-api-keys.md @@ -72,7 +72,8 @@ Select **Create** to create the new key. When you do this, the **API user key** dialog appears. -{{The **API user key** dialog lets you copy the value of the new key to the Clipboard.}}
+![The **API user key** dialog lets you copy the value of the new key to the Clipboard.](/images/rc/access-management-create-user-key.png) +{width="75%"} > [!WARNING] > This is the only time the value of the user key is available. Save it to a secure location before closing the dialog box.

@@ -86,7 +87,7 @@ To delete a user key: 1. Use the **API Keys** tab of the **Access Management** screen to locate the target key. Hover over the key to display the **Delete** button. - {{The **Delete** button appears to the right of the selected user key.}}
+ ![The **Delete** button appears to the right of the selected user key.](/images/rc/access-management-api-user-key-delete.png) 2. Select the **Delete** button. @@ -95,7 +96,8 @@ To delete a user key: 3. This displays the **Delete API secret key** dialog box. - {{The **Delete** button appears to the right of the selected user key.}}
+ ![The **Delete** button appears to the right of the selected user key.](/images/rc/access-management-delete-api-secret-key.png) + {width="50%"} Select the **Delete** button to confirm. diff --git a/content/operate/rc/databases/connect/_index.md b/content/operate/rc/databases/connect/_index.md index f6d78f244f..b9aa58aa21 100644 --- a/content/operate/rc/databases/connect/_index.md +++ b/content/operate/rc/databases/connect/_index.md @@ -25,7 +25,8 @@ The database endpoints are listed in the **Configuration** tab for your database ![The General section of the Configuration tab of the Pro database details page.](/images/rc/databases-configuration-general-endpoints.png) -{{The Access section for an Essentials database.}} +![The Access section for an Essentials database.](/images/rc/database-details-configuration-tab-access-essentials.png) +{width="50%"} Redis Cloud Pro and Redis Cloud Essentials databases have a public endpoint, which you can access from the public internet. Redis Cloud Pro databases also have a private endpoint. You can connect to the private endpoint from a private network. Before you can connect to the private endpoint, you must set up a private connectivity method, such as: - [VPC peering](/content/operate/rc/security/vpc-peering.md) diff --git a/content/operate/rc/databases/migrate-databases.md b/content/operate/rc/databases/migrate-databases.md index 67e56549d8..062800167f 100644 --- a/content/operate/rc/databases/migrate-databases.md +++ b/content/operate/rc/databases/migrate-databases.md @@ -141,7 +141,8 @@ Follow these detailed steps to migrate data using Active-Passive syncing: When data has fully migrated to the target database, database status reports `Synced`. - {{When the data is migrated, the target database status displays `Synced`.}} + ![When the data is migrated, the target database status displays Synced.](/images/rc/migrate-data-status-synced.png) + {width="100px"} Active-Passive sync lets you migrate data while apps and other connections are using the source database. Once the data is migrated, you should migrate active connections to the target database. diff --git a/content/operate/rc/subscriptions/upgrade-essentials-pro.md b/content/operate/rc/subscriptions/upgrade-essentials-pro.md index 5c6f6963cb..2fc4d22d79 100644 --- a/content/operate/rc/subscriptions/upgrade-essentials-pro.md +++ b/content/operate/rc/subscriptions/upgrade-essentials-pro.md @@ -88,7 +88,8 @@ You can migrate your Redis Cloud Essentials database to your new Redis Cloud Pro When data has fully migrated to the target database, database status reports `Synced`. - {{When the data is migrated, the target database status displays `Synced`.}} + ![When the data is migrated, the target database status displays Synced.](/images/rc/migrate-data-status-synced.png) + {width="100px"} Active-Passive sync lets you migrate data while apps and other connections are using the source database. Once the data is migrated, you should migrate active connections to the target database and turn off Active-Passive before you move on.