From 4e1ffdca6d97c1bddc460835c94b16bc64284861 Mon Sep 17 00:00:00 2001
From: mochalins <117967760+mochalins@users.noreply.github.com>
Date: Fri, 23 May 2025 17:02:52 +0900
Subject: Fix typos across docs, comments, and CMake

---
 docs/ref/api/synch.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/ref/api/synch.md')

diff --git a/docs/ref/api/synch.md b/docs/ref/api/synch.md
index 62e9b7c1..ea545cab 100644
--- a/docs/ref/api/synch.md
+++ b/docs/ref/api/synch.md
@@ -29,7 +29,7 @@ int nng_mutx_alloc(nng_mt **mtxp);
 A mutex can be created by allocating one with {{i:`nng_mtx_lock`}}.
 On success, a pointer to the mutex is returned through _mtxp_.
 This function can fail due to insufficient memory or resources, in which
-case it will return [`NNG_ENOMEM`]. Otherwise it will succceed and return zero.
+case it will return [`NNG_ENOMEM`]. Otherwise it will succeed and return zero.
 
 ### Destroying a Mutex
 
@@ -132,7 +132,7 @@ The difference between these functions is that
 one thread (which may be chosen randomly).
 
 > [!TIP]
-> Use of `nng_cv_wake1` may be used to reduce the "{{i:thundering herd}}" syndrom of waking
+> Use of `nng_cv_wake1` may be used to reduce the "{{i:thundering herd}}" syndrome of waking
 > all threads concurrently, but should only be used in circumstances where the application
 > does not depend on _which_ thread will be woken. When in doubt, `nng_cv_wake` is safer.
 
-- 
cgit v1.2.3-70-g09d2