DOCS apply validation suggestions

diff --git a/server/sonar-docs/src/pages/instance-administration/monitoring.md b/server/sonar-docs/src/pages/instance-administration/monitoring.md
index e072ce1f258a0d9b77811f3f882519e54c64d91b..1bcd48bd051a578bc30567f200707a89277db3e8 100644 (file)
--- a/server/sonar-docs/src/pages/instance-administration/monitoring.md
+++ b/server/sonar-docs/src/pages/instance-administration/monitoring.md
@@ -132,3 +132,6 @@ admin  adminpassword
 ```
 
 Note: on `jmxremote.password`, you should apply `chmod 600` or `400` for security reasons.
+
+## Kubernetes Monitoring
+You can monitor your SonarQube instance using SonarQube's native integration with Prometheus. For more information see the **Monitoring** section of the [Deploy SonarQube on Kubernetes](/setup/sonarqube-on-kubernetes/) page if you're using Community, Developer, or Enterprise Edition. See the [Deploy a SonarQube Cluster on Kubernetes](/setup/sonarqube-cluster-on-kubernetes/) if you're using Data Center Edition.

diff --git a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
index 1664fb227810eb4b3c26f40128c6681eb3fdec9c..c55162658f1ad5a8ffbc66893bdeb31585afe53e 100644 (file)
--- a/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
+++ b/server/sonar-docs/src/pages/setup/sonarqube-cluster-on-kubernetes.md
@@ -96,8 +96,8 @@ Monitoring through this endpoint requires authentication. You can access the end
 - **`X-Sonar-Passcode: xxxxx` header:** You can use `X-Sonar-passcode` during database upgrade and when SonarQube is fully operational. Define `X-Sonar-passcode` in the `sonar.properties` file using the `sonar.web.systemPasscode property`.
 - **username:password and JWT token:** When SonarQube is fully operational, system admins logged in with local or delegated authentication can access the endpoint. 
 
-####**JMX Exporter**
-You can also expose at the JMX metrics to Prometheus with the help of the Prometheus JMX exporter.
+#### **JMX Exporter**
+You can also expose the JMX metrics to Prometheus with the help of the Prometheus JMX exporter.
 
 To use this option, set the following values in your `values.yaml` file:
 

diff --git a/server/sonar-docs/src/pages/setup/sonarqube-on-kubernetes.md b/server/sonar-docs/src/pages/setup/sonarqube-on-kubernetes.md
index 87b0f1ed293b45cfe720d0f5ca81a20cccf805d8..cdc4ff2e4ae594becd7c18581488e69ae3ed5295 100644 (file)
--- a/server/sonar-docs/src/pages/setup/sonarqube-on-kubernetes.md
+++ b/server/sonar-docs/src/pages/setup/sonarqube-on-kubernetes.md
@@ -217,7 +217,7 @@ Monitoring through this endpoint requires authentication. You can access the end
 - **`X-Sonar-Passcode: xxxxx` header:** You can use `X-Sonar-passcode` during database upgrade and when SonarQube is fully operational. Define `X-Sonar-passcode` in the `sonar.properties` file using the `sonar.web.systemPasscode property`.
 - **username:password and JWT token:** When SonarQube is fully operational, system admins logged in with local or delegated authentication can access the endpoint. 
 
-####**JMX Exporter**
+#### **JMX Exporter**
 You can also expose the JMX metrics to Prometheus using the Prometheus JMX exporter.
 
 To use this option, set the following values in your `values.yaml` file: