Intro section

docs/HA.md

@@ -13,4 +13,6 @@ Whenever the primary changes, either by the user or by the operator, both the `<
 
 The primary may be manually changed by the user at any point by updating the `spec.[replication|galera].primary.podIndex` field. Alternatively,  automatic primary failover can be enabled by setting `spec.[replication|galera].primary.automaticFailover`, which will make the operator to switch primary whenever the primary `Pod` goes down.
 
-Although using the Kubernetes services for addressing the primary and secondary works, the most highly available setup we can offer relies on [MaxScale](https://mariadb.com/docs/server/products/mariadb-maxscale/), our advanced database proxy. Please take a look at the [MaxScale docs](./MAXSCALE.md).
+## MaxScale
+
+While Kubernetes services can be utilized to dynamically address primary and secondary instances, the most robust high availability configuration we recommend relies on [MaxScale](https://mariadb.com/docs/server/products/mariadb-maxscale/). Please refer to [MaxScale docs](./MAXSCALE.md) for further details.

docs/MAXSCALE.md

@@ -3,9 +3,13 @@
 > [!WARNING]  
 > This documentation applies to `mariadb-operator` version >= v0.0.25
 
-## MaxScale docs
+MaxScale is a sophisticated database proxy, router, and load balancer designed specifically for MariaDB. It provides a range of features that ensure optimal high availability:
+- Query based routing: Transparently route write queries to the primary nodes and read queries to the replica nodes.
+- Connection based routing: Load balance connection between multiple servers.
+- Automatic primary failover based on MariaDB internals.
+- Replay pending transactions when a server goes down.
 
-https://mariadb.com/kb/en/maxscale/
+To better understand what MaxScale is capable of you may check the [product page](https://mariadb.com/docs/server/products/mariadb-maxscale/) and the [documentation](https://mariadb.com/kb/en/maxscale/). 
 
 ## MaxScale resources