diff --git a/docs/platform/concepts/maintenance-window.md b/docs/platform/concepts/maintenance-window.md
index 9d6fa5626..d0167cde0 100644
--- a/docs/platform/concepts/maintenance-window.md
+++ b/docs/platform/concepts/maintenance-window.md
@@ -1,5 +1,6 @@
 ---
-title: Service maintenance, updates and upgrades
+title: Service maintenance, updates, and upgrades
+sidebar_label: Service maintenance
 ---
 
 import ConsoleLabel from "@site/src/components/ConsoleIcons"
@@ -33,18 +34,17 @@ Major service upgrades are triggered manually. A manually triggered upgrade star
 See [Upgrade PostgreSQL to a major version][pg].
 :::
 
-### MySQL, PostgreSQL and Caching updates
+### MySQL, PostgreSQL and Valkey updates
 
-For **MySQL®**, **PostgreSQL®** and **Caching**, the maintenance
-process usually lasts around several seconds. The downtime comes from old
-master stopping itself in a controlled manner and new master executing
-promotion sequence after this.
+For **MySQL®**, **PostgreSQL®** and **Valkey**, the maintenance process should take no
+more than 15 seconds. The downtime comes from the old primary stopping itself in a
+controlled manner and the new primary executing a promotion sequence after this.
 
 Once the promotion is complete the old
-master node starts forwarding requests to the new master node so the
+primary node starts forwarding requests to the new primary node so the
 service is accessible before DNS updates are propagated, though clients
-that end up reconnecting to the old master node will see additional
-disconnection once the old master is permanently retired.
+that end up reconnecting to the old primary node will see additional
+disconnection once the old primary is permanently retired.
 
 ### Apache Kafka and OpenSearch updates