Update HA and PVC incompatibility to make it more obvious (#503)

* Update HA and PVC incompatibility to make it more obvious

* small edits for linter

---------

Co-authored-by: Joan E <[email protected]>

Author: deniseschannon

platform/configure/advanced/audit.mdx

@@ -1,5 +1,5 @@
 ---
-title: Enabling Audit Logging
+title: Enable Audit Logging
 sidebar_label: Enable Audit Logging
 sidebar_position: 2
 description: Learn how to enable and configure audit logging to track activities in the platform, including management instance changes and cluster operations.
@@ -65,7 +65,7 @@ The platform provides audit levels, which are preconfigured audit policies for t
 For all of these levels certain internal read-only APIs are not logged since those might pollute the log and drastically increase log size. To log these, create a custom audit policy as described below.
 :::
 
-Configure the audit level through the platform config, which can be modified either through the platform UI or helm:
+Configure the audit level through the platform config, which can be modified either through the platform UI or Helm:
 
 <Tabs
   defaultValue="ui"
@@ -113,7 +113,11 @@ Below you can find a complete policy reference:
 
 ## Persisting audit logs
 
-There are two ways to persist platform audit logs: deploying the platform with a persistent volume claim (PVC) or connecting the platform to a persistent database. The PVC approach does not work for HA mode for the platform.
+There are two ways to persist platform audit logs: deploying the platform with a persistent volume claim (PVC) or connecting the platform to a persistent database. 
+
+:::info HA only supported with persistent database
+If you are running the platform in high availability (HA mode), the only way to persist audit logs is to use a persistent database. The PVC approach does not work.
+:::
 
 ### Deploy the platform with a PVC to save audit logs
 
@@ -126,7 +130,7 @@ audit:
     # size: 30Gi
 ```
 
-Apply the values via helm:
+Apply the values using Helm:
 
 ```bash title="Apply helm values"
 helm upgrade vcluster-platform vcluster-platform -n vcluster-platform --version 4.0.0-alpha.12 \
@@ -166,7 +170,7 @@ audit:
 
 To easily export the audit events to third party systems, enable the audit log
 sidecar that prints all the audit events onto stdout in a separate container which can then be easily watched and exported.
-Enabling the sidecar is only possible through helm values.
+Enabling the sidecar is only possible through Helm values.
 
 Create a `values.yaml` with the following contents: