@@ -14,7 +14,7 @@ To integrate CBOR into your application:
1414 is enough.
1515
1616* Call ``duk_cbor_init() `` to register a global ``CBOR `` object with
17- Ecmascript bindings ``CBOR.encode() `` and ``CBOR.decode() ``, roughly
17+ ECMAScript bindings ``CBOR.encode() `` and ``CBOR.decode() ``, roughly
1818 matching https://github.com/paroga/cbor-js.
1919
2020Basic usage of the ``jsoncbor `` conversion tool::
@@ -24,7 +24,7 @@ Basic usage of the ``jsoncbor`` conversion tool::
2424 $ cat test.json | ./jsoncbor -e # writes CBOR to stdout
2525 $ cat test.cbor | ./jsoncbor -d # writes JSON to stdout
2626
27- CBOR objects are decoded into Ecmascript objects, with non-string keys
27+ CBOR objects are decoded into ECMAScript objects, with non-string keys
2828coerced into strings.
2929
3030Direct support for CBOR is likely to be included in the Duktape API in the
@@ -45,7 +45,7 @@ Some CBOR shortcomings for preserving information:
4545- Array objects with properties lose their non-index properties.
4646- Array objects with gaps lose their gaps as they read back as undefined.
4747- Buffer objects and views lose much of their detail besides the raw data.
48- - Ecmascript strings cannot be fully represented; strings must be UTF-8.
48+ - ECMAScript strings cannot be fully represented; strings must be UTF-8.
4949- Functions and native objects lose most of their detail.
5050- CBOR tags are useful to provide soft decoding information, but the tags
5151 are just integers from an IANA controlled space with no space for custom
0 commit comments