From 315f48a72880fd852e871a8c5078b6797bcf310a Mon Sep 17 00:00:00 2001 From: Anders Rundgren Date: Thu, 1 Aug 2024 09:58:08 +0200 Subject: [PATCH] improved wording --- build/document-template.html | 8 ++++---- doc/index.html | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/build/document-template.html b/build/document-template.html index 94d5bff..e31252f 100644 --- a/build/document-template.html +++ b/build/document-template.html @@ -178,10 +178,10 @@

Table of Contents

By default the CBOR.js implementation suports NaN, Infinity, and -Infinity. - In case these variants of Number are not applicable to the application - in question, they can be "outlawed" by setting the global property - CBOR.disableInvalidFloats to true. - This setting affects both encoding and decoding. + In case these variants of Number are not applicable for the application + in question, they can be "outlawed" (causing an exception if encountered), + by setting the global property CBOR.disableInvalidFloats + to true. This setting affects both encoding and decoding.

${DIAGNOSTIC_NOTATION} Creating CBOR data in diagnostic notation (as described in section 8 of RFC 8949), diff --git a/doc/index.html b/doc/index.html index f78fd3a..da6f553 100644 --- a/doc/index.html +++ b/doc/index.html @@ -1069,10 +1069,10 @@
6.2.  Floating Point Numbers

By default the CBOR.js implementation suports NaN, Infinity, and -Infinity. - In case these variants of Number are not applicable to the application - in question, they can be "outlawed" by setting the global property - CBOR.disableInvalidFloats to true. - This setting affects both encoding and decoding. + In case these variants of Number are not applicable for the application + in question, they can be "outlawed" (causing an exception if encountered), + by setting the global property CBOR.disableInvalidFloats + to true. This setting affects both encoding and decoding.

7.  Diagnostic Notation