diff --git a/docs/api/async-flush-policy.md b/docs/api/async-flush-policy.md
index 9964d1c..85cad36 100644
--- a/docs/api/async-flush-policy.md
+++ b/docs/api/async-flush-policy.md
@@ -34,6 +34,7 @@ Detailed rules explaining key parameters and behaviors
 - `AsyncFlushPolicy::Batch` calls the configured flush function after each processed batch.
 - `AsyncFlushPolicy::Shutdown` calls the configured flush function once after the worker loop exits.
 - The current flush policy is also exposed through `AsyncLogger::flush_policy()` and included in `AsyncLoggerState`.
+- The canonical labels `Never`, `Batch`, and `Shutdown` are also the labels emitted by async config and logger-state serializers, so parsing and diagnostics share one public vocabulary.
 - Async config parsing accepts the canonical label `Never` and also the compatibility alias `None`, both mapping to the same public enum variant.
 - `Batch` flushing happens after the worker finishes one drained batch, not after every individual record write.
 
@@ -64,6 +65,8 @@ In this example, flushing happens when the worker loop exits instead of after ea
 e.g.:
 - If async config text uses unsupported flush policy text, async config parsing raises a failure.
 
+- The parser error path for unsupported flush text is the same `Failure` surface used by the async config utilities.
+
 - If a sink never needs explicit flushing, `Batch` or `Shutdown` can add unnecessary work without changing output.
 
 - If the configured flush callback raises, the worker records failure state and stops instead of silently hiding the error.
diff --git a/docs/api/async-overflow-policy.md b/docs/api/async-overflow-policy.md
index 33d224b..db54182 100644
--- a/docs/api/async-overflow-policy.md
+++ b/docs/api/async-overflow-policy.md
@@ -34,6 +34,7 @@ Detailed rules explaining key parameters and behaviors
 - `AsyncOverflowPolicy::DropOldest` lets the underlying async queue discard older pending records when capacity is limited.
 - `AsyncOverflowPolicy::DropNewest` discards the incoming record instead of blocking.
 - The same enum is used by `AsyncLoggerConfig::new(...)`, async config parsing, and the queue-kind mapping inside `AsyncLogger`.
+- The canonical labels `Blocking`, `DropOldest`, and `DropNewest` are also the labels emitted again by async config serializers, so export and parse stay aligned around one public vocabulary.
 - Async config parsing accepts the canonical label `DropNewest` and also the compatibility alias `DropLatest`, both mapping to the same public enum variant.
 - When `try_put(...)` reports that a record was not accepted under a drop policy, `dropped_count()` increases for that rejected enqueue.
 
@@ -64,6 +65,8 @@ In this example, the incoming record is dropped if the queue cannot accept it.
 e.g.:
 - If async config text uses unsupported overflow text, async config parsing raises a failure.
 
+- The parser error path for unsupported overflow text is the same `Failure` surface used by the async config utilities.
+
 - Under drop policies, sustained overload increases `dropped_count()` instead of guaranteeing delivery.
 
 - The precise record discarded by the underlying queue behavior depends on the selected policy and queue implementation, so callers should not assume `dropped_count()` alone identifies which message was lost.