summaryrefslogtreecommitdiffstatshomepage
path: root/3rdparty/rapidjson/doc/encoding.md
diff options
context:
space:
mode:
Diffstat (limited to '3rdparty/rapidjson/doc/encoding.md')
-rw-r--r--3rdparty/rapidjson/doc/encoding.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/3rdparty/rapidjson/doc/encoding.md b/3rdparty/rapidjson/doc/encoding.md
index 8f8ff7f45aa..e663aeac972 100644
--- a/3rdparty/rapidjson/doc/encoding.md
+++ b/3rdparty/rapidjson/doc/encoding.md
@@ -10,7 +10,7 @@ The earlier [RFC4627](http://www.ietf.org/rfc/rfc4627.txt) stated that,
> (in ยง6) JSON may be represented using UTF-8, UTF-16, or UTF-32. When JSON is written in UTF-8, JSON is 8bit compatible. When JSON is written in UTF-16 or UTF-32, the binary content-transfer-encoding must be used.
-RapidJSON supports various encodings. It can also validate the encodings of JSON, and transconding JSON among encodings. All these features are implemented internally, without the need for external libraries (e.g. [ICU](http://site.icu-project.org/)).
+RapidJSON supports various encodings. It can also validate the encodings of JSON, and transcoding JSON among encodings. All these features are implemented internally, without the need for external libraries (e.g. [ICU](http://site.icu-project.org/)).
[TOC]