review2

Signed-off-by: Bonusree <[email protected]>

Author: Bonusree

docs/guides/mariadb/restart/restart.md

@@ -84,9 +84,9 @@ spec:
 - The `spec.apply` field determines whether the operation should always be applied (Always) or only when there are changes (IfReady).
 
 
-> Note: The method of restarting the standalone & cluster mode db is exactly same as above. All you need, is to specify the corresponding Postgres name in `spec.databaseRef.name` section.
+> Note: The method of restarting the standalone & cluster mode db is exactly same as above. All you need, is to specify the corresponding MairiDB name in `spec.databaseRef.name` section.
 
-Let's create the `PostgresOpsRequest` CR we have shown above,
+Let's create the `MariaDBOpsRequest` CR we have shown above,
 
 
 ```bash

docs/guides/percona-xtradb/failover/_index.md

@@ -1,11 +1,10 @@
 ---
-title: PerconaXtraDB failover
+title: PerconaXtraDB Failover
 menu:
   docs_{{ .version }}:
-    identifier: guides-perconaxtradb-failover
+    identifier: guides-perconaxtradb-Failover
     name: Failover and Disaster Recovery
     parent: guides-perconaxtradb
     weight: 46
 menu_name: docs_{{ .version }}
-section_menu_id: guides
----
+---

docs/guides/percona-xtradb/failover/overview.md

@@ -1,11 +1,12 @@
 ---
-title: PerconaXtraDB Failover and DR Scenarios
+title: PerconaXtraDB Failover Overview
+description: PerconaXtraDB Failover Overview
 menu:
-docs_{{ .version }}:
-identifier: guides-perconaxtradb-failure-and-disaster-recovery-overview
-name: Overview
-parent: guides-perconaxtradb-failover
-weight: 20
+  docs_{{ .version }}:
+    identifier: guides-perconaxtradb-Failover-overview
+    name: Overview
+    parent: guides-perconaxtradb-Failover
+    weight: 10
 menu_name: docs_{{ .version }}
 section_menu_id: guides
 ---

docs/guides/percona-xtradb/restart/index.md

@@ -1,15 +1,14 @@
 ---
-title: PerconaXtraDB Restart
+title: Restart PerconaXtraDB
 menu:
   docs_{{ .version }}:
-    identifier: guides-perconaxtradb-restart
+    identifier: guides-perconaxtradb-Restart
     name: Restart
     parent: guides-perconaxtradb
     weight: 47
 menu_name: docs_{{ .version }}
 section_menu_id: guides
 ---
-
 > New to KubeDB? Please start [here](/docs/README.md).
 
 # Restart PerconaXtraDB

docs/guides/proxysql/restart/index.md

@@ -127,11 +127,7 @@ spec:
 - `spec.type` specifies the type of operation (Restart in this case).
 
 - `spec.proxyRef` references the ProxySQL database. The OpsRequest must be created in the same namespace as the database.
-
-- `spec.timeout` the maximum time the operator will wait for the operation to finish before marking it as failed.
-
-- `spec.apply` determines whether to always apply the operation (Always) or only if there are changes (IfReady).
-
+> For details on the fields of ProxySQLOpsRequest, please visit to the [ProxySQLOpsRequest API reference](/docs/guides/proxysql/concepts/opsrequest/index.md)
 
 Let's create the `ProxySQLOpsRequest` CR we have shown above,
 
@@ -260,22 +256,7 @@ status:
   phase: Successful
 
 ```
-**Verify Data Persistence**
 
-After the restart, reconnect to the database and verify that the previously created database still exists:
-
-```bash
-$ kubectl exec -it -n demo mysql-proxy-0 -- bash
-
-proxysql@mysql-proxy-0:/$  mysql -uadmin -padmin -h127.0.0.1 -P6032 --prompt="ProxySQLAdmin > " 
-Welcome to the MariaDB monitor.  Commands end with ; or \g.
-Your MySQL connection id is 120
-Server version: 8.0.27 (ProxySQL Admin Module)
-
-Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
-
-Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
-```
 ## Cleaning up
 
 To clean up the Kubernetes resources created by this tutorial, run:
@@ -290,5 +271,5 @@ kubectl delete ns demo
 ## Next Steps
 
 - Detail concepts of [ProxySQL object](/docs/guides/proxysql/concepts/proxysql/index.md).
-- Detail concepts of [ProxySQL object](/docs/guides/proxysql/concepts/opsrequest/index.md).
+- Detail concepts of [ProxySQLOpsRequest object](/docs/guides/proxysql/concepts/opsrequest/index.md).
 - Want to hack on KubeDB? Check our [contribution guidelines](/docs/CONTRIBUTING.md)..

docs/guides/redis/restart/_index.md

@@ -1,20 +1,20 @@
 ---
-title: Restart Redis Overview
+title: Restart Redis 
 menu:
   docs_{{ .version }}:
-    identifier: rd-restart-overview
-    name: Restart Redis
-    parent: rd-restart
-    weight: 10
+    identifier: rd-restart-redis
+    name: Restart 
+    parent: rd-redis-guides
+    weight: 50
 menu_name: docs_{{ .version }}
 section_menu_id: guides
 ---
 
 > New to KubeDB? Please start [here](/docs/README.md).
 
-# Restart Redis
+# Overview
 
-KubeDB supports restarting a Redis database via a `RedisOpsRequest`. Restarting is useful if some pods are stuck in an unexpected state or are not functioning correctly. This tutorial will guide you through the process of restarting a Redis cluster using KubeDB.
+KubeDB supports restarting a Redis/Valkey database via a `RedisOpsRequest`. Restarting is useful if some pods are stuck in an unexpected state or are not functioning correctly. This tutorial will guide you through the process of restarting a Redis cluster using KubeDB.
 
 ## Before You Begin