docs: clarify batch API limitation guidance

Signed-off-by: memleakd <[email protected]>

Author: memleakd

docs/limitations.md

@@ -5,8 +5,8 @@ The following are known limitations of the library:
 1. **Immediate writes (`deferWrites => false`)**: Each setting is written to storage immediately when you call `set()` or `forget()`.
    The first operation hydrates all settings for that context (1 SELECT query), then each subsequent write performs a separate
    INSERT or UPDATE. While `DatabaseHandler` and `FileHandler` use an in-memory cache to maintain fast reads, individual write
-   operations may result in multiple database queries or file writes per request. Use `setMany()` or `forgetMany()` when you
-   want to explicitly persist multiple settings in one batch operation.
+   operations may result in multiple database queries or file writes per request. When multiple changes are known ahead of time,
+   use `setMany()` or `forgetMany()` to group them explicitly and allow supported handlers to persist them more efficiently.
 
 2. **Deferred writes (`deferWrites => true`)**: All settings are batched and written to storage at the end of the request
    (during the `post_system` event). This minimizes the number of database queries and file writes, improving performance.