Skip to content

Commit 16b68b0

Browse files
authored
Tweak grammar to improve readability
1 parent 7025523 commit 16b68b0

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ with JSON data in Rust.
5656
of your data to conform to a particular structure and want to get real
5757
work done without JSON's loosey-goosey nature tripping you up.
5858

59-
Serde JSON provides efficient, flexible, safe ways of converting data
59+
Serde JSON provides efficient, flexible, and safe ways of converting data
6060
between each of these representations.
6161

6262
## Operating on untyped JSON values
@@ -131,9 +131,9 @@ section.
131131

132132
The `Value` representation is sufficient for very basic tasks but can be tedious
133133
to work with for anything more significant. Error handling is verbose to
134-
implement correctly, for example imagine trying to detect the presence of
134+
implement correctly; for example, imagine trying to detect the presence of
135135
unrecognized fields in the input data. The compiler is powerless to help you
136-
when you make a mistake, for example imagine typoing `v["name"]` as `v["nmae"]`
136+
when you make a mistake; for example, imagine typoing `v["name"]` as `v["nmae"]`
137137
in one of the dozens of places it is used in your code.
138138

139139
## Parsing JSON as strongly typed data structures
@@ -265,8 +265,8 @@ let john = json!({
265265
});
266266
```
267267

268-
This is amazingly convenient but we have the problem we had before with
269-
`Value` which is that the IDE and Rust compiler cannot help us if we get it
268+
This is amazingly convenient, but we have the problem we had before with
269+
`Value`: the IDE and Rust compiler cannot help us if we get it
270270
wrong. Serde JSON provides a better way of serializing strongly-typed data
271271
structures into JSON text.
272272

@@ -321,14 +321,14 @@ way. This includes built-in Rust standard library types like `Vec<T>` and
321321
It is fast. You should expect in the ballpark of 500 to 1000 megabytes per
322322
second deserialization and 600 to 900 megabytes per second serialization,
323323
depending on the characteristics of your data. This is competitive with the
324-
fastest C and C++ JSON libraries or even 30% faster for many use cases.
324+
fastest C and C++ JSON libraries (or even 30% faster for many use cases).
325325
Benchmarks live in the [serde-rs/json-benchmark] repo.
326326

327327
[serde-rs/json-benchmark]: https://github.com/serde-rs/json-benchmark
328328

329329
## Getting help
330330

331-
Serde is one of the most widely used Rust libraries so any place that Rustaceans
331+
Serde is one of the most widely used Rust libraries, so any place that Rustaceans
332332
congregate will be able to help you out. For chat, consider trying the
333333
[#rust-questions] or [#rust-beginners] channels of the unofficial community
334334
Discord (invite: <https://discord.gg/rust-lang-community>), the [#rust-usage] or
@@ -337,7 +337,7 @@ Discord (invite: <https://discord.gg/rust-lang-community>), the [#rust-usage] or
337337
asynchronous, consider the [\[rust\] tag on StackOverflow][stackoverflow], the
338338
[/r/rust] subreddit which has a pinned weekly easy questions post, or the Rust
339339
[Discourse forum][discourse]. It's acceptable to file a support issue in this
340-
repo but they tend not to get as many eyes as any of the above and may get
340+
repo, but they tend not to get as many eyes as any of the above and may get
341341
closed without a response after some time.
342342

343343
[#rust-questions]: https://discord.com/channels/273534239310479360/274215136414400513

0 commit comments

Comments
 (0)