From 077ccbda4009969b300186eb2f32e117bee49ee6 Mon Sep 17 00:00:00 2001
From: Rasmus Dahlberg <rasmus.dahlberg@kau.se>
Date: Tue, 12 Oct 2021 18:11:06 +0200
Subject: defined what type of hex encoding is permitted

---
 doc/api.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'doc')

diff --git a/doc/api.md b/doc/api.md
index af2c9b6..e6b0c41 100644
--- a/doc/api.md
+++ b/doc/api.md
@@ -43,10 +43,10 @@ resistant instead of one.
 ### 2.2 - Serialization
 Log requests and responses are transmitted as ASCII-encoded key/value
 pairs, for a smaller dependency than an alternative parser like JSON.
-Some input and output data is binary: cryptographic hashes and
-signatures.  Binary data must be base16-encoded, also known as hex
-encoding.  Using hex as opposed to base64 is motivated by it being
-simpler, favoring ease of decoding and encoding over efficiency on the wire.
+Some input and output data is binary: cryptographic hashes and signatures.
+Binary data must be lower-case base16-encoded, also known as lower-case hex
+encoding.  Using hex as opposed to base64 is motivated by it being simpler,
+favoring ease of decoding and encoding over efficiency on the wire.
 
 We use the [Trunnel](https://gitweb.torproject.org/trunnel.git)
 [description language](https://www.seul.org/~nickm/trunnel-manual.html)
-- 
cgit v1.2.3