From 53bce88c52c3c6dba3ab4d1d9abf2036de051fe8 Mon Sep 17 00:00:00 2001
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Thu, 2 Jan 2025 15:59:57 +0100
Subject: typo

---
 faq/foo_max.mdwn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/faq/foo_max.mdwn b/faq/foo_max.mdwn
index 14015b9b..5f736680 100644
--- a/faq/foo_max.mdwn
+++ b/faq/foo_max.mdwn
@@ -39,7 +39,7 @@ since Posix 2008 `realpath(path, NULL)` and `getcwd(NULL, 0)` allocate the path
 dynamically.
 
 In general, using `FOO_MAX` in source code (with a large value) leads to code
-that is not acually checking against overflows. `PATH_MAX` being 4096 is
+that is not actually checking against overflows. `PATH_MAX` being 4096 is
 actually "wrong" on Linux:
 
     $ printf '#include <limits.h>\nPATH_MAX' | cpp -P
-- 
cgit v1.2.3