aboutsummaryrefslogtreecommitdiff
path: root/docs/ref/api/msg/nng_msg_header.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref/api/msg/nng_msg_header.md')
-rw-r--r--docs/ref/api/msg/nng_msg_header.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/api/msg/nng_msg_header.md b/docs/ref/api/msg/nng_msg_header.md
index 7c25347c..7743684a 100644
--- a/docs/ref/api/msg/nng_msg_header.md
+++ b/docs/ref/api/msg/nng_msg_header.md
@@ -40,7 +40,7 @@ should be considered overhead in the protocols where they appear.
> [!TIP]
> Most applications should not need to access the message header content
-> directly, unless they ar working with [raw mode][raw] sockets.
+> directly, unless they are working with [raw mode][raw] sockets.
The `nng_msg_header` function returns a pointer to the start of the header
content of the message _msg_.