Perform quality control on all statements

.github/CODE_OF_CONDUCT.md

@@ -14,7 +14,7 @@ diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our
+Examples of behaviour that contributes to a positive environment for our
 community include:
 
 * Demonstrating empathy and kindness toward other people
@@ -25,7 +25,7 @@ community include:
 * Focusing on what is best not just for us as individuals, but for the overall
   community
 
-Examples of unacceptable behavior include:
+Examples of unacceptable behaviour include:
 
 * The use of sexualized language or imagery, and sexual attention or advances of
   any kind
@@ -39,8 +39,8 @@ Examples of unacceptable behavior include:
 ## Enforcement Responsibilities
 
 Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
+acceptable behaviour and will take appropriate and fair corrective action in
+response to any behaviour that they deem inappropriate, threatening, offensive,
 or harmful.
 
 Community leaders have the right and responsibility to remove, edit, or reject
@@ -58,7 +58,7 @@ representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be
 reported to the community leaders responsible for enforcement at
 [mail@nlohmann.me](mailto:mail@nlohmann.me).
 All complaints will be reviewed and investigated promptly and fairly.
@@ -73,19 +73,19 @@ the consequences for any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed
+**Community Impact**: Use of inappropriate language or other behaviour deemed
 unprofessional or unwelcome in the community.
 
 **Consequence**: A private, written warning from community leaders, providing
 clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
+behaviour was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
 **Community Impact**: A violation through a single incident or series of
 actions.
 
-**Consequence**: A warning with consequences for continued behavior. No
+**Consequence**: A warning with consequences for continued behaviour. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
@@ -95,7 +95,7 @@ ban.
 ### 3. Temporary Ban
 
 **Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
+sustained inappropriate behaviour.
 
 **Consequence**: A temporary ban from any sort of interaction or public
 communication with the community for a specified period of time. No public or
@@ -106,7 +106,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
+standards, including sustained inappropriate behaviour, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within the

.github/CONTRIBUTING.md

