diff --git a/stable/joomla/Chart.yaml b/stable/joomla/Chart.yaml
index 7b306cf45d..e7ad566184 100644
--- a/stable/joomla/Chart.yaml
+++ b/stable/joomla/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v1
 name: joomla
-version: 6.1.9
+version: 6.1.10
 appVersion: 3.9.12
 description: PHP content management system (CMS) for publishing web content
 keywords:
diff --git a/stable/joomla/README.md b/stable/joomla/README.md
index b0a5f8df16..5366057b09 100644
--- a/stable/joomla/README.md
+++ b/stable/joomla/README.md
@@ -31,7 +31,7 @@ To install the chart with the release name `my-release`:
 $ helm install --name my-release stable/joomla
 ```
 
-The command deploys Joomla! on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
+The command deploys Joomla! on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
 
 > **Tip**: List all releases using `helm list`
 
@@ -45,7 +45,7 @@ $ helm delete my-release
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
 
-## Configuration
+## Parameters
 
 The following table lists the configurable parameters of the Joomla! chart and their default values.
 
@@ -152,6 +152,8 @@ $ helm install --name my-release -f values.yaml stable/joomla
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
 
+## Configuration and installation details
+
 ### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
 
 It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
@@ -163,7 +165,7 @@ Bitnami will release a new chart updating its containers if a new version of the
 The [Bitnami Joomla!](https://github.com/bitnami/bitnami-docker-joomla) image stores the Joomla! data and configurations at the `/bitnami/joomla` path of the container.
 
 Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
-See the [Configuration](#configuration) section to configure the PVC or to disable persistence.
+See the [Parameters](#parameters) section to configure the PVC or to disable persistence.
 
 ## Upgrading