diff --git a/content/operate/rs/7.22/clusters/add-node.md b/content/operate/rs/7.22/clusters/add-node.md
index cdd6139519..3fef36602d 100644
--- a/content/operate/rs/7.22/clusters/add-node.md
+++ b/content/operate/rs/7.22/clusters/add-node.md
@@ -83,7 +83,7 @@ We recommend that you verify the node is functioning properly using one of the f
 
 - Cluster Manager UI method:
 
-    1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to verify.
+    1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the node you want to verify.
     
     1. Select **Verify node** from the list.
 
diff --git a/content/operate/rs/7.22/clusters/remove-node.md b/content/operate/rs/7.22/clusters/remove-node.md
index 4186c4ff7f..43c134ebb4 100644
--- a/content/operate/rs/7.22/clusters/remove-node.md
+++ b/content/operate/rs/7.22/clusters/remove-node.md
@@ -72,7 +72,7 @@ You can migrate resources by using the `rladmin` command-line interface
 
 To remove a node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to remove.
+1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the node you want to remove.
 
     ![Click the more actions button for a node to access node actions.](/images/rs/screenshots/nodes/secondary-nodes-more-actions.png)
 
diff --git a/content/operate/rs/7.22/clusters/replace-node.md b/content/operate/rs/7.22/clusters/replace-node.md
index 44429c8432..623e53597a 100644
--- a/content/operate/rs/7.22/clusters/replace-node.md
+++ b/content/operate/rs/7.22/clusters/replace-node.md
@@ -10,7 +10,7 @@ linkTitle: Replace node
 weight: 90
 url: '/operate/rs/7.22/clusters/replace-node/'
 ---
-A failed node will appear as `Down` ({{< image filename="/images/rs/icons/node-down-icon.png#no-click" alt="Node down icon" class="inline" >}}) in the **Nodes** list.
+A failed node will appear as `Down` (![Node down icon](/images/rs/icons/node-down-icon.png#no-click)) in the **Nodes** list.
 
 To replace a failed node: 
 
diff --git a/content/operate/rs/7.22/databases/active-active/manage.md b/content/operate/rs/7.22/databases/active-active/manage.md
index 9c6c8bf011..3a988b4278 100644
--- a/content/operate/rs/7.22/databases/active-active/manage.md
+++ b/content/operate/rs/7.22/databases/active-active/manage.md
@@ -74,7 +74,7 @@ To remove a participating cluster using the Cluster Manager UI:
 
     ![Edit and delete buttons appear when you point to an entry in the Other participating clusters list.](/images/rs/screenshots/databases/active-active-databases/participating-clusters-edit-delete.png)
 
-1. Click {{< image filename="/images/rs/buttons/delete-button.png#no-click" alt="The Delete button" width="25px" class="inline" >}} to remove the cluster.
+1. Click ![The Delete button](/images/rs/buttons/delete-button.png#no-click) to remove the cluster.
 
 1. Click **Save**.
 
diff --git a/content/operate/rs/7.22/databases/configure/db-defaults.md b/content/operate/rs/7.22/databases/configure/db-defaults.md
index adf2cd4658..4ce3807329 100644
--- a/content/operate/rs/7.22/databases/configure/db-defaults.md
+++ b/content/operate/rs/7.22/databases/configure/db-defaults.md
@@ -19,7 +19,7 @@ Database defaults are cluster-wide policies that determine default settings when
 
 To edit default database configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Database defaults**.
 
diff --git a/content/operate/rs/7.22/databases/configure/db-tags.md b/content/operate/rs/7.22/databases/configure/db-tags.md
index bc1873b0ad..06f11cda77 100644
--- a/content/operate/rs/7.22/databases/configure/db-tags.md
+++ b/content/operate/rs/7.22/databases/configure/db-tags.md
@@ -44,7 +44,7 @@ To edit a database's existing tags using the Cluster Manager UI:
 
 1. Go to the database's **Configuration** screen, then click **Edit**.
 
-1. Next to the existing **Tags**, click {{< image filename="/images/rs/buttons/edit-db-tags-button.png#no-click" alt="Edit tags button" width="22px" class="inline" >}}.
+1. Next to the existing **Tags**, click ![Edit tags button](/images/rs/buttons/edit-db-tags-button.png#no-click).
 
     ![The Edit tags button on the database configuration screen.](/images/rs/screenshots/databases/edit-db-tags-button-location.png)
 
diff --git a/content/operate/rs/7.22/databases/configure/db-upgrade.md b/content/operate/rs/7.22/databases/configure/db-upgrade.md
index 138a0a82da..6d2f1d4d93 100644
--- a/content/operate/rs/7.22/databases/configure/db-upgrade.md
+++ b/content/operate/rs/7.22/databases/configure/db-upgrade.md
@@ -18,7 +18,7 @@ Database upgrade configuration includes cluster-wide policies that affect defaul
 
 To edit database upgrade configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.22/databases/delete.md b/content/operate/rs/7.22/databases/delete.md
index ad5cc4e1d5..8454a4ecfe 100644
--- a/content/operate/rs/7.22/databases/delete.md
+++ b/content/operate/rs/7.22/databases/delete.md
@@ -17,6 +17,6 @@ To delete a database from the Cluster Manager UI:
 
 1. From the **Databases** list, select the database, then select **Configuration**.
 
-1. Select {{< image filename="/images/rs/icons/delete-icon.png#no-click" alt="Delete button" width="22px" class="inline" >}} **Delete**.
+1. Select ![Delete button](/images/rs/icons/delete-icon.png#no-click) **Delete**.
 
 1. In the **Delete database** dialog, confirm deletion.
diff --git a/content/operate/rs/7.22/databases/import-export/export-data.md b/content/operate/rs/7.22/databases/import-export/export-data.md
index d7f8eb2a9b..5046c6c98c 100644
--- a/content/operate/rs/7.22/databases/import-export/export-data.md
+++ b/content/operate/rs/7.22/databases/import-export/export-data.md
@@ -37,7 +37,7 @@ To export data from a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
 
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Export**.
 
diff --git a/content/operate/rs/7.22/databases/import-export/flush.md b/content/operate/rs/7.22/databases/import-export/flush.md
index 6b9a3324b4..a8bb6aad05 100644
--- a/content/operate/rs/7.22/databases/import-export/flush.md
+++ b/content/operate/rs/7.22/databases/import-export/flush.md
@@ -94,7 +94,7 @@ To flush data from an Active-Active database, use one of the following methods:
 
     1. On the **Databases** screen, select the database from the list, then click **Configuration**.
 
-    1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Flush database**.
 
diff --git a/content/operate/rs/7.22/databases/import-export/import-data.md b/content/operate/rs/7.22/databases/import-export/import-data.md
index d3e7b5b1a9..bdba9c836c 100644
--- a/content/operate/rs/7.22/databases/import-export/import-data.md
+++ b/content/operate/rs/7.22/databases/import-export/import-data.md
@@ -28,7 +28,7 @@ such as when you want to import from a backup of a clustered database.
 To import data into a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 1. Select **Import**.
 1. Select the tab that corresponds to your storage location type and enter the location details.
 
diff --git a/content/operate/rs/7.22/databases/import-export/replica-of/create.md b/content/operate/rs/7.22/databases/import-export/replica-of/create.md
index 5562cac111..bb38e3af2f 100644
--- a/content/operate/rs/7.22/databases/import-export/replica-of/create.md
+++ b/content/operate/rs/7.22/databases/import-export/replica-of/create.md
@@ -199,7 +199,7 @@ To enable TLS for Replica Of in the destination database:
 
 1. Expand the **Replica Of** section.
 
-1. Point to the source database entry and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit it.
+1. Point to the source database entry and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit it.
 
 1. Paste or upload the source proxy certificate, then select **Done**.
 
diff --git a/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md
index 5b60a8f80e..8581cb187c 100644
--- a/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md
+++ b/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-database.md
@@ -49,7 +49,7 @@ Before upgrading a database:
 
     To determine the current database version:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - _(Optional)_ Use the [`rladmin status extra all`](/content/operate/rs/7.22/references/cli-utilities/rladmin/status.md) command to display configuration details:
 
@@ -119,7 +119,7 @@ To upgrade a database:
 
     To do so:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - Use [`rladmin status databases extra all`](/content/operate/rs/7.22/references/cli-utilities/rladmin/status.md#status-databases) to display a list of the databases in your cluster and their current Redis database compatibility version:
 
diff --git a/content/operate/rs/7.22/monitoring/v1_monitoring.md b/content/operate/rs/7.22/monitoring/v1_monitoring.md
index 0753a1b245..f40147aaec 100644
--- a/content/operate/rs/7.22/monitoring/v1_monitoring.md
+++ b/content/operate/rs/7.22/monitoring/v1_monitoring.md
@@ -99,7 +99,7 @@ In **Cluster > Alert Settings**, you can enable alerts for node or cluster eve
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the node and cluster
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the node and cluster
 - In the **log**
 - In email notifications, if you configure [email alerts](#send-alerts-by-email)
 
@@ -118,7 +118,7 @@ For each database, you can enable alerts for database events, such as high memor
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the database
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the database
 - In the **log**
 - In emails, if you configure [email alerts](#send-alerts-by-email)
 
diff --git a/content/operate/rs/7.22/references/compatibility/resp.md b/content/operate/rs/7.22/references/compatibility/resp.md
index 922ed3b5b9..02b6eaf8ea 100644
--- a/content/operate/rs/7.22/references/compatibility/resp.md
+++ b/content/operate/rs/7.22/references/compatibility/resp.md
@@ -85,7 +85,7 @@ To change `resp3_default` to `disabled`, use one of the following methods:
 
 - Cluster Manager UI:
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.22/security/encryption/internode-encryption.md b/content/operate/rs/7.22/security/encryption/internode-encryption.md
index 9ef8d855f2..3683574295 100644
--- a/content/operate/rs/7.22/security/encryption/internode-encryption.md
+++ b/content/operate/rs/7.22/security/encryption/internode-encryption.md
@@ -63,7 +63,7 @@ To enable internode encryption for new databases by default, use one of the foll
 
 - Cluster Manager UI
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Database defaults**.
 
diff --git a/content/operate/rs/7.4/clusters/monitoring/_index.md b/content/operate/rs/7.4/clusters/monitoring/_index.md
index 14487d13d9..75f70d851e 100644
--- a/content/operate/rs/7.4/clusters/monitoring/_index.md
+++ b/content/operate/rs/7.4/clusters/monitoring/_index.md
@@ -44,7 +44,7 @@ In **Cluster > Alert Settings**, you can enable alerts for node or cluster eve
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the node and cluster
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the node and cluster
 - In the **log**
 - In email notifications, if you configure [email alerts](#send-alerts-by-email)
 
@@ -63,7 +63,7 @@ For each database, you can enable alerts for database events, such as high memor
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the database
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the database
 - In the **log**
 - In emails, if you configure [email alerts](#send-alerts-by-email)
 
diff --git a/content/operate/rs/7.4/clusters/replace-node.md b/content/operate/rs/7.4/clusters/replace-node.md
index 101035a013..169e90f476 100644
--- a/content/operate/rs/7.4/clusters/replace-node.md
+++ b/content/operate/rs/7.4/clusters/replace-node.md
@@ -10,7 +10,7 @@ linkTitle: Replace node
 weight: 90
 url: '/operate/rs/7.4/clusters/replace-node/'
 ---
-A failed node will appear as `Down` ({{< image filename="/images/rs/icons/node-down-icon.png#no-click" alt="Node down icon" class="inline" >}}) in the **Nodes** list.
+A failed node will appear as `Down` (![Node down icon](/images/rs/icons/node-down-icon.png#no-click)) in the **Nodes** list.
 
 To replace a failed node: 
 
diff --git a/content/operate/rs/7.4/databases/active-active/manage.md b/content/operate/rs/7.4/databases/active-active/manage.md
index 4032292961..d4a36d75af 100644
--- a/content/operate/rs/7.4/databases/active-active/manage.md
+++ b/content/operate/rs/7.4/databases/active-active/manage.md
@@ -74,7 +74,7 @@ To remove a participating cluster using the Cluster Manager UI:
 
     ![Edit and delete buttons appear when you point to an entry in the Other participating clusters list.](/images/rs/screenshots/databases/active-active-databases/participating-clusters-edit-delete.png)
 
-1. Click {{< image filename="/images/rs/buttons/delete-button.png#no-click" alt="The Delete button" width="25px" class="inline" >}} to remove the cluster.
+1. Click ![The Delete button](/images/rs/buttons/delete-button.png#no-click) to remove the cluster.
 
 1. Click **Save**.
 
diff --git a/content/operate/rs/7.4/databases/configure/db-defaults.md b/content/operate/rs/7.4/databases/configure/db-defaults.md
index 008fbe936b..af0eb907db 100644
--- a/content/operate/rs/7.4/databases/configure/db-defaults.md
+++ b/content/operate/rs/7.4/databases/configure/db-defaults.md
@@ -19,7 +19,7 @@ Database defaults are cluster-wide policies that determine default settings when
 
 To edit default database configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Database defaults**.
 
diff --git a/content/operate/rs/7.4/databases/configure/db-upgrade.md b/content/operate/rs/7.4/databases/configure/db-upgrade.md
index ef0692ce03..c3bd6a0fec 100644
--- a/content/operate/rs/7.4/databases/configure/db-upgrade.md
+++ b/content/operate/rs/7.4/databases/configure/db-upgrade.md
@@ -18,7 +18,7 @@ Database upgrade configuration includes cluster-wide policies that affect defaul
 
 To edit database upgrade configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.4/databases/delete.md b/content/operate/rs/7.4/databases/delete.md
index 16d6fc6a5b..7b8cb63df0 100644
--- a/content/operate/rs/7.4/databases/delete.md
+++ b/content/operate/rs/7.4/databases/delete.md
@@ -17,6 +17,6 @@ To delete a database from the Cluster Manager UI:
 
 1. From the **Databases** list, select the database, then select **Configuration**.
 
-1. Select {{< image filename="/images/rs/icons/delete-icon.png#no-click" alt="Delete button" width="22px" class="inline" >}} **Delete**.
+1. Select ![Delete button](/images/rs/icons/delete-icon.png#no-click) **Delete**.
 
 1. In the **Delete database** dialog, confirm deletion.
diff --git a/content/operate/rs/7.4/databases/import-export/export-data.md b/content/operate/rs/7.4/databases/import-export/export-data.md
index 867112c6dd..c080421a74 100644
--- a/content/operate/rs/7.4/databases/import-export/export-data.md
+++ b/content/operate/rs/7.4/databases/import-export/export-data.md
@@ -37,7 +37,7 @@ To export data from a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
 
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Export**.
 
diff --git a/content/operate/rs/7.4/databases/import-export/import-data.md b/content/operate/rs/7.4/databases/import-export/import-data.md
index 5c7a42dfef..f63f257504 100644
--- a/content/operate/rs/7.4/databases/import-export/import-data.md
+++ b/content/operate/rs/7.4/databases/import-export/import-data.md
@@ -26,7 +26,7 @@ such as when you want to import from a backup of a clustered database.
 To import data into a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 1. Select **Import**.
 1. Select the tab that corresponds to your storage location type and enter the location details.
 
diff --git a/content/operate/rs/7.4/databases/import-export/replica-of/create.md b/content/operate/rs/7.4/databases/import-export/replica-of/create.md
index bb3d635296..acb2bff47f 100644
--- a/content/operate/rs/7.4/databases/import-export/replica-of/create.md
+++ b/content/operate/rs/7.4/databases/import-export/replica-of/create.md
@@ -173,7 +173,7 @@ To enable TLS for Replica Of in the destination database:
 
 1. Expand the **Replica Of** section.
 
-1. Point to the source database entry and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit it.
+1. Point to the source database entry and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit it.
 
 1. Paste or upload the source proxy certificate, then select **Done**.
 
diff --git a/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md
index f3daa7ef27..9beb203734 100644
--- a/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md
+++ b/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-database.md
@@ -46,7 +46,7 @@ Before upgrading a database:
 
     To determine the database version:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - _(Optional)_ Use the [`rladmin status extra all`](/content/operate/rs/7.4/references/cli-utilities/rladmin/status.md) command to display configuration details:
 
@@ -114,7 +114,7 @@ To upgrade a database:
 
     To do so:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - Use [`rladmin status databases extra all`](/content/operate/rs/7.4/references/cli-utilities/rladmin/status.md#status-databases) to display a list of the databases in your cluster and their current Redis database compatibility version:
 
diff --git a/content/operate/rs/7.4/references/compatibility/resp.md b/content/operate/rs/7.4/references/compatibility/resp.md
index d756c74d02..cd429700b5 100644
--- a/content/operate/rs/7.4/references/compatibility/resp.md
+++ b/content/operate/rs/7.4/references/compatibility/resp.md
@@ -85,7 +85,7 @@ To change `resp3_default` to `disabled`, use one of the following methods:
 
 - Cluster Manager UI:
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.4/security/access-control/create-cluster-roles.md b/content/operate/rs/7.4/security/access-control/create-cluster-roles.md
index 39b4b4954f..4f8a4d6f3c 100644
--- a/content/operate/rs/7.4/security/access-control/create-cluster-roles.md
+++ b/content/operate/rs/7.4/security/access-control/create-cluster-roles.md
@@ -54,7 +54,7 @@ To create a role that grants cluster access but does not grant access to any dat
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
diff --git a/content/operate/rs/7.4/security/access-control/create-combined-roles.md b/content/operate/rs/7.4/security/access-control/create-combined-roles.md
index 66d7090fb7..ecfb0fd8b4 100644
--- a/content/operate/rs/7.4/security/access-control/create-combined-roles.md
+++ b/content/operate/rs/7.4/security/access-control/create-combined-roles.md
@@ -23,7 +23,7 @@ To define a Redis ACL rule that you can assign to a role:
 
 1. From **Access Control > Redis ACLs**, you can either:
 
-    - Point to a Redis ACL and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing Redis ACL.
+    - Point to a Redis ACL and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing Redis ACL.
 
     - Select **+ Add Redis ACL** to create a new Redis ACL.
 
@@ -46,7 +46,7 @@ To create a role that grants database access privileges and allows access to the
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
@@ -66,7 +66,7 @@ To create a role that grants database access privileges and allows access to the
 
     ![Add databases to access](/images/rs/screenshots/access-control/access-control-role-databases.png)
 
-1. Select the check mark {{< image filename="/images/rs/buttons/checkmark-button.png#no-click" alt="The Check button" width="25px" class="inline" >}} to confirm.
+1. Select the check mark ![The Check button](/images/rs/buttons/checkmark-button.png#no-click) to confirm.
 
 1. Select **Save**.
 
diff --git a/content/operate/rs/7.4/security/access-control/create-db-roles.md b/content/operate/rs/7.4/security/access-control/create-db-roles.md
index 14d0dac1a2..330cb0b3e6 100644
--- a/content/operate/rs/7.4/security/access-control/create-db-roles.md
+++ b/content/operate/rs/7.4/security/access-control/create-db-roles.md
@@ -27,7 +27,7 @@ To define a Redis ACL rule that you can assign to a role:
 
 1. From **Access Control > Redis ACLs**, you can either:
 
-    - Point to a Redis ACL and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing Redis ACL.
+    - Point to a Redis ACL and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing Redis ACL.
 
     - Select **+ Add Redis ACL** to create a new Redis ACL.
 
@@ -52,7 +52,7 @@ To define a role for database access:
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
@@ -72,7 +72,7 @@ To define a role for database access:
 
     ![Add databases to access](/images/rs/screenshots/access-control/access-control-role-databases.png)
 
-1. Select the check mark {{< image filename="/images/rs/buttons/checkmark-button.png#no-click" alt="The Check button" width="25px" class="inline" >}} to confirm.
+1. Select the check mark ![The Check button](/images/rs/buttons/checkmark-button.png#no-click) to confirm.
 
 1. Select **Save**.
 
diff --git a/content/operate/rs/7.4/security/access-control/create-users.md b/content/operate/rs/7.4/security/access-control/create-users.md
index ba4387bd30..07d4036a0b 100644
--- a/content/operate/rs/7.4/security/access-control/create-users.md
+++ b/content/operate/rs/7.4/security/access-control/create-users.md
@@ -53,7 +53,7 @@ Assign a role, associated with specific databases and access control lists (ACLs
 
 1. From the **Access Control > Users** tab in the Cluster Manager UI, you can:
 
-    - Point to an existing user and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit the user.
+    - Point to an existing user and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit the user.
     
     - Select **+ Add user** to [create a new user](/content/operate/rs/7.4/security/access-control/create-users.md).
 
diff --git a/content/operate/rs/7.4/security/encryption/internode-encryption.md b/content/operate/rs/7.4/security/encryption/internode-encryption.md
index 0e27205e77..2ebe109ae6 100644
--- a/content/operate/rs/7.4/security/encryption/internode-encryption.md
+++ b/content/operate/rs/7.4/security/encryption/internode-encryption.md
@@ -63,7 +63,7 @@ To enable internode encryption for new databases by default, use one of the foll
 
 - Cluster Manager UI
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Database defaults**.
 
diff --git a/content/operate/rs/7.4/security/encryption/tls/enable-tls.md b/content/operate/rs/7.4/security/encryption/tls/enable-tls.md
index b9f5a75001..acb99c22ab 100644
--- a/content/operate/rs/7.4/security/encryption/tls/enable-tls.md
+++ b/content/operate/rs/7.4/security/encryption/tls/enable-tls.md
@@ -136,10 +136,10 @@ For each participating cluster, copy the syncer certificate from the **general**
     - **Enforce client authentication** is selected by default. If you clear this option, you will still enforce encryption, but TLS client authentication will be deactivated.
 1. Select **Require TLS for CRDB communication only** from the dropdown menu.
     {{< image filename="/images/rs/crdb-tls-all.png" alt="crdb-tls-all" >}}
-1. Select **Add** {{< image filename="/images/rs/icon_add.png#no-click" alt="Add" >}}
+1. Select **Add** ![Add](/images/rs/icon_add.png#no-click)
 1. Paste a syncer certificate into the text box.
     {{< image filename="/images/rs/database-tls-replica-certs.png" alt="Database TLS Configuration" >}}
-1. Save the syncer certificate. {{< image filename="/images/rs/icon_save.png#no-click" alt="Save" >}}
+1. Save the syncer certificate. ![Save](/images/rs/icon_save.png#no-click)
 1. Repeat this process, adding the syncer certificate for each participating cluster.
 1. Optional: If also you want to require TLS for client connections, select **Require TLS for All Communications** from the dropdown and add client certificates as well.
 1. Select **Update** at the bottom of the screen to save your configuration.
diff --git a/content/operate/rs/7.8/clusters/add-node.md b/content/operate/rs/7.8/clusters/add-node.md
index f6e126aa1a..141305dce7 100644
--- a/content/operate/rs/7.8/clusters/add-node.md
+++ b/content/operate/rs/7.8/clusters/add-node.md
@@ -84,7 +84,7 @@ We recommend that you verify the node is functioning properly using one of the f
 
 - Cluster Manager UI method:
 
-    1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to verify.
+    1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the node you want to verify.
     
     1. Select **Verify node** from the list.
 
diff --git a/content/operate/rs/7.8/clusters/change-node-role.md b/content/operate/rs/7.8/clusters/change-node-role.md
index c64a5e3b53..819a4f1ed1 100644
--- a/content/operate/rs/7.8/clusters/change-node-role.md
+++ b/content/operate/rs/7.8/clusters/change-node-role.md
@@ -17,7 +17,7 @@ A Redis Software cluster contains a primary node, which coordinates cluster-wide
 
 To demote the primary node to a secondary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the primary node you want to demote.
+1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the primary node you want to demote.
 
     ![Click the more actions button for a node to access node actions.](/images/rs/screenshots/nodes/primary-node-more-actions.png)
 
@@ -37,7 +37,7 @@ To demote the primary node to a secondary node using the Cluster Manager UI:
 
 To promote a secondary node to become the primary node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the secondary node you want to promote.
+1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the secondary node you want to promote.
 
     ![Click the more actions button for a node to access node actions.](/images/rs/screenshots/nodes/secondary-nodes-more-actions.png)
 
diff --git a/content/operate/rs/7.8/clusters/remove-node.md b/content/operate/rs/7.8/clusters/remove-node.md
index c40cf0941c..33d9b6e0aa 100644
--- a/content/operate/rs/7.8/clusters/remove-node.md
+++ b/content/operate/rs/7.8/clusters/remove-node.md
@@ -72,7 +72,7 @@ You can migrate resources by using the `rladmin` command-line interface
 
 To remove a node using the Cluster Manager UI:
 
-1. On the **Nodes** screen, click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="More actions button" width="22px" class="inline" >}} for the node you want to remove.
+1. On the **Nodes** screen, click ![More actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) for the node you want to remove.
 
     ![Click the more actions button for a node to access node actions.](/images/rs/screenshots/nodes/secondary-nodes-more-actions.png)
 
diff --git a/content/operate/rs/7.8/clusters/replace-node.md b/content/operate/rs/7.8/clusters/replace-node.md
index 9056c6495b..36934142f0 100644
--- a/content/operate/rs/7.8/clusters/replace-node.md
+++ b/content/operate/rs/7.8/clusters/replace-node.md
@@ -10,7 +10,7 @@ linkTitle: Replace node
 weight: 90
 url: '/operate/rs/7.8/clusters/replace-node/'
 ---
-A failed node will appear as `Down` ({{< image filename="/images/rs/icons/node-down-icon.png#no-click" alt="Node down icon" class="inline" >}}) in the **Nodes** list.
+A failed node will appear as `Down` (![Node down icon](/images/rs/icons/node-down-icon.png#no-click)) in the **Nodes** list.
 
 To replace a failed node: 
 
diff --git a/content/operate/rs/7.8/databases/active-active/manage.md b/content/operate/rs/7.8/databases/active-active/manage.md
index e74350885d..5e8f7f0192 100644
--- a/content/operate/rs/7.8/databases/active-active/manage.md
+++ b/content/operate/rs/7.8/databases/active-active/manage.md
@@ -74,7 +74,7 @@ To remove a participating cluster using the Cluster Manager UI:
 
     ![Edit and delete buttons appear when you point to an entry in the Other participating clusters list.](/images/rs/screenshots/databases/active-active-databases/participating-clusters-edit-delete.png)
 
-1. Click {{< image filename="/images/rs/buttons/delete-button.png#no-click" alt="The Delete button" width="25px" class="inline" >}} to remove the cluster.
+1. Click ![The Delete button](/images/rs/buttons/delete-button.png#no-click) to remove the cluster.
 
 1. Click **Save**.
 
diff --git a/content/operate/rs/7.8/databases/configure/db-defaults.md b/content/operate/rs/7.8/databases/configure/db-defaults.md
index 9e019b806b..f9820f5d66 100644
--- a/content/operate/rs/7.8/databases/configure/db-defaults.md
+++ b/content/operate/rs/7.8/databases/configure/db-defaults.md
@@ -19,7 +19,7 @@ Database defaults are cluster-wide policies that determine default settings when
 
 To edit default database configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Database defaults**.
 
diff --git a/content/operate/rs/7.8/databases/configure/db-tags.md b/content/operate/rs/7.8/databases/configure/db-tags.md
index 8064da163a..7434a7dd03 100644
--- a/content/operate/rs/7.8/databases/configure/db-tags.md
+++ b/content/operate/rs/7.8/databases/configure/db-tags.md
@@ -44,7 +44,7 @@ To edit a database's existing tags using the Cluster Manager UI:
 
 1. Go to the database's **Configuration** screen, then click **Edit**.
 
-1. Next to the existing **Tags**, click {{< image filename="/images/rs/buttons/edit-db-tags-button.png#no-click" alt="Edit tags button" width="22px" class="inline" >}}.
+1. Next to the existing **Tags**, click ![Edit tags button](/images/rs/buttons/edit-db-tags-button.png#no-click).
 
     ![The Edit tags button on the database configuration screen.](/images/rs/screenshots/databases/edit-db-tags-button-location.png)
 
diff --git a/content/operate/rs/7.8/databases/configure/db-upgrade.md b/content/operate/rs/7.8/databases/configure/db-upgrade.md
index deca9f1288..1a17d21af9 100644
--- a/content/operate/rs/7.8/databases/configure/db-upgrade.md
+++ b/content/operate/rs/7.8/databases/configure/db-upgrade.md
@@ -18,7 +18,7 @@ Database upgrade configuration includes cluster-wide policies that affect defaul
 
 To edit database upgrade configuration using the Cluster Manager UI:
 
-1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.8/databases/delete.md b/content/operate/rs/7.8/databases/delete.md
index 49bc17fff5..cbc3721b52 100644
--- a/content/operate/rs/7.8/databases/delete.md
+++ b/content/operate/rs/7.8/databases/delete.md
@@ -17,6 +17,6 @@ To delete a database from the Cluster Manager UI:
 
 1. From the **Databases** list, select the database, then select **Configuration**.
 
-1. Select {{< image filename="/images/rs/icons/delete-icon.png#no-click" alt="Delete button" width="22px" class="inline" >}} **Delete**.
+1. Select ![Delete button](/images/rs/icons/delete-icon.png#no-click) **Delete**.
 
 1. In the **Delete database** dialog, confirm deletion.
diff --git a/content/operate/rs/7.8/databases/import-export/export-data.md b/content/operate/rs/7.8/databases/import-export/export-data.md
index 7b15253fc8..8150837cb7 100644
--- a/content/operate/rs/7.8/databases/import-export/export-data.md
+++ b/content/operate/rs/7.8/databases/import-export/export-data.md
@@ -37,7 +37,7 @@ To export data from a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
 
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
 1. Select **Export**.
 
diff --git a/content/operate/rs/7.8/databases/import-export/flush.md b/content/operate/rs/7.8/databases/import-export/flush.md
index 193707327f..82330936ae 100644
--- a/content/operate/rs/7.8/databases/import-export/flush.md
+++ b/content/operate/rs/7.8/databases/import-export/flush.md
@@ -54,7 +54,7 @@ To flush data from an Active-Active database, use one of the following methods:
 
     1. On the **Databases** screen, select the database from the list, then click **Configuration**.
 
-    1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Flush database**.
 
diff --git a/content/operate/rs/7.8/databases/import-export/import-data.md b/content/operate/rs/7.8/databases/import-export/import-data.md
index c8b61a1994..94147748e8 100644
--- a/content/operate/rs/7.8/databases/import-export/import-data.md
+++ b/content/operate/rs/7.8/databases/import-export/import-data.md
@@ -26,7 +26,7 @@ such as when you want to import from a backup of a clustered database.
 To import data into a database using the Cluster Manager UI:
 
 1. On the **Databases** screen, select the database from the list, then select **Configuration**.
-1. Click {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+1. Click ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 1. Select **Import**.
 1. Select the tab that corresponds to your storage location type and enter the location details.
 
diff --git a/content/operate/rs/7.8/databases/import-export/replica-of/create.md b/content/operate/rs/7.8/databases/import-export/replica-of/create.md
index 6841ba2406..5c6c6fd66e 100644
--- a/content/operate/rs/7.8/databases/import-export/replica-of/create.md
+++ b/content/operate/rs/7.8/databases/import-export/replica-of/create.md
@@ -173,7 +173,7 @@ To enable TLS for Replica Of in the destination database:
 
 1. Expand the **Replica Of** section.
 
-1. Point to the source database entry and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit it.
+1. Point to the source database entry and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit it.
 
 1. Paste or upload the source proxy certificate, then select **Done**.
 
diff --git a/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md b/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md
index 2be69ba27c..7ab584dd4f 100644
--- a/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md
+++ b/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-database.md
@@ -48,7 +48,7 @@ Before upgrading a database:
 
     To determine the current database version:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - _(Optional)_ Use the [`rladmin status extra all`](/content/operate/rs/7.8/references/cli-utilities/rladmin/status.md) command to display configuration details:
 
@@ -116,7 +116,7 @@ To upgrade a database:
 
     To do so:
 
-    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select {{< image filename="/images/rs/icons/info-icon.png#no-click" alt="The About database button" width="18px" class="inline" >}} **About**.
+    - Use the Cluster Manager UI to open the **Configuration** tab for the database and select ![The About database button](/images/rs/icons/info-icon.png#no-click) **About**.
 
     - Use [`rladmin status databases extra all`](/content/operate/rs/7.8/references/cli-utilities/rladmin/status.md#status-databases) to display a list of the databases in your cluster and their current Redis database compatibility version:
 
diff --git a/content/operate/rs/7.8/monitoring/v1_monitoring.md b/content/operate/rs/7.8/monitoring/v1_monitoring.md
index aa76f16062..a67df087a7 100644
--- a/content/operate/rs/7.8/monitoring/v1_monitoring.md
+++ b/content/operate/rs/7.8/monitoring/v1_monitoring.md
@@ -51,7 +51,7 @@ In **Cluster > Alert Settings**, you can enable alerts for node or cluster eve
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the node and cluster
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the node and cluster
 - In the **log**
 - In email notifications, if you configure [email alerts](#send-alerts-by-email)
 
@@ -70,7 +70,7 @@ For each database, you can enable alerts for database events, such as high memor
 
 Configured alerts are shown:
 
-- As a notification on the status icon ( {{< image filename="/images/rs/icons/icon_warning.png#no-click" alt="Warning" width="18px" class="inline" >}} ) for the database
+- As a notification on the status icon ( ![Warning](/images/rs/icons/icon_warning.png#no-click) ) for the database
 - In the **log**
 - In emails, if you configure [email alerts](#send-alerts-by-email)
 
diff --git a/content/operate/rs/7.8/references/compatibility/resp.md b/content/operate/rs/7.8/references/compatibility/resp.md
index 2c71cba0d1..477dd0d92c 100644
--- a/content/operate/rs/7.8/references/compatibility/resp.md
+++ b/content/operate/rs/7.8/references/compatibility/resp.md
@@ -85,7 +85,7 @@ To change `resp3_default` to `disabled`, use one of the following methods:
 
 - Cluster Manager UI:
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Upgrade configuration**.
 
diff --git a/content/operate/rs/7.8/security/access-control/create-cluster-roles.md b/content/operate/rs/7.8/security/access-control/create-cluster-roles.md
index 9fb4776e2b..a86b9e0eea 100644
--- a/content/operate/rs/7.8/security/access-control/create-cluster-roles.md
+++ b/content/operate/rs/7.8/security/access-control/create-cluster-roles.md
@@ -58,7 +58,7 @@ To create a role that grants cluster access:
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
diff --git a/content/operate/rs/7.8/security/access-control/create-combined-roles.md b/content/operate/rs/7.8/security/access-control/create-combined-roles.md
index ed7356f462..7f4ac7c2ff 100644
--- a/content/operate/rs/7.8/security/access-control/create-combined-roles.md
+++ b/content/operate/rs/7.8/security/access-control/create-combined-roles.md
@@ -27,7 +27,7 @@ To define a Redis ACL rule using the Cluster Manager UI:
 
 1. From **Access Control > Redis ACLs**, you can either:
 
-    - Point to a Redis ACL and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing Redis ACL.
+    - Point to a Redis ACL and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing Redis ACL.
 
     - Select **+ Add Redis ACL** to create a new Redis ACL.
 
@@ -80,7 +80,7 @@ To define a role for combined access using the Cluster Manager UI:
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
@@ -100,7 +100,7 @@ To define a role for combined access using the Cluster Manager UI:
 
     ![Add databases to access](/images/rs/screenshots/access-control/access-control-role-databases.png)
 
-1. Select the check mark {{< image filename="/images/rs/buttons/checkmark-button.png#no-click" alt="The Check button" width="25px" class="inline" >}} to confirm.
+1. Select the check mark ![The Check button](/images/rs/buttons/checkmark-button.png#no-click) to confirm.
 
 1. Select **Save**.
 
diff --git a/content/operate/rs/7.8/security/access-control/create-db-roles.md b/content/operate/rs/7.8/security/access-control/create-db-roles.md
index f406a2e3a1..9d14cf7bde 100644
--- a/content/operate/rs/7.8/security/access-control/create-db-roles.md
+++ b/content/operate/rs/7.8/security/access-control/create-db-roles.md
@@ -29,7 +29,7 @@ To define a Redis ACL rule using the Cluster Manager UI:
 
 1. From **Access Control > Redis ACLs**, you can either:
 
-    - Point to a Redis ACL and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing Redis ACL.
+    - Point to a Redis ACL and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing Redis ACL.
 
     - Select **+ Add Redis ACL** to create a new Redis ACL.
 
@@ -82,7 +82,7 @@ To define a role for database access using the Cluster Manager UI:
 
 1. From **Access Control** > **Roles**, you can:
 
-    - Point to a role and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit an existing role.
+    - Point to a role and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit an existing role.
 
     - Select **+ Add role** to create a new role.
 
@@ -102,7 +102,7 @@ To define a role for database access using the Cluster Manager UI:
 
     ![Add databases to access](/images/rs/screenshots/access-control/access-control-role-databases.png)
 
-1. Select the check mark {{< image filename="/images/rs/buttons/checkmark-button.png#no-click" alt="The Check button" width="25px" class="inline" >}} to confirm.
+1. Select the check mark ![The Check button](/images/rs/buttons/checkmark-button.png#no-click) to confirm.
 
 1. Select **Save**.
 
diff --git a/content/operate/rs/7.8/security/access-control/create-users.md b/content/operate/rs/7.8/security/access-control/create-users.md
index 6ba42e3853..9a7d414acc 100644
--- a/content/operate/rs/7.8/security/access-control/create-users.md
+++ b/content/operate/rs/7.8/security/access-control/create-users.md
@@ -50,7 +50,7 @@ Assign a role, associated with specific databases and access control lists (ACLs
 
 1. From the **Access Control > Users** tab in the Cluster Manager UI, you can:
 
-    - Point to an existing user and select {{< image filename="/images/rs/buttons/edit-button.png#no-click" alt="The Edit button" width="25px" class="inline" >}} to edit the user.
+    - Point to an existing user and select ![The Edit button](/images/rs/buttons/edit-button.png#no-click) to edit the user.
     
     - Select **+ Add user** to [create a new user](/content/operate/rs/7.8/security/access-control/create-users.md).
 
diff --git a/content/operate/rs/7.8/security/encryption/internode-encryption.md b/content/operate/rs/7.8/security/encryption/internode-encryption.md
index 1d73fcb975..6971d5172b 100644
--- a/content/operate/rs/7.8/security/encryption/internode-encryption.md
+++ b/content/operate/rs/7.8/security/encryption/internode-encryption.md
@@ -63,7 +63,7 @@ To enable internode encryption for new databases by default, use one of the foll
 
 - Cluster Manager UI
 
-    1. On the **Databases** screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.
+    1. On the **Databases** screen, select ![Toggle actions button](/images/rs/buttons/button-toggle-actions-vertical.png#no-click) to open a list of additional actions.
 
     1. Select **Database defaults**.