docs: clarify chunk Map eviction is FIFO by write order

Reads do not refresh recency; match the docs wording to evictChunks().

Co-authored-by: Pavel Kuzmin <Virus191288@gmail.com>

Author: cursoragent

docs/guide/configuration.md

@@ -1297,7 +1297,7 @@ For most projects the default (unlimited, no expiration) is fine — route names
 `cacheMaxSize` caps:
 
 1. **Fetch / server `CacheControl`** (HTTP payload and server loader caches)
-2. **Client chunk Map** (`NuxtI18n.storage.translations`) — oldest unused `(locale, route)` chunks are evicted; the just-written and active page keys are preferred. If the limit cannot hold both (e.g. `cacheMaxSize: 1`), the just-written key wins so the bound is enforced — active `$t` still uses the view layer
+2. **Client chunk Map** (`NuxtI18n.storage.translations`) — oldest (by write order) `(locale, route)` chunks are FIFO-evicted; the just-written and active page keys are preferred. If the limit cannot hold both (e.g. `cacheMaxSize: 1`), the just-written key wins so the bound is enforced — active `$t` still uses the view layer
 
 - **`cacheMaxSize`** — caps entries in those caches. Useful for bounding memory.
 - **`cacheTtl`** — expires fetch/server cache entries (not the live view layer). Useful for serverless or runtime-updated translations.