From 6b3bb529db4bdd3cf21582c85eab41fd1a8d7a66 Mon Sep 17 00:00:00 2001 From: Fredrik Teschke Date: Thu, 23 Jul 2026 07:43:02 +0200 Subject: [PATCH] docs: Fix type --- docs/management/expiring-records.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/management/expiring-records.md b/docs/management/expiring-records.md index 1cc233fb..0bbfe887 100644 --- a/docs/management/expiring-records.md +++ b/docs/management/expiring-records.md @@ -44,7 +44,7 @@ Naturally this technique cannot stand alone as it only evicts on key retrieval; There are a number of ways to provide expirations for entries inside a cache: -* Setting a default expiration for a cahe via `Cachex.start_link/2` +* Setting a default expiration for a cache via `Cachex.start_link/2` * Setting an expiration manually via `Cachex.expire/4` or `Cachex.expire_at/4` * Setting the `:expire` option within calls to `Cachex.put/4` or `Cachex.put_many/3` * Setting the `:expire` option within return tuples in `Cachex.fetch/4` or `Cachex.get_and_update/4`