Vault Audit Logs: correct anchor link and replication note (#1466)

* Correct anchor link for exempted audit log endpoints
* Note on replication
* Apply suggestion from @schavis

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

Author: nphilbrook

content/vault/v1.20.x/content/docs/audit/index.mdx

@@ -6,7 +6,7 @@ description: Audit devices are mountable devices that log requests and responses
 
 # Audit logging
 
-With a small set of [exceptions](#excepted-api-endpoints), Vault audit devices record all API requests and responses in detail. An audit device can be a [file](/vault/docs/audit/file), a [syslog server](/vault/docs/audit/syslog), or a [socket](/vault/docs/audit/socket).
+With a small set of [exceptions](#exempted-api-endpoints), Vault audit devices record all API requests and responses in detail. An audit device can be a [file](/vault/docs/audit/file), a [syslog server](/vault/docs/audit/syslog), or a [socket](/vault/docs/audit/socket).
 
 Refer to the [best practices](/vault/docs/audit/best-practices) page for important considerations before you configure your audit devices.
 
@@ -29,6 +29,8 @@ $ vault audit enable file \
 
 Vault replicates audit device configurations to all nodes within a cluster. Vault Enterprise also replicates audit device configurations to performance secondary and disaster recovery secondary clusters unless you configure the audit device as [`local`](/vault/api-docs/system/audit#local) to the cluster. Before you enable an audit device, ensure that all Vault nodes to which the audit device configuration replicates can successfully log to that audit device.
 
+Disaster recovery secondary clusters do not log to any audit devices until Vault promotes the cluster to primary.
+
 When you disable an audit device, Vault immediately stops writing information to the device, but leaves the existing log information untouched.
 
 Once you disable an audit device, you can no longer [compute hashes](#hashing-sensitive-values) for the associated audit log entries. Even if you re-enable the audit device at the same path, Vault creates a new hashing key for the new log entries.

content/vault/v1.21.x/content/docs/audit/index.mdx

@@ -6,7 +6,7 @@ description: Audit devices are mountable devices that log requests and responses
 
 # Audit logging
 
-With a small set of [exceptions](#excepted-api-endpoints), Vault audit devices record all API requests and responses in detail. An audit device can be a [file](/vault/docs/audit/file), a [syslog server](/vault/docs/audit/syslog), or a [socket](/vault/docs/audit/socket).
+With a small set of [exceptions](#exempted-api-endpoints), Vault audit devices record all API requests and responses in detail. An audit device can be a [file](/vault/docs/audit/file), a [syslog server](/vault/docs/audit/syslog), or a [socket](/vault/docs/audit/socket).
 
 Refer to the [best practices](/vault/docs/audit/best-practices) page for important considerations before you configure your audit devices.
 
@@ -29,6 +29,8 @@ $ vault audit enable file \
 
 Vault replicates audit device configurations to all nodes within a cluster. Vault Enterprise also replicates audit device configurations to performance secondary and disaster recovery secondary clusters unless you configure the audit device as [`local`](/vault/api-docs/system/audit#local) to the cluster. Before you enable an audit device, ensure that all Vault nodes to which the audit device configuration replicates can successfully log to that audit device.
 
+Disaster recovery secondary clusters do not log to any audit devices until Vault promotes the cluster to primary.
+
 When you disable an audit device, Vault immediately stops writing information to the device, but leaves the existing log information untouched.
 
 Once you disable an audit device, you can no longer [compute hashes](#hashing-sensitive-values) for the associated audit log entries. Even if you re-enable the audit device at the same path, Vault creates a new hashing key for the new log entries.