From 4d71384afb3b5f69d4cc0ccb0bbe4635edbe9937 Mon Sep 17 00:00:00 2001
From: Valentin Lacour <valentin.lacour.ext@corp.ovh.com>
Date: Mon, 31 Mar 2025 10:07:48 +0200
Subject: [PATCH 1/3] feat(databases - Caching): add Valkey in name

---
 pages/index-translations.de.yaml              |  6 +--
 pages/index-translations.es.yaml              |  6 +--
 pages/index-translations.fq.yaml              |  6 +--
 pages/index-translations.fr.yaml              |  6 +--
 pages/index-translations.it.yaml              |  6 +--
 pages/index-translations.pl.yaml              |  6 +--
 pages/index-translations.pt.yaml              |  6 +--
 pages/index.md                                | 20 ++++-----
 .../guide.de-de.md                            | 10 ++---
 .../guide.en-asia.md                          | 10 ++---
 .../guide.en-au.md                            | 10 ++---
 .../guide.en-ca.md                            | 10 ++---
 .../guide.en-gb.md                            | 10 ++---
 .../guide.en-ie.md                            | 10 ++---
 .../guide.en-sg.md                            | 10 ++---
 .../guide.en-us.md                            | 10 ++---
 .../guide.es-es.md                            | 10 ++---
 .../guide.es-us.md                            | 10 ++---
 .../guide.fr-ca.md                            | 10 ++---
 .../guide.fr-fr.md                            | 10 ++---
 .../guide.it-it.md                            | 10 ++---
 .../guide.pl-pl.md                            | 10 ++---
 .../guide.pt-pt.md                            | 10 ++---
 .../guide.de-de.md                            |  2 +-
 .../guide.en-asia.md                          |  2 +-
 .../guide.en-au.md                            |  2 +-
 .../guide.en-ca.md                            |  2 +-
 .../guide.en-gb.md                            |  2 +-
 .../guide.en-ie.md                            |  2 +-
 .../guide.en-sg.md                            |  2 +-
 .../guide.en-us.md                            |  2 +-
 .../guide.es-es.md                            |  2 +-
 .../guide.es-us.md                            |  2 +-
 .../guide.fr-ca.md                            |  2 +-
 .../guide.fr-fr.md                            |  2 +-
 .../guide.it-it.md                            |  2 +-
 .../guide.pl-pl.md                            |  2 +-
 .../guide.pt-pt.md                            |  2 +-
 .../guide.de-de.md                            | 10 ++---
 .../guide.en-asia.md                          | 10 ++---
 .../guide.en-au.md                            | 10 ++---
 .../guide.en-ca.md                            | 10 ++---
 .../guide.en-gb.md                            | 10 ++---
 .../guide.en-ie.md                            | 10 ++---
 .../guide.en-sg.md                            | 10 ++---
 .../guide.en-us.md                            | 10 ++---
 .../guide.es-es.md                            | 10 ++---
 .../guide.es-us.md                            | 10 ++---
 .../guide.fr-ca.md                            | 10 ++---
 .../guide.fr-fr.md                            | 10 ++---
 .../guide.it-it.md                            | 10 ++---
 .../guide.pl-pl.md                            | 10 ++---
 .../guide.pt-pt.md                            | 10 ++---
 .../databases_08_vrack/guide.de-de.md         |  4 +-
 .../databases_08_vrack/guide.en-asia.md       |  4 +-
 .../databases_08_vrack/guide.en-au.md         |  4 +-
 .../databases_08_vrack/guide.en-ca.md         |  4 +-
 .../databases_08_vrack/guide.en-gb.md         |  4 +-
 .../databases_08_vrack/guide.en-ie.md         |  4 +-
 .../databases_08_vrack/guide.en-sg.md         |  4 +-
 .../databases_08_vrack/guide.en-us.md         |  4 +-
 .../databases_08_vrack/guide.es-es.md         |  4 +-
 .../databases_08_vrack/guide.es-us.md         |  4 +-
 .../databases_08_vrack/guide.fr-ca.md         |  4 +-
 .../databases_08_vrack/guide.fr-fr.md         |  4 +-
 .../databases_08_vrack/guide.it-it.md         |  4 +-
 .../databases_08_vrack/guide.pl-pl.md         |  4 +-
 .../databases_08_vrack/guide.pt-pt.md         |  4 +-
 .../guide.de-de.md                            |  2 +-
 .../guide.en-asia.md                          |  2 +-
 .../guide.en-au.md                            |  2 +-
 .../guide.en-ca.md                            |  2 +-
 .../guide.en-gb.md                            |  2 +-
 .../guide.en-ie.md                            |  2 +-
 .../guide.en-sg.md                            |  2 +-
 .../guide.en-us.md                            |  2 +-
 .../guide.es-es.md                            |  2 +-
 .../guide.es-us.md                            |  2 +-
 .../guide.fr-ca.md                            |  2 +-
 .../guide.fr-fr.md                            |  2 +-
 .../guide.it-it.md                            |  2 +-
 .../guide.pl-pl.md                            |  2 +-
 .../guide.pt-pt.md                            |  2 +-
 .../guide.de-de.md                            |  2 +-
 .../guide.en-asia.md                          |  2 +-
 .../guide.en-au.md                            |  2 +-
 .../guide.en-ca.md                            |  2 +-
 .../guide.en-gb.md                            |  2 +-
 .../guide.en-ie.md                            |  2 +-
 .../guide.en-sg.md                            |  2 +-
 .../guide.en-us.md                            |  2 +-
 .../guide.es-es.md                            |  2 +-
 .../guide.es-us.md                            |  2 +-
 .../guide.fr-ca.md                            |  2 +-
 .../guide.fr-fr.md                            |  2 +-
 .../guide.it-it.md                            |  2 +-
 .../guide.pl-pl.md                            |  2 +-
 .../guide.pt-pt.md                            |  2 +-
 .../guide.de-de.md                            |  4 +-
 .../guide.en-asia.md                          |  4 +-
 .../guide.en-au.md                            |  4 +-
 .../guide.en-ca.md                            |  4 +-
 .../guide.en-gb.md                            |  4 +-
 .../guide.en-ie.md                            |  4 +-
 .../guide.en-sg.md                            |  4 +-
 .../guide.en-us.md                            |  4 +-
 .../guide.es-es.md                            |  4 +-
 .../guide.es-us.md                            |  4 +-
 .../guide.fr-ca.md                            |  4 +-
 .../guide.fr-fr.md                            |  4 +-
 .../guide.it-it.md                            |  4 +-
 .../guide.pl-pl.md                            |  4 +-
 .../guide.pt-pt.md                            |  4 +-
 .../guide.de-de.md                            |  6 +--
 .../guide.en-asia.md                          |  6 +--
 .../guide.en-au.md                            |  6 +--
 .../guide.en-ca.md                            |  6 +--
 .../guide.en-gb.md                            |  6 +--
 .../guide.en-ie.md                            |  6 +--
 .../guide.en-sg.md                            |  6 +--
 .../guide.en-us.md                            |  6 +--
 .../guide.es-es.md                            |  6 +--
 .../guide.es-us.md                            |  6 +--
 .../guide.fr-ca.md                            |  6 +--
 .../guide.fr-fr.md                            |  6 +--
 .../guide.it-it.md                            |  6 +--
 .../guide.pl-pl.md                            |  6 +--
 .../guide.pt-pt.md                            |  6 +--
 .../guide.de-de.md                            |  2 +-
 .../guide.en-asia.md                          |  2 +-
 .../guide.en-au.md                            |  2 +-
 .../guide.en-ca.md                            |  2 +-
 .../guide.en-gb.md                            |  2 +-
 .../guide.en-ie.md                            |  2 +-
 .../guide.en-sg.md                            |  2 +-
 .../guide.en-us.md                            |  2 +-
 .../guide.es-es.md                            |  2 +-
 .../guide.es-us.md                            |  2 +-
 .../guide.fr-ca.md                            |  2 +-
 .../guide.fr-fr.md                            |  2 +-
 .../guide.it-it.md                            |  2 +-
 .../guide.pl-pl.md                            |  2 +-
 .../guide.pt-pt.md                            |  2 +-
 .../guide.de-de.md                            |  8 ++--
 .../guide.en-asia.md                          |  8 ++--
 .../guide.en-au.md                            |  8 ++--
 .../guide.en-ca.md                            |  8 ++--
 .../guide.en-gb.md                            |  8 ++--
 .../guide.en-ie.md                            |  8 ++--
 .../guide.en-sg.md                            |  8 ++--
 .../guide.en-us.md                            |  8 ++--
 .../guide.es-es.md                            |  8 ++--
 .../guide.es-us.md                            |  8 ++--
 .../guide.fr-ca.md                            |  8 ++--
 .../guide.fr-fr.md                            |  8 ++--
 .../guide.it-it.md                            |  8 ++--
 .../guide.pl-pl.md                            |  8 ++--
 .../guide.pt-pt.md                            |  8 ++--
 .../redis_01_capabilities/guide.de-de.md      | 14 +++----
 .../redis_01_capabilities/guide.en-asia.md    | 14 +++----
 .../redis_01_capabilities/guide.en-au.md      | 14 +++----
 .../redis_01_capabilities/guide.en-ca.md      | 14 +++----
 .../redis_01_capabilities/guide.en-gb.md      | 14 +++----
 .../redis_01_capabilities/guide.en-ie.md      | 14 +++----
 .../redis_01_capabilities/guide.en-sg.md      | 14 +++----
 .../redis_01_capabilities/guide.en-us.md      | 14 +++----
 .../redis_01_capabilities/guide.es-es.md      | 14 +++----
 .../redis_01_capabilities/guide.es-us.md      | 14 +++----
 .../redis_01_capabilities/guide.fr-ca.md      | 14 +++----
 .../redis_01_capabilities/guide.fr-fr.md      | 14 +++----
 .../redis_01_capabilities/guide.it-it.md      | 14 +++----
 .../redis_01_capabilities/guide.pl-pl.md      | 14 +++----
 .../redis_01_capabilities/guide.pt-pt.md      | 14 +++----
 .../redis_03_connect_cli/guide.de-de.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-asia.md     | 16 +++----
 .../redis_03_connect_cli/guide.en-au.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-ca.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-gb.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-ie.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-sg.md       | 16 +++----
 .../redis_03_connect_cli/guide.en-us.md       | 16 +++----
 .../redis_03_connect_cli/guide.es-es.md       | 16 +++----
 .../redis_03_connect_cli/guide.es-us.md       | 16 +++----
 .../redis_03_connect_cli/guide.fr-ca.md       | 16 +++----
 .../redis_03_connect_cli/guide.fr-fr.md       | 16 +++----
 .../redis_03_connect_cli/guide.it-it.md       | 16 +++----
 .../redis_03_connect_cli/guide.pl-pl.md       | 16 +++----
 .../redis_03_connect_cli/guide.pt-pt.md       | 16 +++----
 .../redis_04_connect_php/guide.de-de.md       | 16 +++----
 .../redis_04_connect_php/guide.en-asia.md     | 16 +++----
 .../redis_04_connect_php/guide.en-au.md       | 16 +++----
 .../redis_04_connect_php/guide.en-ca.md       | 16 +++----
 .../redis_04_connect_php/guide.en-gb.md       | 16 +++----
 .../redis_04_connect_php/guide.en-ie.md       | 16 +++----
 .../redis_04_connect_php/guide.en-sg.md       | 16 +++----
 .../redis_04_connect_php/guide.en-us.md       | 16 +++----
 .../redis_04_connect_php/guide.es-es.md       | 16 +++----
 .../redis_04_connect_php/guide.es-us.md       | 16 +++----
 .../redis_04_connect_php/guide.fr-ca.md       | 16 +++----
 .../redis_04_connect_php/guide.fr-fr.md       | 16 +++----
 .../redis_04_connect_php/guide.it-it.md       | 16 +++----
 .../redis_04_connect_php/guide.pl-pl.md       | 16 +++----
 .../redis_04_connect_php/guide.pt-pt.md       | 16 +++----
 .../redis_05_connect_python/guide.de-de.md    | 12 +++---
 .../redis_05_connect_python/guide.en-asia.md  | 12 +++---
 .../redis_05_connect_python/guide.en-au.md    | 12 +++---
 .../redis_05_connect_python/guide.en-ca.md    | 12 +++---
 .../redis_05_connect_python/guide.en-gb.md    | 12 +++---
 .../redis_05_connect_python/guide.en-ie.md    | 12 +++---
 .../redis_05_connect_python/guide.en-sg.md    | 12 +++---
 .../redis_05_connect_python/guide.en-us.md    | 12 +++---
 .../redis_05_connect_python/guide.es-es.md    | 12 +++---
 .../redis_05_connect_python/guide.es-us.md    | 12 +++---
 .../redis_05_connect_python/guide.fr-ca.md    | 12 +++---
 .../redis_05_connect_python/guide.fr-fr.md    | 12 +++---
 .../redis_05_connect_python/guide.it-it.md    | 12 +++---
 .../redis_05_connect_python/guide.pl-pl.md    | 12 +++---
 .../redis_05_connect_python/guide.pt-pt.md    | 12 +++---
 .../guide.de-de.md                            | 28 ++++++-------
 .../guide.en-asia.md                          | 28 ++++++-------
 .../guide.en-au.md                            | 28 ++++++-------
 .../guide.en-ca.md                            | 28 ++++++-------
 .../guide.en-gb.md                            | 28 ++++++-------
 .../guide.en-ie.md                            | 28 ++++++-------
 .../guide.en-sg.md                            | 28 ++++++-------
 .../guide.en-us.md                            | 28 ++++++-------
 .../guide.es-es.md                            | 28 ++++++-------
 .../guide.es-us.md                            | 28 ++++++-------
 .../guide.fr-ca.md                            | 28 ++++++-------
 .../guide.fr-fr.md                            | 28 ++++++-------
 .../guide.it-it.md                            | 28 ++++++-------
 .../guide.pl-pl.md                            | 28 ++++++-------
 .../guide.pt-pt.md                            | 28 ++++++-------
 .../redis_07_update_acls/guide.de-de.md       | 12 +++---
 .../redis_07_update_acls/guide.en-asia.md     | 12 +++---
 .../redis_07_update_acls/guide.en-au.md       | 12 +++---
 .../redis_07_update_acls/guide.en-ca.md       | 12 +++---
 .../redis_07_update_acls/guide.en-gb.md       | 12 +++---
 .../redis_07_update_acls/guide.en-ie.md       | 12 +++---
 .../redis_07_update_acls/guide.en-sg.md       | 12 +++---
 .../redis_07_update_acls/guide.en-us.md       | 12 +++---
 .../redis_07_update_acls/guide.es-es.md       | 12 +++---
 .../redis_07_update_acls/guide.es-us.md       | 12 +++---
 .../redis_07_update_acls/guide.fr-ca.md       | 12 +++---
 .../redis_07_update_acls/guide.fr-fr.md       | 12 +++---
 .../redis_07_update_acls/guide.it-it.md       | 12 +++---
 .../redis_07_update_acls/guide.pl-pl.md       | 12 +++---
 .../redis_07_update_acls/guide.pt-pt.md       | 12 +++---
 .../guide.de-de.md                            | 14 +++----
 .../guide.en-asia.md                          | 14 +++----
 .../guide.en-au.md                            | 14 +++----
 .../guide.en-ca.md                            | 14 +++----
 .../guide.en-gb.md                            | 14 +++----
 .../guide.en-ie.md                            | 14 +++----
 .../guide.en-sg.md                            | 14 +++----
 .../guide.en-us.md                            | 14 +++----
 .../guide.es-es.md                            | 14 +++----
 .../guide.es-us.md                            | 14 +++----
 .../guide.fr-ca.md                            | 14 +++----
 .../guide.fr-fr.md                            | 14 +++----
 .../guide.it-it.md                            | 14 +++----
 .../guide.pl-pl.md                            | 14 +++----
 .../guide.pt-pt.md                            | 14 +++----
 .../guide.de-de.md                            | 10 ++---
 .../guide.en-asia.md                          | 10 ++---
 .../guide.en-au.md                            | 10 ++---
 .../guide.en-ca.md                            | 10 ++---
 .../guide.en-gb.md                            | 10 ++---
 .../guide.en-ie.md                            | 10 ++---
 .../guide.en-sg.md                            | 10 ++---
 .../guide.en-us.md                            | 10 ++---
 .../guide.es-es.md                            | 10 ++---
 .../guide.es-us.md                            | 10 ++---
 .../guide.fr-ca.md                            | 10 ++---
 .../guide.fr-fr.md                            | 10 ++---
 .../guide.it-it.md                            | 10 ++---
 .../guide.pl-pl.md                            | 10 ++---
 .../guide.pt-pt.md                            | 10 ++---
 .../redis_tuto_01_wordpress/guide.de-de.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-asia.md  | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-au.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-ca.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-gb.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-ie.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-sg.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.en-us.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.es-es.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.es-us.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.fr-ca.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.fr-fr.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.it-it.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.pl-pl.md    | 42 +++++++++----------
 .../redis_tuto_01_wordpress/guide.pt-pt.md    | 42 +++++++++----------
 293 files changed, 1636 insertions(+), 1636 deletions(-)

