From 534d1d0e3d16993656077591292d29e9786d2bc4 Mon Sep 17 00:00:00 2001 From: Joao Gilberto Magalhaes Date: Tue, 20 Oct 2026 11:48:55 -0400 Subject: [PATCH] Remove the explicit heading id from compare-and-swap.md The documentation site keeps the MDX v1 heading id syntax off, so {#...} broke its build. The id Docusaurus generates from the heading is the same one. --- docs/compare-and-swap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/compare-and-swap.md b/docs/compare-and-swap.md index 1257460..ae752f3 100644 --- a/docs/compare-and-swap.md +++ b/docs/compare-and-swap.md @@ -124,7 +124,7 @@ is still a guess: a slow owner can have its lock expire while it is still workin will correctly refuse that owner's release, but the work has already run twice. If you need guarantees beyond "exactly one winner per acquisition", you want a real lock manager. -## Why not FileSystemCacheEngine {#why-not-filesystemcacheengine} +## Why not FileSystemCacheEngine The file system is not a reliable substrate for mutual exclusion, and this engine does not pretend otherwise. Use Redis or Memcached.