fix typo - json2tsv - JSON to TSV converter
 (HTM) git clone git://git.codemadness.org/json2tsv
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) README
 (DIR) LICENSE
       ---
 (DIR) commit 705f468584d0c425b6871a6e1f894e4c7aad0993
 (DIR) parent 8ec8c8f26da6e20e58150a5b9e611ec651445469
 (HTM) Author: Hiltjo Posthuma <hiltjo@codemadness.org>
       Date:   Mon, 15 May 2023 18:47:02 +0200
       
       fix typo
       
       Diffstat:
         M json.c                              |       4 ++--
         M json2tsv.1                          |       2 +-
       
       2 files changed, 3 insertions(+), 3 deletions(-)
       ---
 (DIR) diff --git a/json.c b/json.c
       @@ -132,7 +132,7 @@ handlechr:
                                while (1) {
                                        c = GETNEXT();
        chr:
       -                                /* EOF or control char: 0x7f is not defined as a control char in RFC8259 */
       +                                /* EOF or control char: 0x7f is not defined as a control char in RFC 8259 */
                                        if (c < 0x20)
                                                JSON_INVALID();
        
       @@ -156,7 +156,7 @@ escchr:
                                                                        JSON_INVALID(); /* invalid code point */
                                                                cp |= (hexdigit(c) << i);
                                                        }
       -                                                /* RFC8259 - 7. Strings - surrogates.
       +                                                /* RFC 8259 - 7. Strings - surrogates.
                                                         * 0xd800 - 0xdbff - high surrogates */
                                                        if (cp >= 0xd800 && cp <= 0xdbff) {
                                                                if ((c = GETNEXT()) != '\\') {
 (DIR) diff --git a/json2tsv.1 b/json2tsv.1
       @@ -151,7 +151,7 @@ output, this can change the meaning of the nodename field.
        The JSON parser handles all valid JSON.
        It also allows some invalid JSON extensions: it does not do a complete
        validation on numbers and is not strict with handling unicode input.
       -See also RFC8259 section 9. Parsers.
       +See also RFC 8259 section 9. Parsers.
        .It
        The maximum depth of objects or arrays is hard-coded to 64 levels deep.
        .El