diff --git a/pages/index-translations.de.yaml b/pages/index-translations.de.yaml
index c4d1c71f6d8..3462d3f79b8 100644
--- a/pages/index-translations.de.yaml
+++ b/pages/index-translations.de.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutorials
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutorials
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutorials
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials
diff --git a/pages/index-translations.es.yaml b/pages/index-translations.es.yaml
index ced2edf9c02..77061863572 100755
--- a/pages/index-translations.es.yaml
+++ b/pages/index-translations.es.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutorials
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutorials
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutorials
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials
diff --git a/pages/index-translations.fq.yaml b/pages/index-translations.fq.yaml
index baef8c6e5e5..b60e4350b89 100755
--- a/pages/index-translations.fq.yaml
+++ b/pages/index-translations.fq.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutoriels
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutoriels
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutoriels
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutoriels
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutoriels
diff --git a/pages/index-translations.fr.yaml b/pages/index-translations.fr.yaml
index 2abd4a9b739..909cb75a6e0 100755
--- a/pages/index-translations.fr.yaml
+++ b/pages/index-translations.fr.yaml
@@ -148,9 +148,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutoriels
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutoriels
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutoriels
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutoriels
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutoriels
diff --git a/pages/index-translations.it.yaml b/pages/index-translations.it.yaml
index bc8b40a430b..b2b3f6d3f16 100644
--- a/pages/index-translations.it.yaml
+++ b/pages/index-translations.it.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutorials
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutorials
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutorials
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials
diff --git a/pages/index-translations.pl.yaml b/pages/index-translations.pl.yaml
index 89ff5ea402d..63755fd408e 100755
--- a/pages/index-translations.pl.yaml
+++ b/pages/index-translations.pl.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutorials
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutorials
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutorials
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials
diff --git a/pages/index-translations.pt.yaml b/pages/index-translations.pt.yaml
index 23ed4c434d3..74185d348fd 100755
--- a/pages/index-translations.pt.yaml
+++ b/pages/index-translations.pt.yaml
@@ -147,9 +147,9 @@ public-cloud-databases-mysql-tutorials: MySQL - Tutorials
 public-cloud-databases-postgresql: PostgreSQL
 public-cloud-databases-postgresql-guides: PostgreSQL - Guides
 public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials
