From 216af745e34b0f9914ea678b47a0029bc38632d7 Mon Sep 17 00:00:00 2001 From: Glen Mabey Date: Tue, 25 Feb 2025 20:34:53 -0700 Subject: [PATCH] Subject: docs: fix typo --- READMEs/README.coding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/READMEs/README.coding.md b/READMEs/README.coding.md index 43aed1d9b..153f19513 100644 --- a/READMEs/README.coding.md +++ b/READMEs/README.coding.md @@ -190,7 +190,7 @@ a UDP socket pair that the event loop waits on. When the wake is handled by the lws event loop thread, it will broadcast a `LWS_CALLBACK_EVENT_WAIT_CANCELLED` message to every vhost-protocol instantiation, so you can handle this callback, usually lock a shared data region, and if you see you need to write, call -`lws_callback_on_writeable()` for the wsi(s) that need to write. +`lws_callback_on_writable()` for the wsi(s) that need to write. There's no restriction on multiple threads calling `lws_cancel_service()`, it's unconditionally safe due to how it is implemented underneath.