From 1f3b72f008de5ffcc039afde06742c4f4b87b81e Mon Sep 17 00:00:00 2001 From: chrysn Date: Wed, 9 Oct 2024 13:29:24 +0200 Subject: [PATCH] fixup! Co-authored-by: ROMemories <152802150+ROMemories@users.noreply.github.com> --- book/src/tooling/coap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/tooling/coap.md b/book/src/tooling/coap.md index b3eb2e7ea..cb58098d9 100644 --- a/book/src/tooling/coap.md +++ b/book/src/tooling/coap.md @@ -106,7 +106,7 @@ A program that triggers a CoAP request provides[^whatsinarequest] some component Examples of policies that can be available are "expect the server to present some concrete public key, use this secret key once the server is verified", "use a token for this audience and scope obtained from that authentication server", - "expect the server to present a chain of certificates for its host name down to a set of root certificates" (which is the default for web browsers), + "expect the server to present a chain of certificates for its hostname down to a set of root certificates" (which is the default for web browsers), "establish an encrypted connection and trust the peer's key on first use" down to "do not use any encryption".