-public-cloud-databases-redis: Caching
-public-cloud-databases-redis-guides: Caching - Guides
-public-cloud-databases-redis-tutorials: Caching - Tutorials
+public-cloud-databases-redis: Caching/Valkey
+public-cloud-databases-redis-guides: Caching/Valkey - Guides
+public-cloud-databases-redis-tutorials: Caching/Valkey - Tutorials
 public-cloud-data-analytics-grafana: Dashboards
 public-cloud-data-analytics-grafana-guides: Dashboards - Guides
 public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials
diff --git a/pages/index.md b/pages/index.md
index a2f309438d0..7e02ec011db 100644
--- a/pages/index.md
+++ b/pages/index.md
@@ -804,18 +804,18 @@
                 + [PostgreSQL - Tutorial - Build a Strapi app connected to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_01_connect_strapi_to_managed_postgresql)
                 + [PostgreSQL - Tutorial - Install Wagtail and connect it to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_02_connect_wagtail_to_managed_postgresql)
                 + [PostgreSQL - Tutorial - How to migrate an on-premises database to Public Cloud Databases](public_cloud/public_cloud_databases/postgresql_tuto_03_migrate_ecdb)
-        + [Caching](products/public-cloud-databases-redis)
+        + [Caching/Valkey](products/public-cloud-databases-redis)
             + [Guides](public-cloud-databases-redis-guides)
-                + [Caching - Capabilities and Limitations](public_cloud/public_cloud_databases/redis_01_capabilities)
-                + [Caching - Configure your Caching service to accept incoming connections](public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections)
-                + [Caching - Connect with CLI](public_cloud/public_cloud_databases/redis_03_connect_cli)
-                + [Caching - Connect with PHP](public_cloud/public_cloud_databases/redis_04_connect_php)
-                + [Caching - Connect with Python](public_cloud/public_cloud_databases/redis_05_connect_python)
-                + [Caching - Connect with RedisInsight](public_cloud/public_cloud_databases/redis_06_connect_redisinsight)
-                + [Caching - Manage ACLs via API](public_cloud/public_cloud_databases/redis_07_update_acls)
-                + [Caching - Advanced parameters references](public_cloud/public_cloud_databases/redis_09_advanced_parameters_references)
+                + [Caching/Valkey - Capabilities and Limitations](public_cloud/public_cloud_databases/redis_01_capabilities)
+                + [Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections](public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections)
+                + [Caching/Valkey - Connect with CLI](public_cloud/public_cloud_databases/redis_03_connect_cli)
+                + [Caching/Valkey - Connect with PHP](public_cloud/public_cloud_databases/redis_04_connect_php)
+                + [Caching/Valkey - Connect with Python](public_cloud/public_cloud_databases/redis_05_connect_python)
+                + [Caching/Valkey - Connect with RedisInsight](public_cloud/public_cloud_databases/redis_06_connect_redisinsight)
+                + [Caching/Valkey - Manage ACLs via API](public_cloud/public_cloud_databases/redis_07_update_acls)
+                + [Caching/Valkey - Advanced parameters references](public_cloud/public_cloud_databases/redis_09_advanced_parameters_references)
             + [Tutorials](public-cloud-databases-redis-tutorials)
-                + [Caching - Tutorial - Boost your CMS (from the example of WordPress)](public_cloud/public_cloud_databases/redis_tuto_01_wordpress)
+                + [Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)](public_cloud/public_cloud_databases/redis_tuto_01_wordpress)
         + [Cassandra](products/public-cloud-databases-cassandra)
             + [Guides](public-cloud-databases-cassandra-guides)
                 + [Cassandra - Capabilities and Limitations](public_cloud/public_cloud_databases/cassandra_01_capabilities)
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md
index dc935c3e487..c14ac91dc18 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md
index dc935c3e487..c14ac91dc18 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md
index 5496db50241..41a75f5b236 100644
--- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md
@@ -15,7 +15,7 @@ Public cloud database engines are managed services, which means that they are no
 > - Cassandra
 > - MySQL
 > - PostgreSQL
-> - Caching
+> - Caching/Valkey
 
 
 ## Requirements
