From ee9efc289d0b9e8c62204ca0f5105cd2e5e22dd6 Mon Sep 17 00:00:00 2001
From: TasdidurRahman <tasdid@appscode.com>
Date: Fri, 2 Dec 2022 12:46:06 +0600
Subject: [PATCH] change title name

Signed-off-by: TasdidurRahman <tasdid@appscode.com>
---
 .../proxysql/concepts/declarativeConfiguration/index.md  | 9 +++++----
 docs/guides/proxysql/quickstart/xtradbext/index.md       | 4 ++--
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/docs/guides/proxysql/concepts/declarativeConfiguration/index.md b/docs/guides/proxysql/concepts/declarativeConfiguration/index.md
index a4792017c2..48b4df2298 100644
--- a/docs/guides/proxysql/concepts/declarativeConfiguration/index.md
+++ b/docs/guides/proxysql/concepts/declarativeConfiguration/index.md
@@ -22,11 +22,12 @@ With kubedb proxysql we have eased this process with declarative yaml. We have s
 
 ## How it works 
 
-User will provide the configuration under the `.spec.initConfig` section of the proxysql yaml. The operator parses the yaml and creates a configuration file. A secret is then created, holding that configuration file inside. Each time a new pod is created it is created with the configuration file inside that secret. 
+User will provide the configuration under the `.spec.initConfig` section of the proxysql yaml. The operator parses the yaml and creates a configuration file. A secret is then created, holding that configuration file inside. Each time a new pod is created it is created with the configuration file inside that secret.
 
-<p align="center">
-<img alt="ProxySQL Declarative Configuration"  src="/docs/guides/proxysql/concepts/declarativeConfiguration/images/configuration.png">
-</p>
+<figure align="center">
+  <img alt="ProxySQL Declarative Configuration" src="/docs/guides/proxysql/concepts/declarativeConfiguration/images/configuration.png">
+<figcaption align="center">Fig: ProxySQL Configuration Secret Lifecycle</figcaption>
+</figure>
 
 At any time the user might need to change the configuration. To serve that purpose we have introduced ProxySQLOpsRequest. When an ops-request is being created the enterprise operator updates the configuration secret and applies the changes to the proxysql cluster nodes. This is how the the configuration secret remains as a source of truth for the ProxySQL CRO and any changes are made in a declarative way. 
 
diff --git a/docs/guides/proxysql/quickstart/xtradbext/index.md b/docs/guides/proxysql/quickstart/xtradbext/index.md
index 5430cbf915..b564fcbc9a 100644
--- a/docs/guides/proxysql/quickstart/xtradbext/index.md
+++ b/docs/guides/proxysql/quickstart/xtradbext/index.md
@@ -3,9 +3,9 @@ title: Proxy Load To Percona XtraDB Galera cluster With KubeDB Provisioned Proxy
 menu:
   docs_{{ .version }}:
     identifier: guides-proxysql-quickstart-external
-    name: External XtraDB Group Replication Backend
+    name: External XtraDB Galera Cluster Backend
     parent: guides-proxysql-quickstart
-    weight: 20
+    weight: 15
 menu_name: docs_{{ .version }}
 ---