aboutsummaryrefslogtreecommitdiff
path: root/docs/ref/api/sock.md
diff options
context:
space:
mode:
authormochalins <117967760+mochalins@users.noreply.github.com>2025-05-23 17:02:52 +0900
committerGarrett D'Amore <garrett@damore.org>2025-06-02 07:24:06 -0700
commit4e1ffdca6d97c1bddc460835c94b16bc64284861 (patch)
tree80c27b0e509c8d7001619af27a33794f4bcad3c4 /docs/ref/api/sock.md
parent1323aece0712522ccb2bf432b5085889a3513fa8 (diff)
downloadnng-4e1ffdca6d97c1bddc460835c94b16bc64284861.tar.gz
nng-4e1ffdca6d97c1bddc460835c94b16bc64284861.tar.bz2
nng-4e1ffdca6d97c1bddc460835c94b16bc64284861.zip
Fix typos across docs, comments, and CMake
Diffstat (limited to 'docs/ref/api/sock.md')
-rw-r--r--docs/ref/api/sock.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/api/sock.md b/docs/ref/api/sock.md
index 4ebd8051..bc5c1380 100644
--- a/docs/ref/api/sock.md
+++ b/docs/ref/api/sock.md
@@ -227,7 +227,7 @@ These functions ({{i:`nng_recv`}}, {{i:`nng_recvmsg`}}, and {{i:`nng_socket_recv
messages over the socket _s_. The differences in their behaviors are as follows.
> [!NOTE]
-> The semantics of what receving a message means varies from protocol to
+> The semantics of what receiving a message means varies from protocol to
> protocol, so examination of the protocol documentation is encouraged.
> Additionally, some protocols may not support receiving at all or may require other pre-conditions first.
> (For example, [REQ][req] sockets cannot normally receive data until they have first sent a request,