From ab0aa4a153616367e1efa876a4c729dbde0f3b73 Mon Sep 17 00:00:00 2001 From: Qianqian Fang Date: Wed, 11 May 2022 23:31:53 -0400 Subject: [PATCH] Minor edit --- docs/mkdocs/docs/features/binary_formats/bjdata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mkdocs/docs/features/binary_formats/bjdata.md b/docs/mkdocs/docs/features/binary_formats/bjdata.md index 34d120747..9a641e669 100644 --- a/docs/mkdocs/docs/features/binary_formats/bjdata.md +++ b/docs/mkdocs/docs/features/binary_formats/bjdata.md @@ -84,7 +84,7 @@ The library uses the following mapping from JSON values types to BJData types ac A breaking difference between BJData and UBJSON is the endianness of numerical values. In BJData, all numerical data types (integers `UiuImlML` and floating-point values `hdD`) are stored in the little-endian (LE) - byte order as opposed to the big-endian as used by UBJSON. To adopt LE + byte order as opposed to big-endian as used by UBJSON. To adopt LE to store numeric records avoids unnecessary byte swapping on most modern computers where LE is used as the default byte order.