From 0531bf7790d349bb5c46fe845680089793297870 Mon Sep 17 00:00:00 2001 From: Christian Legnitto Date: Thu, 13 Sep 2018 11:10:02 -0700 Subject: [PATCH] Fix README grammar --- changelog/0.10.0.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/changelog/0.10.0.md b/changelog/0.10.0.md index d9ebb9d3..79be882e 100644 --- a/changelog/0.10.0.md +++ b/changelog/0.10.0.md @@ -14,11 +14,10 @@ [#170](https://github.com/graphql-rust/juniper/pull/170) - Large integers (> signed 32bit) are now deserialized as floats. Previously, - they produced the "integer out of range" error. For languages that do not - have distinction between integer and floating point types (including - javascript), this means large floating point values which do not have - fractional part could not be decoded (because they are represented without - a decimal part `.0`). + they produced an "integer out of range" error. For languages that do not + have a distinction between integer and floating point types (such as + javascript), this meant large whole floating point values could not be + decoded (because they were represented without a fractional value such as `.0`). [#179](https://github.com/graphql-rust/juniper/pull/179) @@ -50,7 +49,7 @@ [#225](https://github.com/graphql-rust/juniper/issues/225) -* When using the `GraphQLObject` custom derive, fields now be omitted by annotating the field with `#[graphql(skip)]`. +* When using the `GraphQLObject` custom derive, fields can now be omitted by annotating the field with `#[graphql(skip)]`. [#220](https://github.com/graphql-rust/juniper/issues/220)