Make vale happy

Author: Kidswiss

docs/modules/ROOT/pages/adr/0049-managed-openbao.adoc

@@ -221,8 +221,10 @@ data:
   ROOT_TOKEN: <base64-encoded-root-token>
 ```
 
+pass:[<!-- vale off -->]
 **Auto-unseal**
 
+
 Auto unseal allows OpenBao to unseal automatically without manual intervention using an external key management system. This is crucial for automated recovery and reduces operational burden.
 
 By default OpenBao instances will be configured to use a central, internal VSHN managed Vault or OpenBao to auto-unseal.
@@ -242,6 +244,8 @@ If no auto-unseal provider is configured, manual unsealing using the unseal keys
 
 Example AWS KMS auto-unseal secret:
 
+pass:[<!-- vale on -->]
+
 ```yaml
 apiVersion: v1
 kind: Secret
@@ -288,12 +292,13 @@ Key Components::
 4. **Monitoring**: Custom SLI exporter and Prometheus integration
 
 Security Model::
-
+pass:[<!-- vale off -->]
 - TLS encryption for all communications
 - RBAC policies managed through OpenBao
 - Audit logging to persistent storage
 - Auto-unseal configuration for OpenBao bootstrap
 
+pass:[<!-- vale on -->]
 == Consequences
 
 Positive::
@@ -318,7 +323,10 @@ Operational Impact::
 - Need for OpenBao and Raft consensus expertise in operations team
 - Integration testing with existing AppCat services
 - TLS certificate lifecycle management (renewal, rotation)
+pass:[<!-- vale off -->]
 - Auto-unseal configuration and cluster bootstrap management
+
+pass:[<!-- vale on -->]
 - Raft cluster health monitoring and node management
 - Audit log management and compliance reporting
 - ServiceMonitor configuration for Prometheus integration