@@ -100,7 +100,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -130,7 +130,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
@@ -158,7 +158,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis/{clusterId}/capabilities/advancedConfiguration
@@ -186,7 +186,7 @@ Open the following API call and paste the corresponding inputs (serviceName, clu
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/postgresql/{clusterId}/advancedConfiguration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/redis/{clusterId}/advancedConfiguration
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
index 3d4674f3342..b838e110902 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
index 3d4674f3342..b838e110902 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
index 7b3b8517443..d0947f170a4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
@@ -28,7 +28,7 @@ MongoDB | Backup on object storage | Off-Site | Daily | 24h | Yes
 MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minutes | Yes
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
-Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
+Caching/Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
 M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
index f8985cf00af..b9a0459b670 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
index a458bc2bf15..79b7fd21f8c 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
index ccfc7f320cc..62d876a23b5 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
index c851900ba75..ea24cc09304 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
index 743230bacb3..7abb693049d 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
index d926c3a8063..2c9ed1782c6 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
index 6f4e2f3343f..3be54eab020 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
index 85759eb9964..af1d26d7792 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
index e78760f6d65..8f72d8f796f 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
index 69fce2da287..d829f406cdb 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
index e8fc51b1787..ea71d3e4d5e 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
index 745cfaea97f..fa03f215f3c 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
index 0e300ce6a71..5a3d6e0e1c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
index 8493784a940..b23acaf6645 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
index 7c84fc50667..d061b5ca3d7 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching/Valkey or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -207,7 +207,7 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/redis
@@ -260,7 +260,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/postgresql/{clusterId}/capabilities/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
@@ -314,7 +314,7 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
@@ -378,7 +378,7 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/postgresql/{clusterId}/integration
 >> >
-> Caching
+> Caching/Valkey
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/caching/{clusterId}/integration
 >> >
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.de-de.md
index 172ef2030b3..5e3e79f0d88 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.de-de.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-asia.md
index a86aa6ee972..3c473900f2b 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-asia.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-au.md
index 2214c37a748..3f08dd4bfb7 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-au.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ca.md
index 5e08b7f3884..ef5ceed0755 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ca.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-gb.md
index d384aa60225..5bef67a5455 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-gb.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ie.md
index f9843054a5c..101c65c76f6 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-ie.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-sg.md
index 886cbaf3a64..c6dc4ad191a 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-sg.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-us.md
index 972ff96b003..83e250c6e39 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.en-us.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-es.md
index b4c558416b5..b3c2edb9699 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-es.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-us.md
index 451e29c3508..d826cfa0139 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.es-us.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-ca.md
index 9bc6f4a64c2..2e6c2c20b44 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-ca.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-fr.md
index 9c59a68df63..8ae1f14130c 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.fr-fr.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.it-it.md
index b50f3bc5f3e..7976fa178bc 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.it-it.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pl-pl.md
index 8b01319ed50..3e15156a9b8 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pl-pl.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pt-pt.md
index fb8cab81dbd..4f8853dc69e 100644
--- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/guide.pt-pt.md
@@ -82,7 +82,7 @@ Follow this [guide](/pages/public_cloud/compute/public-cloud-first-steps) to cre
 >If you want to test the access from an existing instance, read this tutorial to connect it to the vRack: [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#in-case-of-an-existing-instance).
 >
 
-### Step 5 - Example of verification with a Public Cloud Databases for Caching
+### Step 5 - Example of verification with a Public Cloud Databases for Caching/Valkey
 
 We assume that you have an already set SSH key on your project. For more details, read the [Creating and connecting to your first Public Cloud instance](/pages/public_cloud/compute/public-cloud-first-steps) page.
 
@@ -98,7 +98,7 @@ Now install the client by installing the `redis-server` package:
 sudo apt-get update && sudo apt-get install redis-server -y
 ```
 
-Now connect to the Caching service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
+Now connect to the Caching/Valkey service using the URL retrieved from the OVHcloud Control Panel, with a command such as:
 
 ```bash
 redis-cli --tls -u "rediss://my-redis-user@redis-2612345abc-abcd1234defg.database.cloud.ovh.net:20185"
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
index 288c94fdc7f..ad4df376548 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
index 288c94fdc7f..ad4df376548 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
index 09b444748dd..3680bfc5935 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
@@ -33,7 +33,7 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
+- `Caching/Valkey` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
 - `Cassandra` and `M3DB` turn to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md
index fa817e4e7ab..79fd5ef28c9 100644
--- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md
@@ -86,7 +86,7 @@ scrape_configs:
 
 Public Cloud Databases offer service metrics via Prometheus for the following engines:
 
-- Caching
+- Caching/Valkey
 - Cassandra
 - MongoDB
 - MySQL
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md
index ad0afedaeb5..fe457818174 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md
index 9df27a294ef..dca465dd99a 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md
index 8f2af1ad91b..c3cba7b6d83 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md
index 9b642e0f7dd..071eda347e8 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md
index 90a70f473e5..d36000957b7 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md
index 3c2285588fd..dc1b88ed046 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md
index ad9c48d47df..64fb7ac3486 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md
index 51177ec1fe2..ed73f84ee67 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md
index 7aef8ae14ae..fc031220d8a 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md
index 6e06bc38ee3..d1839873baa 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md
index baeaa166138..44424aaabbd 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md
index 3e89591dc59..c62cac8944c 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md
index ac191fd4c55..4b64882f1ba 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md
index 56474519099..9bd4091ed5d 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md
index 0ebdd07cefc..edf16aeaf5a 100644
--- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md
@@ -109,7 +109,7 @@ The key is never re-used and will be trashed at the destruction of the instance,
 We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key.
 - **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096.
 
-For all the databases engines such as MySQL, PostgreSQL, Caching and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
+For all the databases engines such as MySQL, PostgreSQL, Caching/Valkey and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage :
 
 - **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. 
 The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. 
@@ -151,7 +151,7 @@ The subscription to the Business support level is mandatory, at least to maintai
 You can  import and export your data  following recommendations provided by editors for each Database engine technology. Here are some examples :
 
 - For MongoDB, you can refer to this link : <https://www.mongodb.com/docs/compass/current/import-export/>
-- For Caching, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
+- For Caching/Valkey, you can refer to this link : <https://docs.redis.com/latest/rs/databases/import-export/>
 
 ### 9.1 Erasure of customer data
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
index 28796eebaaa..83867daef22 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
index bfa8617b418..eb064e3dec1 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
index bfa8617b418..eb064e3dec1 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
index c44c5a51f34..f6199d4662d 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
@@ -27,7 +27,7 @@ This lifecycle policy is applicable to :
 
 - All Public Cloud Databases services;
 - Including all the service plans (Essential, Business, Enterprise, Production, Advanced);
-- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching, ...
+- And all proposed DBMS, such as MySQL, PostgreSQL, MongoDB, Caching/Valkey, ...
 - Whatever state; if they are **up and running** or in a **sleeping state** (powered off, waiting for payment).
 
 ### Providing new major versions
@@ -77,9 +77,9 @@ MySQL EOL will coincide with the official MySQL Lifecycle schedule for linux : <
 
 PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <https://www.postgresql.org/support/versioning/>
 
-### Caching
+### Caching/Valkey
 
-Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
index aad84df8dd4..8f504d1eeb4 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
index 68cc3427814..e643becd403 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
index 14d6e399a78..51b7eeca88a 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
index a8a9b3e7df9..bc9022e517a 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
index 39b4adfc7f2..adaca75f93c 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
index 4ae7f859fd2..74d4af2a715 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
index 4be0ffc0715..50071838a93 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
index ea56e9a0ede..3b0ae1cf655 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
index 6afb4c75e6d..65851737829 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
index 3777e619c0f..2d89e2fae4c 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
index 1eac8ac585b..40a82eb70b7 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
index 355d770114e..5404cb8eae4 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
index ee21ae861f7..0c4ee6bfd86 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
index 302ac7baec5..ebe3d2aa82f 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
index b554b761ea5..760a6c24b94 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching/Valkey, Kafka, Cassandra, or M3 cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
index e09cbfc7970..66ced276f47 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
index 99b04fa14bc..e624cfa299d 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
index 99b04fa14bc..e624cfa299d 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
index e18ed100197..ae4f95943b9 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
@@ -30,10 +30,10 @@ See our [PostgreSQL Capabilities and limitations](/pages/public_cloud/public_clo
 MongoDB is a fully managed and scalable document-oriented database management system which does not require a predefined data schema.<br>
 See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) guide.
 
-### Caching
+### Caching/Valkey
 
-Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
-See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
+Caching/Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
+See our [Caching/Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
 ### M3db
 
@@ -47,7 +47,7 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching/Valkey | M3db | Cassandra |
 |--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
 | End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
 | Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
index 04315451833..e723b6b296c 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
index 86bd2918e76..5edad439f72 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
index 8cd0d08b52e..f485b07ce62 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
index 15565b14a8c..36627f9c649 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
index 8774aa7429a..465c9878aac 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
index 95cee0c885e..e7ea446efc7 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
index 44d8058a9b8..d427b871945 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
index a4bd5a10765..121039e3670 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
index f253aff9fbf..d9752d0c3a5 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
index fa5c09218bc..23d29a2964c 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
index ba4f934ff9c..a8762d07465 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capacités et limites (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capacités et limites (EN)
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
index e5ae0affdc0..1632ece9ccc 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capacités et limites (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capacités et limites (EN)
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
index 1c36ba6a42a..5fba1350692 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
index b8217c7d01b..9f7b19c05ad 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
index f412f894b79..619ccf03dde 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
@@ -1,12 +1,12 @@
 ---
-title: Caching - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching
+title: Caching/Valkey - Capabilities and Limitations
+excerpt: Discover the capabilities and limitations of Public Cloud Databases for Caching/Valkey
 updated: 2025-02-19
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching offer.
+This page provides the technical capabilities and limitations of the Public Cloud Databases for Caching/Valkey offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
@@ -26,7 +26,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 Database nodes have to be in the same region. Multi-AZ is currently not supported.
 
-### Caching versions
+### Caching/Valkey versions
 
 The Public Cloud Databases offer uses the following Redis® open source versions:
 
@@ -34,7 +34,7 @@ The Public Cloud Databases offer uses the following Redis® open source versions
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
-### Caching clients
+### Caching/Valkey clients
 
 You can use any of the [clients recommended by Redis®](https://redis.io/clients){.external} to access your instance.
 
@@ -77,7 +77,7 @@ For information on node types and pricing, please refer to the [price page](http
 ### Features
 
 #### Network
-Caching clusters are reachable through default port 20182.
+Caching/Valkey clusters are reachable through default port 20182.
 
 Public as well as private networking (vRack) can be used for all the offers.
 
@@ -100,7 +100,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Caching depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
+The number of simultaneous connections in Public Cloud Databases for Caching/Valkey depends on the available total memory on the server. We allow 4 \* megabytes_of_bytes_memory connections per RAM GB, but at least 10000 connections, even on the smallest servers.
 
 So for example on a server with 7GB memory, you will get up to 7 \* 4096 = 28672 simultaneous connections.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.de-de.md
index 973ab584bb3..c6cd8cc70ea 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de);
 - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-asia.md
index c27021201cb..4172062e20f 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia);
 - A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-au.md
index caeeee5f345..dddf230ba45 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au);
 - A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ca.md
index e831672874b..61247e7cc56 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca);
 - A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-gb.md
index e07751f2f29..fd7e0599629 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB);
 - A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ie.md
index 490d68b824c..667008786fb 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie);
 - A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-sg.md
index 34cd0f4004d..ee01fee64c2 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg);
 - A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-us.md
index 3630332d144..9958fbcfc80 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we);
 - A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-es.md
index 69c6fc84555..f982a332191 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es);
 - A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-us.md
index cd68d870c59..06dd6cfeeb5 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws);
 - A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-ca.md
index a56591f0ed6..a0d35ab1e85 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Se connecter avec CLI (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Se connecter avec CLI (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc);
 - A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-fr.md
index 2505d8a9a4d..6a905e7cb9a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Se connecter avec CLI (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Se connecter avec CLI (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr);
 - A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.it-it.md
index b573c7a34ce..f8c67538b8f 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it);
 - A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pl-pl.md
index aa2ebea8a4e..3a4cb42df18 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl);
 - A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pt-pt.md
index 0d8446db545..2f6954bbb3a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_03_connect_cli/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with CLI
-excerpt: Connect to your Public Cloud Databases for Caching using the Command Line Interface (CLI)
+title: Caching/Valkey - Connect with CLI
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Command Line Interface (CLI)
 updated: 2024-06-12
 ---
 
@@ -8,20 +8,20 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with a Command Line Interface (CLI).**
+**This guide explains how to connect to a Caching/Valkey service instance with a Command Line Interface (CLI).**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt);
 - A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account;
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 
 ## Concept
 
-A Caching service can be managed through multiple ways.<br>
+A Caching/Valkey service can be managed through multiple ways.<br>
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), also known as a Console or Terminal.
-To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching service remotely.<br>
+To interact correctly with the instance, we need to first install something called a client, in order to connect and control the Caching/Valkey service remotely.<br>
 It's a Client-Server interaction.
 
 ## Instructions
@@ -104,7 +104,7 @@ In case the user doesn't have the right privilege, you will get a NOPERM respons
 
 ## Go further
 
-[Caching capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+[Caching/Valkey capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 
 [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.de-de.md
index 0c061ebf5fc..d86fcc82551 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de)
 - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-asia.md
index efc5af92a6e..7b14addc769 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia)
 - A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-au.md
index 53f952b2093..09fe38d949f 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au)
 - A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ca.md
index 91c9dcfcdd5..33fcb2fdf6d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca)
 - A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-gb.md
index f9b78053cd9..1bc3584f0c7 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB)
 - A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ie.md
index dfa25b31b0e..56117201056 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie)
 - A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-sg.md
index 98cad94014f..30aa85af76f 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg)
 - A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-us.md
index 7cc4fc8201c..fd9ae2655c5 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we)
 - A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-es.md
index 29e821f955e..0d731216064 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es)
 - A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-us.md
index 70ef6cd20cc..93d5a02cb0e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws)
 - A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-ca.md
index a0c24ddb1d1..c01cc9fca09 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec PHP (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connectez-vous avec PHP (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc)
 - A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-fr.md
index 9d9d26849c8..9fe80f7169d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec PHP (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connectez-vous avec PHP (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr)
 - A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.it-it.md
index 82e27b4275c..5337fb1e3d0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it)
 - A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pl-pl.md
index 064e728b52e..f59662e91d0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl)
 - A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pt-pt.md
index 7701f9d5965..1988d1e1403 100644
--- a/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_04_connect_php/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with PHP
-excerpt: Connect to your Public Cloud Databases for Caching using the PHP programming language
+title: Caching/Valkey - Connect with PHP
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the PHP programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: PHP.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: PHP.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/php/hello-world).
 
@@ -16,20 +16,20 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt)
 - A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A PHP environment with a stable version and public network connectivity (Internet). This guide was made in PHP 7.4.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as PHP.
 PHP is used in almost 80% of the websites in the world, such as Facebook, Wikipedia or WordPress.
 Redis® has multiple PHP clients, allowing us to connect and manage an instance from code. Please follow the official [Redis® documentation for PHP clients](https://redis.io/clients#php){.external} to get the latest clients information.
 
-We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally code in PHP to perform a few example actions.
+We will need to set up our PHP environment with phpredis client, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally code in PHP to perform a few example actions.
 
 ## Instructions
 
@@ -87,7 +87,7 @@ Congratulations! Everything is working properly.
 ## Go further
 
 - [Redis® official tutorial: simple Twitter clone using PHP](https://redis.io/topics/twitter-clone)
-- [Caching - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [Caching/Valkey - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
 - [Configuring vRack for Public Cloud](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack)
 
 Visit our dedicated Discord channel: [https://discord.gg/ovhcloud](https://discord.gg/ovhcloud). Ask questions, provide feedback and interact directly with the team that builds our databases services.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.de-de.md
index b1bdca2200e..9eb731f703a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de)
 - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-asia.md
index 65780c366fa..6ba008cf19c 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia)
 - A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-au.md
index ddb3a35f778..ca1d15acb7d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au)
 - A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ca.md
index aace918389f..649c0ff9b1c 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca)
 - A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-gb.md
index b45e9f9ed54..74019ed1509 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB)
 - A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ie.md
index f4099df151c..aa2733b2f42 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie)
 - A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-sg.md
index 139115b97b2..9f6b5c39334 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg)
 - A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-us.md
index 88a996cb545..06c017aebcb 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we)
 - A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-es.md
index ac3280e5ece..b959a362d70 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es)
 - A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-us.md
index 14de8126f13..bdc9187dec4 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws)
 - A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-ca.md
index 4326f09139e..e3c552750f9 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec Python (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connectez-vous avec Python (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc)
 - A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-fr.md
index 6153e376d40..e616358508d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec Python (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connectez-vous avec Python (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr)
 - A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.it-it.md
index 9e2c74fe648..fe558f9bbff 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it)
 - A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pl-pl.md
index 523bfe0adf3..c5c6c79f1fe 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl)
 - A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pt-pt.md
index e88f317c8ce..259cb71a32b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_05_connect_python/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with Python
-excerpt: Connect to your Public Cloud Databases for Caching using the Python programming language
+title: Caching/Valkey - Connect with Python
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using the Python programming language
 updated: 2024-06-12
 ---
 
@@ -8,7 +8,7 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service instance with one of the world's most famous programming language: Python.**
+**This guide explains how to connect to a Caching/Valkey service instance with one of the world's most famous programming language: Python.**
 
 You can find an example on the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/redis/python/hello-world).
 