@@ -185,7 +185,7 @@ Although these guidelines may seem restrictive, they are essential for maintaini
 
 Breaking changes may be introduced when they are guarded with a feature macro such as
 [`JSON_USE_IMPLICIT_CONVERSIONS`](https://json.nlohmann.me/api/macros/json_use_implicit_conversions/) which allows to
-selectively change the behavior of the library. In next steps, the current behavior can then be deprecated. Using
+selectively change the behaviour of the library. In next steps, the current behaviour can then be deprecated. Using
 feature macros then allows users to test their code against the library in the next major release.
 
 ### Break C++11 language conformance

ChangeLog.md

@@ -728,7 +728,7 @@ All notable changes to this project will be documented in this file. This projec
 - string literals possibly being parsed as another type due to the presence of only digits and full-stops [\#2852](https://github.com/nlohmann/json/issues/2852)
 - json::parse\(\) works only with absolute paths [\#2851](https://github.com/nlohmann/json/issues/2851)
 - Compiler Warnings on Raspberry Pi OS [\#2850](https://github.com/nlohmann/json/issues/2850)
-- Braced initialization and aggregate initialization behavior is different for `json::array()` function call. [\#2848](https://github.com/nlohmann/json/issues/2848)
+- Braced initialization and aggregate initialization behaviour is different for `json::array()` function call. [\#2848](https://github.com/nlohmann/json/issues/2848)
 - 3.9.1: test suite is failing [\#2845](https://github.com/nlohmann/json/issues/2845)
 - Documentation for macro JSON\_NO\_IO is missing [\#2842](https://github.com/nlohmann/json/issues/2842)
 - Assertion failure when inserting into arrays with JSON\_DIAGNOSTICS set [\#2838](https://github.com/nlohmann/json/issues/2838)
@@ -843,7 +843,7 @@ All notable changes to this project will be documented in this file. This projec
 - ADL issue in input\_adapter [\#2248](https://github.com/nlohmann/json/issues/2248)
 - Output adapters should be templated. [\#2172](https://github.com/nlohmann/json/issues/2172)
 - error when using nlohmann::json, std::function and std::bind [\#2147](https://github.com/nlohmann/json/issues/2147)
-- Remove undefined behavior for const operator\[\] [\#2111](https://github.com/nlohmann/json/issues/2111)
+- Remove undefined behaviour for const operator\[\] [\#2111](https://github.com/nlohmann/json/issues/2111)
 - json\({}\) gives null instead of empty object with GCC and -std=c++17 [\#2046](https://github.com/nlohmann/json/issues/2046)
 - GDB pretty printing support [\#1952](https://github.com/nlohmann/json/issues/1952)
 - Always compile tests with all warnings enabled and error out on warnings [\#1798](https://github.com/nlohmann/json/issues/1798)
@@ -1192,7 +1192,7 @@ All notable changes to this project will be documented in this file. This projec
 - Build error  when modify value [\#1998](https://github.com/nlohmann/json/issues/1998)
 - How do i include a vector of pointers in my json? [\#1997](https://github.com/nlohmann/json/issues/1997)
 - Compiler error wrt incomplete types changed in gcc8.3.0-26 [\#1996](https://github.com/nlohmann/json/issues/1996)
-- NaN-like comparison behavior of discarded is inconvenient [\#1988](https://github.com/nlohmann/json/issues/1988)
+- NaN-like comparison behaviour of discarded is inconvenient [\#1988](https://github.com/nlohmann/json/issues/1988)
 - Maintaining JSON package in my CMake [\#1987](https://github.com/nlohmann/json/issues/1987)
 - reading int number and string number [\#1986](https://github.com/nlohmann/json/issues/1986)
 - Build error: keyword is hidden by macro definition! [\#1985](https://github.com/nlohmann/json/issues/1985)
@@ -1287,7 +1287,7 @@ All notable changes to this project will be documented in this file. This projec
 - How to serialize nested classes to semi-flat JSON object? [\#1859](https://github.com/nlohmann/json/issues/1859)
 - Memory Requirement for large json file [\#1858](https://github.com/nlohmann/json/issues/1858)
 - Query a binary format \(BSON, CBOR, MessagePack, UBJSON\) [\#1856](https://github.com/nlohmann/json/issues/1856)
-- Documentation on operator\[\] behavior with missing keys [\#1855](https://github.com/nlohmann/json/issues/1855)
+- Documentation on operator\[\] behaviour with missing keys [\#1855](https://github.com/nlohmann/json/issues/1855)
 - Problem in converting string into JSON; Can't parse successfully. [\#1854](https://github.com/nlohmann/json/issues/1854)
 - json.at\_or\_default\(key, defaultval\) [\#1852](https://github.com/nlohmann/json/issues/1852)
 - please improve the enum conversion documentation \(my example gist provided\) [\#1851](https://github.com/nlohmann/json/issues/1851)
@@ -1315,7 +1315,7 @@ All notable changes to this project will be documented in this file. This projec
 - Add support for parse stack limiting [\#1788](https://github.com/nlohmann/json/issues/1788)
 - GCC -Wuseless-cast warnings [\#1777](https://github.com/nlohmann/json/issues/1777)
 - compilation issue with NVCC 9.0 [\#1773](https://github.com/nlohmann/json/issues/1773)
-- Unexpected behavior with fifo\_map json when copy and append  [\#1763](https://github.com/nlohmann/json/issues/1763)
+- Unexpected behaviour with fifo\_map json when copy and append  [\#1763](https://github.com/nlohmann/json/issues/1763)
 - Parse error [\#1761](https://github.com/nlohmann/json/issues/1761)
 - Assignment \(using value\(\)\) to nonexistent element behaves differently on Xcode 8 vs Xcode 10 [\#1758](https://github.com/nlohmann/json/issues/1758)
 - Readme out of date [\#1756](https://github.com/nlohmann/json/issues/1756)
@@ -1839,7 +1839,7 @@ All notable changes to this project will be documented in this file. This projec
 - Get value without explicit typecasting [\#1395](https://github.com/nlohmann/json/issues/1395)
 - Big file parsing [\#1393](https://github.com/nlohmann/json/issues/1393)
 - Adding Structured Binding Support [\#1388](https://github.com/nlohmann/json/issues/1388)
-- map\<json::value\_t, string\> exhibits unexpected behavior [\#1387](https://github.com/nlohmann/json/issues/1387)
+- map\<json::value\_t, string\> exhibits unexpected behaviour [\#1387](https://github.com/nlohmann/json/issues/1387)
 - Error Code Return [\#1386](https://github.com/nlohmann/json/issues/1386)
 - using unordered\_map as object type [\#1385](https://github.com/nlohmann/json/issues/1385)
 - float precision [\#1384](https://github.com/nlohmann/json/issues/1384)
@@ -2673,7 +2673,7 @@ All notable changes to this project will be documented in this file. This projec
 - Reuse memory in to\_cbor and to\_msgpack functions [\#476](https://github.com/nlohmann/json/issues/476)
 - Error Using JSON Library with arrays C++ [\#475](https://github.com/nlohmann/json/issues/475)
 - Moving forward to version 3.0.0 [\#474](https://github.com/nlohmann/json/issues/474)
-- Inconsistent behavior in conversion to array type [\#473](https://github.com/nlohmann/json/issues/473)
+- Inconsistent behaviour in conversion to array type [\#473](https://github.com/nlohmann/json/issues/473)
 - Create a \[key:member\_pointer\] map to ease parsing custom types [\#471](https://github.com/nlohmann/json/issues/471)
 - MSVC 2015 update 2 [\#469](https://github.com/nlohmann/json/issues/469)
 - VS2017 implicit to std::string conversion fix. [\#464](https://github.com/nlohmann/json/issues/464)
@@ -2684,7 +2684,7 @@ All notable changes to this project will be documented in this file. This projec
 - Is it possible to turn this into a shared library? [\#420](https://github.com/nlohmann/json/issues/420)
 - Further thoughts on performance improvements [\#418](https://github.com/nlohmann/json/issues/418)
 - nan number stored as null [\#388](https://github.com/nlohmann/json/issues/388)
-- Behavior of operator\>\> should more closely resemble that of built-in overloads. [\#367](https://github.com/nlohmann/json/issues/367)
+- behaviour of operator\>\> should more closely resemble that of built-in overloads. [\#367](https://github.com/nlohmann/json/issues/367)
 - Request: range-based-for over a json-object to expose .first/.second [\#350](https://github.com/nlohmann/json/issues/350)
 - feature wish: JSONPath [\#343](https://github.com/nlohmann/json/issues/343)
 - UTF-8/Unicode escape and dump [\#330](https://github.com/nlohmann/json/issues/330)
@@ -2986,7 +2986,7 @@ All notable changes to this project will be documented in this file. This projec
 - Equality operator results in array when assigned object [\#292](https://github.com/nlohmann/json/issues/292)
 - Support for integers not from the range \[-\(2\*\*53\)+1, \(2\*\*53\)-1\] in parser [\#291](https://github.com/nlohmann/json/issues/291)
 - Support for iterator-range parsing [\#290](https://github.com/nlohmann/json/issues/290)
-- Horribly inconsistent behavior between const/non-const reference in operator \[\] \(\) [\#289](https://github.com/nlohmann/json/issues/289)
+- Horribly inconsistent behaviour between const/non-const reference in operator \[\] \(\) [\#289](https://github.com/nlohmann/json/issues/289)
 - Silently get numbers into smaller types [\#288](https://github.com/nlohmann/json/issues/288)
 - Incorrect parsing of large int64\_t numbers [\#287](https://github.com/nlohmann/json/issues/287)
 - \[question\]: macro to disable floating point support [\#284](https://github.com/nlohmann/json/issues/284)