diff --git a/README.md b/README.md index be70b7b..65f2df3 100644 --- a/README.md +++ b/README.md @@ -319,7 +319,7 @@ V>`, as well as any structs or enums annotated with `#[derive(Serialize)]`. It is fast. You should expect in the ballpark of 500 to 1000 megabytes per second deserialization and 600 to 900 megabytes per second serialization, depending on the characteristics of your data. This is competitive with the -fastest C and C++ JSON libraries or even 30% faster for many use cases. +fastest C and C++ JSON libraries, or even 30% faster for many use cases. Benchmarks live in the [serde-rs/json-benchmark] repo. [serde-rs/json-benchmark]: https://github.com/serde-rs/json-benchmark diff --git a/src/lexical/mod.rs b/src/lexical/mod.rs index aeed406..8ac06a0 100644 --- a/src/lexical/mod.rs +++ b/src/lexical/mod.rs @@ -1,4 +1,4 @@ -// The code in this module is derived from the `lexical` crate by @Alexhuszagh +// The code in this module is derived from the `lexical` crate by @Alexhuszagh, // which the author condensed into this minimal subset for use in serde_json. // For the serde_json use case we care more about reliably round tripping all // possible floating point values than about parsing any arbitrarily long string diff --git a/src/macros.rs b/src/macros.rs index c47bdf9..2955e4a 100644 --- a/src/macros.rs +++ b/src/macros.rs @@ -18,7 +18,7 @@ /// /// Variables or expressions can be interpolated into the JSON literal. Any type /// interpolated into an array element or object value must implement Serde's -/// `Serialize` trait, while any type interpolated into a object key must +/// `Serialize` trait, while any type interpolated into an object key must /// implement `Into`. If the `Serialize` implementation of the /// interpolated type decides to fail, or if the interpolated type contains a /// map with non-string keys, the `json!` macro will panic.