@@ -16,13 +16,13 @@ You can find an example on the [Github examples repository](https://github.com/o
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt)
 - A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A working Python environment.
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli).
 
 Another way is to interact directly using programming languages, such as Python.
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.de-de.md
index 2511f7da470..e30be1d5e3a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de)
-- A [Caching service project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-asia.md
index 3d8afc0a411..b61161bcb2a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia)
-- A [Caching service project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-au.md
index b26f98fb656..9a860b0235a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au)
-- A [Caching service project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ca.md
index 9937b395e17..860043d2fa6 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca)
-- A [Caching service project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-gb.md
index 00d6f03be98..d89040055e8 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB)
-- A [Caching service project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ie.md
index 383d810626e..2eaf658fbdf 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie)
-- A [Caching service project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-sg.md
index b6da272d66a..21ba59c1519 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg)
-- A [Caching service project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-us.md
index d485e1cec09..15157f76c19 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we)
-- A [Caching service project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-es.md
index 3a1fbc5c5b1..f3dfb224bd7 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es)
-- A [Caching service project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-us.md
index 9f0b4e0d523..633ab67a797 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws)
-- A [Caching service project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-ca.md
index 091c1cb52b5..15c248181b3 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec RedisInsight (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connectez-vous avec RedisInsight (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc)
-- A [Caching service project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-fr.md
index 5c20c7e068b..634c58fd626 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connectez-vous avec RedisInsight (EN)
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connectez-vous avec RedisInsight (EN)
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr)
-- A [Caching service project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.it-it.md
index 33dd86d2e1f..cd6907caabc 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it)
-- A [Caching service project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pl-pl.md
index 24b917269d9..58017dd2419 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl)
-- A [Caching service project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pt-pt.md
index 726bdc62a6f..d7622aed792 100644
--- a/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_06_connect_redisinsight/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Connect with RedisInsight
-excerpt: Connect to your Public Cloud Databases for Caching using RedisInsight
+title: Caching/Valkey - Connect with RedisInsight
+excerpt: Connect to your Public Cloud Databases for Caching/Valkey using RedisInsight
 updated: 2024-06-12
 ---
 
@@ -8,34 +8,34 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to connect to a Caching service with the free GUI: RedisInsight.**
+**This guide explains how to connect to a Caching/Valkey service with the free GUI: RedisInsight.**
 
 ## Requirements
 
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt)
-- A [Caching service project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-- [Configure your Caching service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
+- A [Caching/Valkey service project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- [Configure your Caching/Valkey service](/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) to accept incoming connections
 - A RedisInsight stable version installed and public network connectivity (Internet). This guide was made in RedisInsight 1.11.1
 
 ## Concept
 
-A Caching service can be managed through multiple ways.
+A Caching/Valkey service can be managed through multiple ways.
 One of the easiest, yet powerful, is to use a Command Line Interface (CLI), as shown in our guide: [Connect with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli) or by using programming languages, such as [PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php).
 
 Another way is to interact directly using the GUI: RedisInsight.
 
-In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching services to accept incoming connections, and finally configure RedisInsight.
+In order to do so, we will need to install RedisInsight, then configure our Public Cloud Databases for Caching/Valkey services to accept incoming connections, and finally configure RedisInsight.
 
 ## Instructions
 
 ### Installation
 
-To interact with your Caching service with RedisInsight you need to install it.
+To interact with your Caching/Valkey service with RedisInsight you need to install it.
 
 Please follow the official [RedisInsight](https://docs.redis.com/latest/ri/installing) to get the latest information.
 
-We are now ready to learn how to connect to our Caching service.
+We are now ready to learn how to connect to our Caching/Valkey service.
 
 ### Connect with RedisInsight
 
@@ -51,19 +51,19 @@ Once connected to the RedisInsight interface, click on the `I already have a dat
 
 ![Redis first screen](images/redis_06_connect_redisinsight-20220207114821477.png)
 
-Then on `Connect to a Caching service` :
+Then on `Connect to a Caching/Valkey service` :
 
-![Configure your Caching service](images/redis_06_connect_redisinsight-2022020711515517.png)
+![Configure your Caching/Valkey service](images/redis_06_connect_redisinsight-2022020711515517.png)
 
 Fill in the form with the previously collected credentials. Check the `Use TLS` check box and uncheck the `Verify TLS Certificate` check box. Then click on `ADD REDIS DATABASE` :
 
 ![Add Redis database](images/redis_06_connect_redisinsight-20220207120005204.png)
 
-Finally, select your Caching service:
+Finally, select your Caching/Valkey service:
 
 ![Dashboard](images/redis_06_connect_redisinsight-20220209095424435.png)
 
-Congratulations! You are now connected to your Caching instance!
+Congratulations! You are now connected to your Caching/Valkey instance!
 
 ![Result](images/redis_06_connect_redisinsight-20220209095533690.png)
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.de-de.md
index 2dfc491b89b..116d46fd8a0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.de-de.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-asia.md
index 96b28d4f7ec..5e3cc52613e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-asia.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-au.md
index 71483c1243f..7d05eadf5a9 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-au.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ca.md
index eb22cdac23b..8e6c34485a6 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ca.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-gb.md
index 9698cc71ff6..3d0a274aafe 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-gb.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ie.md
index 23148150edd..b9b3433bab8 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-ie.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-sg.md
index 415e03dffce..46a17856716 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-sg.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-us.md
index 3951e33f9f9..4064de458b0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.en-us.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-es.md
index f9b6495af88..e63ddb42001 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-es.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-us.md
index 0661dfcf621..3f8219871e2 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.es-us.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-ca.md
index 1908a888bc7..84cc8b9e036 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-ca.md
@@ -1,23 +1,23 @@
 ---
-title: "Caching - Gérer les ACL via l'API (EN)"
+title: "Caching/Valkey - Gérer les ACL via l'API (EN)"
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-fr.md
index fe37db0f6cf..9626f1cb6a1 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.fr-fr.md
@@ -1,23 +1,23 @@
 ---
-title: "Caching - Gérer les ACL Redis via l'API (EN)"
+title: "Caching/Valkey - Gérer les ACL Redis via l'API (EN)"
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.it-it.md
index d00c902625c..9170425fd55 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.it-it.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pl-pl.md
index 674c483627a..caa355b2131 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pl-pl.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pt-pt.md
index 2a32f63bdda..fc449ae1db1 100644
--- a/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_07_update_acls/guide.pt-pt.md
@@ -1,23 +1,23 @@
 ---
-title: Caching - Manage ACLs via API
+title: Caching/Valkey - Manage ACLs via API
 excerpt: Update users ACLs with the OVHcloud API
 updated: 2024-06-12
 ---
 
 ## Objective
 
-This page shows you how to update your Caching service user ACLs with the OVHcloud API.
+This page shows you how to update your Caching/Valkey service user ACLs with the OVHcloud API.
 
 ## Users and roles
 
-As explained on this page: [Caching Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
+As explained on this page: [Caching/Valkey Capabilities, Users & roles](/pages/public_cloud/public_cloud_databases/redis_01_capabilities#users-and-roles), the users' ACLs cannot be updated via the OVHcloud Control Panel.
 
 You must therefore use the [OVHcloud API](/pages/manage_and_operate/api/first-steps).
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account.
-- An up and running Public Cloud Database for Caching.
+- An up and running Public Cloud Database for Caching/Valkey.
 
 If you have never used the OVHcloud API before, then follow this tutorial: [First Steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
@@ -25,9 +25,9 @@ For this tutorial, we consider that you are logged on the relevant API (Europe:
 
 ## Instructions
 
-### Get your service, Caching cluster and user IDs
+### Get your service, Caching/Valkey cluster and user IDs
 
-You first need to identify the service, the Caching cluster and the user you want to apply the changes to.
+You first need to identify the service, the Caching/Valkey cluster and the user you want to apply the changes to.
 
 #### Get the desired service ID
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.de-de.md
index eae42fc1a2e..290ce77b0f8 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-asia.md
index be12b0dd2a3..f49838d3481 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-au.md
index 23fef09096b..8f064627520 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ca.md
index 06b5fff4d3d..b31485b3a87 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-gb.md
index 19eaf9c8aac..e6f597230a3 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ie.md
index c981624cbdc..9cf59635c94 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-sg.md
index ec711018a64..2d2f99383ae 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-us.md
index e0972fa003d..ba80673c4cc 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-es.md
index 8d8c7384af5..7cc3665d7e9 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-us.md
index 24ecce6b73f..b70074ef1d0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-ca.md
index 31b5b9fca4c..899fe1a1015 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configurez votre service Caching pour accepter les connexions entrantes (EN)
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configurez votre service Caching/Valkey pour accepter les connexions entrantes (EN)
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-fr.md
index 1f2115784c4..0f5e8380c75 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configurez votre service Caching pour accepter les connexions entrantes (EN)
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configurez votre service Caching/Valkey pour accepter les connexions entrantes (EN)
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.it-it.md
index 2c30de73a99..bf525c3bb4d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pl-pl.md
index 1338c51b7c2..3c02eb97250 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pt-pt.md
index 8be740efa98..da45cc78aa1 100644
--- a/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Configure your Caching service to accept incoming connections
-excerpt: Find out how to configure your Caching service to accept incoming connections
+title: Caching/Valkey - Configure your Caching/Valkey service to accept incoming connections
+excerpt: Find out how to configure your Caching/Valkey service to accept incoming connections
 updated: 2024-06-12
 ---
 
@@ -8,21 +8,21 @@ updated: 2024-06-12
 
 Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
 
-**This guide explains how to configure your Caching instance to accept incoming connections.**
+**This guide explains how to configure your Caching/Valkey instance to accept incoming connections.**
 
 ## Requirements
 
 - A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
 - Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt)
-- A Caching service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
+- A Caching/Valkey service running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
 
 ## Instructions
 
-### Configure your Caching instance to accept incoming connections
+### Configure your Caching/Valkey instance to accept incoming connections
 
-Before making a connection, we need to verify that our Caching instance is correctly configured.
+Before making a connection, we need to verify that our Caching/Valkey instance is correctly configured.
 
-Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching instance.
+Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Caching/Valkey instance.
 
 #### Step 1: Verify your user roles and password
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.de-de.md
index 2487d579e79..6ba3f6a4301 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.de-de.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-asia.md
index 2b2081ade2b..ca79253bd31 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-asia.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-au.md
index 085a4416347..1a3a07a825b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-au.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ca.md
index a4031742a18..85a35e24e63 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-gb.md
index 74bf8b69bb3..6309ad0ee2b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-gb.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ie.md
index 8052ab7d14d..9f153618120 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-ie.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-sg.md
index 2c32dfee331..0d40350f9df 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-sg.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-us.md
index ae8b50a567a..6b4f98f408d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.en-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-es.md
index 0ace3853b93..2a979c273cc 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-es.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-us.md
index 59e8af079dc..cf9ebd518b7 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.es-us.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-ca.md
index 05f105f3da5..c6097a51f0e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-ca.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Références des paramètres avancés (EN)
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Références des paramètres avancés (EN)
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-fr.md
index d147f6565df..cade7d694c4 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.fr-fr.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Références des paramètres avancés (EN)
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Références des paramètres avancés (EN)
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.it-it.md
index 2f131948e59..74451be2f86 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.it-it.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pl-pl.md
index faf94c473ae..e8b2fb69d3a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pl-pl.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pt-pt.md
index ee81217264c..1ec08cf1828 100644
--- a/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_09_advanced_parameters_references/guide.pt-pt.md
@@ -1,6 +1,6 @@
 ---
-title: Caching - Advanced parameters references
-excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases
+title: Caching/Valkey - Advanced parameters references
+excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases
 updated: 2024-06-12
 ---
 
@@ -29,7 +29,7 @@ updated: 2024-06-12
 
 ## Objective
 
-This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching according to your use cases.
+This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Caching/Valkey according to your use cases.
 
 ## Requirements
 
@@ -52,9 +52,9 @@ Please refer to this [guide](/pages/public_cloud/public_cloud_databases/database
 
 Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API.
 
-### Advanced parameters for Caching
+### Advanced parameters for Caching/Valkey
 
-Below you can find a summary of every configuration option available for Caching service:
+Below you can find a summary of every configuration option available for Caching/Valkey service:
 
 | | |
 |---|---|
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.de-de.md
index 3fc276a3cd5..5a91eeb72e9 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.de-de.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-asia.md
index 182c50ac205..69d9ea3b8da 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-asia.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-au.md
index 62b11af9566..adb98e9e5d0 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-au.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ca.md
index d6d480abae2..f3abf78150b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ca.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-gb.md
index 98e631985e9..3c5a3de0985 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-gb.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ie.md
index 245b9758c0c..88028f096d6 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-ie.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-sg.md
index db047b37591..4d6a0169ecc 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-sg.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-us.md
index 6f7b707461b..ed530eac21b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.en-us.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-es.md
index 4d4d10efbaf..805f0dc9228 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-es.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-us.md
index d6d03e01897..493e8cdcff8 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.es-us.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-ca.md
index f343d9466e5..cd4b257950e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-ca.md
@@ -1,13 +1,13 @@
 ---
-title: "Caching - Boostez votre CMS (à partir de l'exemple de WordPress) (EN)"
+title: "Caching/Valkey - Boostez votre CMS (à partir de l'exemple de WordPress) (EN)"
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with the power of Caching
+excerpt: Boost the performances of your WordPress CMS with the power of Caching/Valkey
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-fr.md
index bfb5ac9a5de..f390e9baabb 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.fr-fr.md
@@ -1,13 +1,13 @@
 ---
-title: "Caching - Boostez votre CMS (à partir de l'exemple de WordPress) (EN)"
+title: "Caching/Valkey - Boostez votre CMS (à partir de l'exemple de WordPress) (EN)"
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with the power of Caching
+excerpt: Boost the performances of your WordPress CMS with the power of Caching/Valkey
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.it-it.md
index aa1634c91f5..b1bef280d60 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.it-it.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pl-pl.md
index 1e3963842a5..a6fcd1ebc1a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pl-pl.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pt-pt.md
index 6d97eb9ba9c..46302d33cad 100644
--- a/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_tuto_01_wordpress/guide.pt-pt.md
@@ -1,13 +1,13 @@
 ---
-title: Caching - Tutorial - Boost your CMS (from the example of WordPress)
+title: Caching/Valkey - Tutorial - Boost your CMS (from the example of WordPress)
 keywords: wordpress, redis, dbaas, cms
-excerpt: Boost the performances of your WordPress CMS with a Caching service
+excerpt: Boost the performances of your WordPress CMS with a Caching/Valkey service
 updated: 2024-06-12
 ---
 
 ## Objective
 
-Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching service! In this tutorial, we will set up a Caching service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
+Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to speed up page load times and SQL queries using a Caching/Valkey service! In this tutorial, we will set up a Caching/Valkey service for your CMS data. All users, even administrators and especially visitors, will directly benefit from a better performance of the website.
 
 > [!warning]
 >
@@ -18,7 +18,7 @@ Do you have a CMS website or blog, perhaps powered by WordPress? Learn how to sp
 
 ### CMS platform
 
-For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching and a WordPress plugin for Redis®.
+For this tutorial we propose to use the WordPress CMS, running on Linux Ubuntu with MySQL as the main database. To get the object cache we will use a Public Cloud Database for Caching/Valkey and a WordPress plugin for Redis®.
 
 > [!warning]
 >This tutorial will show you how to use one or more OVHcloud solutions with external tools, and will describe the actions to be carried out in a specific context. Please remember to adapt these actions to fit your situation.
@@ -35,7 +35,7 @@ This tutorial requires:
 - A running WordPress
 - A WordPress administrator account to install a plugin
 - A [PHP Redis® client](https://redis.io/clients#php){.external} supported by the plugin
-- An OVHcloud Public Cloud database for Caching
+- An OVHcloud Public Cloud database for Caching/Valkey
 
 ## Instructions
 
@@ -60,7 +60,7 @@ For the next steps, let's consider that you have an up and running WordPress sys
 
 As WordPress is based on PHP, we will need a PHP Redis® client. We propose to use one of the main recommended [PHP Redis® clients](https://redis.io/clients#php){.external}: PhpRedis.
 
-As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching, we have to use the v5.3.x release of PhpRedis or above.
+As TLS is required to secure the connection to the OVHcloud Public Cloud database for Caching/Valkey, we have to use the v5.3.x release of PhpRedis or above.
 
 Please check that PhpRedis is installed, with a compliant release:
 
@@ -81,19 +81,19 @@ sudo systemctl restart apache2
 
 ### Redis® WordPress plugin
 
-There are multiple Redis® plugins that could be used to integrate to a Caching service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
+There are multiple Redis® plugins that could be used to integrate to a Caching/Valkey service. You can search them directly in the Plugin menu. For this tutorial we decided to use the most popular one: Redis Object Cache. Click on the Install Now button:
 
 ![Search Redis Plugin](images/Redis_plugin_list.png){.thumbnail}
 
 You can get more information related to this WordPress plugin at the official [WordPress plugin documentation - Redis Object Cache](https://wordpress.org/plugins/redis-cache/){.external}.
 
-### Configure WordPress to connect to the Caching service
+### Configure WordPress to connect to the Caching/Valkey service
 
 #### Modify wp-config.php
 
-Before activating the Redis Object Cache plugin, it is required to configure the Caching service connection parameters.
-By default, this plugin looks for a Caching service hosted in the same server as your WordPress.
-It's not our case scenario here, since the Caching service is hosted in OVhcloud Public Cloud Databases.
+Before activating the Redis Object Cache plugin, it is required to configure the Caching/Valkey service connection parameters.
+By default, this plugin looks for a Caching/Valkey service hosted in the same server as your WordPress.
+It's not our case scenario here, since the Caching/Valkey service is hosted in OVhcloud Public Cloud Databases.
 
 We will follow the official plugin wiki to define the remote server: <https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options>.
 This has to be done in the WordPress configuration file (**wp-config.php** located in /var/www/wordpress/ in our example) and add the following lines:
@@ -108,11 +108,11 @@ define('WP_CACHE_KEY_SALT', 'myOVHcloudRedis_' );
 ```
 #### Modify the host
 
-The salt key is not mandatory, even more if you have only one application using a Caching service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
+The salt key is not mandatory, even more if you have only one application using a Caching/Valkey service, but if you have several WordPress sites, it will be useful to determine **what-pushes-what**.
 
 #### Check that authorised IPs are updated
 
-Do not forget to add the WordPress IP address to the authorised IPs list of the Caching service.
+Do not forget to add the WordPress IP address to the authorised IPs list of the Caching/Valkey service.
 
 ![Add Authorised IP](images/Redis_add_ip_whitelist.png){.thumbnail}
 
@@ -132,7 +132,7 @@ If you run into any problems enabling the Redis Object Cache plugin, start your
 
 #### Additional parameters
 
-Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching service usage:
+Please find below more documentation on the additional available parameters that you might want to use to optimise your Caching/Valkey service usage:
 
 - [Redis Object Cache connection parameters](https://github.com/rhubarbgroup/redis-cache/wiki/Connection-Parameters){.external}
 - [Redis Object Cache configuration options](https://github.com/rhubarbgroup/redis-cache/wiki/Configuration-Options){.external}
@@ -141,7 +141,7 @@ Please find below more documentation on the additional available parameters that
 
 #### Validate that cache is populated
 
-If you can use a CLI to query the Caching service, you can check that information populated to it after browsing some WordPress pages.
+If you can use a CLI to query the Caching/Valkey service, you can check that information populated to it after browsing some WordPress pages.
 
 In our case:
 ```bash
@@ -176,17 +176,17 @@ With the cache, there is a total of 2 database queries taking 0.0043s:
 
 ![Performance measure with cache](images/Perf_with_cache.png){.thumbnail}
 
-#### Two main benefits using a Caching service
+#### Two main benefits using a Caching/Valkey service
 
-As seen, using a Caching service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
+As seen, using a Caching/Valkey service you will see a performance gain for your CMS. It will be even more efficient as soon as your site stores more and larger data. You will also directly benefit from the fact that the MySQL server will be less stressed with the load/concurrent accesses, which will offer the opportunity to handle more and more users.
 
 ## Go further
 
 - [OVHcloud documentation on managed Public Cloud Databases](/products/public-cloud-databases)
-- [Caching capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
-- [How to connect to a Caching service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
-- [How to connect to a Caching service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
-- [Caching Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
+- [Caching/Valkey capabilities](/pages/public_cloud/public_cloud_databases/redis_01_capabilities)
+- [How to connect to a Caching/Valkey service with CLI](/pages/public_cloud/public_cloud_databases/redis_03_connect_cli)
+- [How to connect to a Caching/Valkey service with PHP](/pages/public_cloud/public_cloud_databases/redis_04_connect_php)
+- [Caching/Valkey Roadmap](https://github.com/orgs/ovh/projects/16/views/5?card_filter_query=label%3Aredis)
 
 Join our community of users on <https://community.ovh.com/en/>.
 

From 55d1bc3fb69393150d79580332407847ccdd0e46 Mon Sep 17 00:00:00 2001
From: Valentin Lacour <valentin.lacour.ext@corp.ovh.com>
Date: Wed, 9 Apr 2025 13:49:09 +0200
Subject: [PATCH 2/3] update

---
 .../information_02_lifecycle_policy/guide.de-de.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-asia.md         | 4 +++-
 .../information_02_lifecycle_policy/guide.en-au.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-ca.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-gb.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-ie.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-sg.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.en-us.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.es-es.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.es-us.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.fr-ca.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.fr-fr.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.it-it.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.pl-pl.md           | 4 +++-
 .../information_02_lifecycle_policy/guide.pt-pt.md           | 4 +++-
 .../redis_01_capabilities/guide.de-de.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-asia.md                   | 5 +++--
 .../redis_01_capabilities/guide.en-au.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-ca.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-gb.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-ie.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-sg.md                     | 5 +++--
 .../redis_01_capabilities/guide.en-us.md                     | 5 +++--
 .../redis_01_capabilities/guide.es-es.md                     | 5 +++--
 .../redis_01_capabilities/guide.es-us.md                     | 5 +++--
 .../redis_01_capabilities/guide.fr-ca.md                     | 5 +++--
 .../redis_01_capabilities/guide.fr-fr.md                     | 5 +++--
 .../redis_01_capabilities/guide.it-it.md                     | 5 +++--
 .../redis_01_capabilities/guide.pl-pl.md                     | 5 +++--
 .../redis_01_capabilities/guide.pt-pt.md                     | 5 +++--
 30 files changed, 90 insertions(+), 45 deletions(-)

diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.de-de.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-asia.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-au.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ca.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
index 83867daef22..162478f52bd 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-gb.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-ie.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-sg.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.en-us.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-es.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.es-us.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
index eb064e3dec1..368a3aabbe2 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-ca.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
index eb064e3dec1..368a3aabbe2 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.fr-fr.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.it-it.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pl-pl.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
index f6199d4662d..fcc900bbd3b 100644
--- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/guide.pt-pt.md
@@ -79,7 +79,9 @@ PostgreSQL EOL will coincide with the official PostgreSQL versioning policy : <h
 
 ### Caching/Valkey
 
-Caching/Valkey EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+Caching EOL will coincide with the official Redis® Community Releases policy : <https://redis.io/topics/releases>
+
+Valkey EOL will coincide with the official Valkey Community Releases policy : <https://valkey.io/topics/releases>
 
 ## Go further
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
index e723b6b296c..2bc74b474d5 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
index 5edad439f72..9494af090e9 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
index f485b07ce62..a537510018d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
index 36627f9c649..d6ddbdc41a7 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
index 465c9878aac..33771b76c5e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
index e7ea446efc7..f1211351b9b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
index d427b871945..180f4cee6e8 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
index 121039e3670..e73154823c1 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
index d9752d0c3a5..8b017411f89 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
index 23d29a2964c..6e454274499 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
index a8762d07465..2993cc2ae65 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
index 1632ece9ccc..a81babb6df4 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
index 5fba1350692..d8e638a2428 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
index 9f7b19c05ad..0ea7981e0e3 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
index 619ccf03dde..9677ffade1e 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
@@ -28,9 +28,10 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 
 ### Caching/Valkey versions
 
-The Public Cloud Databases offer uses the following Redis® open source versions:
+The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
-- Redis® open source 7.0
+- Redis® open source 7.2
+- Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
 

From 302e4c3b20417143fb9e64c0d59f452c066afb19 Mon Sep 17 00:00:00 2001
From: Valentin Lacour <valentin.lacour.ext@corp.ovh.com>
Date: Wed, 9 Apr 2025 14:33:10 +0200
Subject: [PATCH 3/3] update valkey version

---
 .../public_cloud_databases/redis_01_capabilities/guide.de-de.md  | 1 +
 .../redis_01_capabilities/guide.en-asia.md                       | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-au.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-ca.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-gb.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-ie.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-sg.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.en-us.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.es-es.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.es-us.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.fr-ca.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.fr-fr.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.it-it.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.pl-pl.md  | 1 +
 .../public_cloud_databases/redis_01_capabilities/guide.pt-pt.md  | 1 +
 15 files changed, 15 insertions(+)

diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
index 2bc74b474d5..e41a4355990 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.de-de.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
index 9494af090e9..1ff625e25c3 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-asia.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
index a537510018d..fbe3a202479 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-au.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
index d6ddbdc41a7..62401492dcb 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ca.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
index 33771b76c5e..f3bba0a5e90 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-gb.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
index f1211351b9b..3f5ff9ad343 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-ie.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
index 180f4cee6e8..c185e3efa8b 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-sg.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
index e73154823c1..1a2b0cb3f0a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.en-us.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
index 8b017411f89..cb2f947b303 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-es.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
index 6e454274499..ccd42b07970 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.es-us.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
index 2993cc2ae65..e2f27cc566a 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-ca.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
index a81babb6df4..b821bff92a2 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.fr-fr.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
index d8e638a2428..64b491e0b54 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.it-it.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
index 0ea7981e0e3..f3f647b7b12 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pl-pl.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>
diff --git a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
index 9677ffade1e..82e1c9d2f5d 100644
--- a/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/redis_01_capabilities/guide.pt-pt.md
@@ -31,6 +31,7 @@ Database nodes have to be in the same region. Multi-AZ is currently not supporte
 The Public Cloud Databases offer uses the following Redis® open source and Valkey versions:
 
 - Redis® open source 7.2
+- Valkey 7.2
 - Valkey 8.0
 
 Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. Additionally, you can follow Redis® release cycle on their official page: <https://redis.io/topics/releases>